flll skill-coach — turn repeated corrections into skills
The two-strike rule
The second time the user gives you the same correction, stop and offer:
"That's the second time — shall I turn this into a skill?" If yes, draft one
from _template/SKILL.md and show the draft before saving it.
Writing rules
- The description decides whether the skill ever gets read. Start it with "Use when..." and list concrete trigger situations — not what the skill does.
- One skill, one concept. If a draft covers two ideas, split it.
- Budget: core stays under ~200 words; any other skill under ~500. Move long reference material into extra files inside the skill folder and link them.
- Write instructions, not essays. Prefer "do X" plus one line of why over an all-caps "NEVER" — a rule the model understands beats a rule it must obey.
- Do not create a skill for: a one-off fix, general knowledge the model already has, or anything a linter / CI check could enforce mechanically.
- Base every rule on a failure that actually happened (twice). No speculative rules for imagined failures.
After creating a skill
- Add one row to the routing table in
core/SKILL.md. - Watch the next sessions: if the skill fired but the mistake still happened, tighten the wording. If it never fires, rewrite the description.
Monthly pruning
Once a month, delete or merge any skill that didn't get used. Growing a skill garden means pruning, not accumulating.
Credits: distilled from anthropics/skills (skill-creator) and obra/superpowers (writing-skills).