agentleFS
Archive228Archive228/loopkit/template/SKILL.md

my-new-skill

Skill754 starsChanged 5 months agoMITView on GitHub

One sentence that describes WHEN to invoke this skill. Write it as a trigger phrase, not a summary — include the words a user would say ("fix bug", "add feature", "review diff"). The agent routes on this field.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. BaratiLab/mechanical-engineering-skills★ 16same name
    2. pradyumnasagar/open-research-skills★ 8same name
    3. colomet/skill-boilerplate★ 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

2 rules. About 0 are common, 2 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every skill ships with a real before/after pair proving it changes agent behaviour on a concrete task.

    line 51
  2. Distinctive:

    If you cannot produce a before/after pair, the skill is not ready to ship.

    line 61

≈ “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

My New Skill

<!-- Anthropic-shaped SKILL.md template. Copy this folder to skills/<your-name>/ and edit. Keep the body under ~150 lines — long bodies are a context tax on every turn where this skill is loaded. Recommended structure: 1. One-paragraph statement of the failure mode this skill exists to prevent. 2. A short checklist or numbered procedure the agent should follow. 3. Red flags — the shortcuts an agent takes when it wants to skip this. 4. Evidence — a required before/after pair proving the skill actually changes behaviour. Ships in the sibling evidence/ folder. 5. (optional) `references/` sibling files with deeper material the skill lazy-loads only when needed. Do not include: - Marketing copy. - Duplicates of other skills (link, do not copy). - Project-specific rules — those belong in .claude/rules/. Frontmatter contract (validated by scripts/validate-skills + CI): - `name` — kebab-case, unique across the repo, matches the directory name. - `description` — one non-empty line, phrased as a trigger. - Anything else is optional and not currently enforced. -->

Without this skill, the agent tends to <failure mode>. This skill enforces <the alternative>.

Steps

  1. <step>
  2. <step>
  3. <step>

Red flags — STOP

ThoughtReality
"I've done this before, I don't need the checklist"Skills evolve; re-read the current SKILL.md.
"This case is simple"Simple cases become complex mid-task.
"The user didn't ask for this rigor"The user asked for a working result. Rigor is how you get one.

Evidence

Every skill ships with a real before/after pair proving it changes agent behaviour on a concrete task. Without this, the skill is a claim, not a tool.

  • evidence/before.md — a verbatim snippet of what the agent does on a representative task WITHOUT this skill loaded. Include the prompt, the agent's response, and what went wrong (or what got skipped).
  • evidence/after.md — the same prompt with this skill loaded. Show the changed behaviour and why it is better.

If you cannot produce a before/after pair, the skill is not ready to ship. Land it as a draft in a branch, gather the evidence, then merge.

References

  • references/<topic>.md (only if needed; keep the body lightweight)

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.