SKILL_NAME
Skill0 starsChanged 5 months agoMITView on GitHub
One or two sentences a model uses to decide WHEN to trigger this skill. Lead with the job to be done, then the trigger phrases ("draw a diagram", "audit security"...), then what it is NOT for. Be concrete — this string is the whole routing signal.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- navjyotnishant/nj-agentstheir own version, first seen Oct 15, 2026
- thijsvos/Claude_Skillstheir own version, first seen May 14, 2026
- openmetaloom/skillstheir own version, first seen Feb 5, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- openmetaloom/skills★ 2same name
- navjyotnishant/nj-agents★ 1same name
- thijsvos/Claude_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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- annotateSkill
- debug-loop-breakerSkill
- deploy-checklistSkill
- goalSkill
- growth-playbookSkill
- security-scannerSkill
- seo-auditSkill
- svg-diagramSkill
- tdd-disciplineSkill
- teaching-modeSkill
- verify-frontend-changeSkill
The file
Files
SKILL_NAME
One-paragraph statement of what the skill produces and the single most important rule for using it well.
When to use
- Bullet the concrete situations that should trigger this skill.
- And the ones that should NOT (point at the right alternative).
How it works
The steps a model follows. Keep them ordered and verifiable. If the skill ships scripts, show the exact command (relative to the skill folder, never an absolute machine path).
Quality checklist
Binary pass/fail checks to run before calling the output done.
Gotchas
The hard-won edge cases. Every time this skill hits a new failure mode, add a line here — this section is why the skill beats an ad-hoc prompt.
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.

