Skip to main content
Improve a skill when SelfTune has evidence of a specific problem, such as missed activation, weak instructions, or a regression. Start with a preview and keep the change only when its validation is stronger than the current version.

​
Ask your agent

​
What should happen

1

Confirm the target and evidence

The agent resolves the source SKILL.md, checks health and recent evidence, and stops if the data does not support a specific change.
2

Preview a bounded change

The default manual preview is:
Select a narrower scope only when the evidence identifies that surface.
3

Review the proposal

Review the source evidence, changed files, behavioral claim, validation method, and recovery plan. A larger diff is not evidence of a better skill.
4

Apply and verify

After approval, let the agent apply the proposed change and repeat the same evaluation against the previous version. Keep a backup or version-control diff until post-change evidence is available.

​
Success criteria

  • The proposal addresses an observed problem, not a speculative rewrite.
  • Unrelated skill surfaces and files remain unchanged.
  • The comparison uses the same evaluation conditions for both versions.
  • The agent reports ambiguous or negative results instead of selecting a winner.
  • You can identify and restore the previous version.
Do not use a higher score from a different test set, agent, or model as proof of improvement. Change one side of the comparison at a time.