{{skill-name}}
Skill0 starsChanged 32 days agoMITView on GitHub
<!-- TODO(project): what this covers and when to use it, with trigger words. --> Use when the task involves …, …, or …. Trigger when the user mentions "…", "…" or "…". Do not use for … (see skill `…`).
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ellmos-ai/skillstheir own version, first seen Sep 11, 2026
- LOUSANPANG/agent-skillstheir own version, first seen Sep 2, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ellmos-ai/skills★ 4same name
- LOUSANPANG/agent-skills★ 2same 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.
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
- Distinctive: line 18
Writing: read the decision matrix, then run the checklist on the draft.
- Distinctive: line 19
Do not over-correct tiny changes.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 title}}
<!-- TODO(project): one paragraph: what this is, the one principle behind it. -->How to use
- Writing: read the decision matrix, then run the checklist on the draft. Do not over-correct tiny changes.
- Reviewing: scan against the checklist, flag, propose a rewrite.
- Apply silently; mention this skill only when explaining a concrete change.
Decision matrix
| Situation | Use | Not |
| … | … | … |
Canonical references
Name
What it is for, its props or signature, the one thing people get wrong.
Checklist
- …
- …
- …
Anti-patterns to fix on sight
| Smell | Fix |
| … | … |
Out of scope
- …
References
references/<topic>.md— …
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.