<kebab-case-name>
Skill0 starsChanged 5 months agoCC0-1.0View on GitHub
<This line decides whether the skill ever gets read — it matters more than the body. Start with "Use when..." and list concrete trigger situations: when to use it, phrases or contexts that should trigger it, and when NOT to use it.>
1 other project uses a version of this.
Adopted by
Most recently taken up by
- santiment/skillstheir own version, first seen Jun 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- santiment/skills★ 1same 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.
- coreSkill
- skill-coachSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 14
Write instructions, not background ("do X", not "X should be done").
- Distinctive: line 16
Add one line of *why* wherever a rule looks arbitrary.
- Distinctive: line 17
Keep it under ~10 lines / ~500 words.
- Very specific: line 18
When done: add one row to the routing table in core/SKILL.md.
≈ “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.
Files
<skill name> — <one line: what this skill is for>
<!--
How to write the body:
- Write instructions, not background ("do X", not "X should be done").
- Base it on a mistake the AI actually made twice — no speculative rules.
- Add one line of *why* wherever a rule looks arbitrary.
- Keep it under ~10 lines / ~500 words. If it grows, split it in two.
- When done: add one row to the routing table in core/SKILL.md.
-->- <instruction 1>
- <instruction 2>
Out of scope
<state explicitly what this skill does NOT cover>
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
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.

