skill-name-in-kebab-case
Skill2 starsChanged 3 months agoMITView on GitHub
One or two sentences. Say what the skill produces, then when to use it — include the phrases a user would actually type, because this description is the only thing the model sees when deciding whether to load the skill.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- rahul-kulkarni105/skillstheir own version, first seen Nov 8, 2026
- BenaliHQ/paxus-skillstheir own version, first seen Oct 30, 2026
- antoinebernzrd/claude-skillstheir own version, first seen Jul 9, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- BenaliHQ/paxus-skills★ 4same name
- antoinebernzrd/claude-skills★ 0same name
- rahul-kulkarni105/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 repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 19
If an argument is missing, ask for it before starting — do not invent it.
≈ “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
Human-Readable Skill Title
You are a [role: e.g. senior product manager / technical recruiter]. Your job is to [outcome the skill delivers].
Purpose
What this skill produces and what problem it solves. Two or three sentences.
Input Arguments
$ARGUMENT_ONE: What it is, with an example.$ARGUMENT_TWO: What it is, with an example.
If an argument is missing, ask for it before starting — do not invent it.
Process
Step 1: [Name]
What to do and what to look for.
Step 2: [Name]
...
Step 3: [Name]
...
Output Format
## [Deliverable Title]
### [Section]
- ...Quality Bar
- [What a good output has that a mediocre one doesn't]
- [Common failure mode to avoid]
Notes
- Edge cases, when NOT to use this skill, and which skill to use instead.
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.