30bdc7c516
autotune, autoskill and confidence each carried their own idea of what an improvement is, and autotune's two efficiency rules were the same sentence twice. They now route to one skill that names three axes to move at once — fewer tokens, less time, higher quality — and the rules that decide when a proposal counts: at least one axis better, none damaged, quality never the currency, observed friction instead of a guessed percentage. Applying its own rule, autotune gets shorter rather than longer. The test holds the coupling, so a later rewrite cannot silently drop a route. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1.9 KiB
1.9 KiB
name, description
| name | description |
|---|---|
| autoskill | Detect operator repetition and turn it into a skill. Trigger when the operator gives an instruction, correction, or prompt pattern for roughly the third time in a conversation (or says they keep repeating themselves), and the pattern is general enough to reuse. Portable across projects. |
Its objective is the optimize skill's: a skill is worth creating only when it
cuts tokens or time and raises quality — judge every candidate against that
skill's three axes and rules.
When you notice the operator repeating the same kind of instruction, correction, or prompt pattern (about three occurrences, exact wording may vary), do the following:
- Finish the current task first; never interrupt work in progress.
- Then propose, in one short paragraph: the repeated pattern you observed, a skill name suggestion, the trigger phrasing, and what the skill would do. Ask whether to create it.
- On approval, write the skill:
- a conversation shortcut or expansion: add it to the
shortcutsskill table instead of creating a new skill. - anything else: persist it exactly as the
autotuneskill's Persistence section specifies — locate the operator's skills repository, writeskills/<name>/SKILL.mdthere (or in the current project for project-specific behavior), then mirror the skill directory into~/.claude/skills/and~/.agents/skills/, plus the project's.claude/skills/and.agents/skills/when it is project-specific. Follow the local naming conventions and keep the skill a thin, single-purpose instruction; route to an authoritative doc when one exists instead of duplicating it.
- a conversation shortcut or expansion: add it to the
- Do not propose a skill for one-off work, secrets, or anything whose repetition is already covered by an existing skill; when an existing skill almost fits, propose extending it instead.