agentleFS
flllflll/grow-your-own-skills/skills/skill-coach/SKILL.md

skill-coach

Skill0 starsChanged 5 months agoCC0-1.0View on GitHub

Use when the user corrects you about the same thing for the second time, or when they ask to create, improve, or prune a skill. Also use when you catch yourself repeating a mistake an existing skill was meant to prevent. Not for one-off fixes that will never recur.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. AlejandroVegaFullstackDev/ai-skill-coach★ 3same name
    2. dhriyatinandu-bot/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write instructions, not essays.

    line 25
  2. Distinctive:

    Do not create a skill for: a one-off fix, general knowledge the model already has, or anything a linter / CI check could enforce …

    line 27
  3. Very specific:

    Add one row to the routing table in core/SKILL.md.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Add one row to the routing table in core/SKILL.md.
  2. 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).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.