make-skill
Skill2 starsChanged 22 days agoMITView on GitHub
Create a new Claude Code skill, either by interviewing me about a job or by capturing a task we just did in this conversation. Use when I say /make-skill, "make a skill", "turn this into a skill", "save this as a skill", or "I keep explaining this".
8 other projects use a version of this.
Adopted by
Most recently taken up by
- diegoos/skillstheir own version, first seen Nov 8, 2026
- Sharqiewicz/skillstheir own version, first seen Nov 8, 2026
- sevenevesai/skillstheir own version, first seen Nov 1, 2026
- sohaibdevv/project-templatetheir own version, first seen Oct 9, 2026
- dotnet/efcoretheir own version, first seen Oct 8, 2026
- sergeyklay/.agentstheir own version, first seen Sep 28, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- dotnet/efcore★ 15ksame name
- sergeyklay/.agents★ 6same name
- daveebbelaar/project-template★ 4same name
- diegoos/skills★ 3same name
- sohaibdevv/project-template★ 2same name
- Sharqiewicz/skills★ 1same name
- qiaoruntao/skills★ 0same name
- sevenevesai/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 repository15 other files it gives its agents.
- bankSkill
- build-toolSkill
- busy-workSkill
- freebieSkill
- idea-vetSkill
- linkedin-engageSkill
- post-weekSkill
- seat-templateSkill
- ship-skillSkill
- sparSkill
- validate-accuracySkill
- vid-batchSkill
- week-planSkill
- written-redraftSkill
- x-engageSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
8
Distinctive
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 13
If we just finished a task in this conversation and I say "turn this into a skill", capture it: pull the steps that actually worked, the …
- Distinctive: line 26
Write the description as: what it does, then "Use when I say" plus the trigger phrases, including the plain-English ways I'd ask, not just …
- Distinctive: line 28
Write the body: one line on the goal, the steps as a numbered list, the good example, then a "Never" list.
- Distinctive: line 30
Keep it under 80 lines. If it needs a template or a checklist, put that in a separate file in the same folder and tell the skill when to …
- Distinctive: line 38
If it doesn't fire, the description is wrong.
- Distinctive: line 42
Never write a skill for a one-time task.
- Distinctive: line 43
Never pad the body with general advice Claude already follows.
- Distinctive: line 44
Never overwrite an existing skill without asking.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Make a skill
You write skills for me. A skill is one folder with one SKILL.md in it. The description decides when it loads, so most of your effort goes there.
Pick the mode
- If we just finished a task in this conversation and I say "turn this into a skill", capture it: pull the steps that actually worked, the corrections I made, and the final output.
- Otherwise, interview me. Ask these one at a time, and wait for each answer:
- What's the job, in one sentence?
- What would I type or say when I want it? Give me three ways.
- What are the steps, in order?
- What does a good result look like? Paste one if you have it.
- What should it never do?
Write it
- Pick a short lowercase name with hyphens. Check
~/.claude/skills/first, and if the name is taken, ask me before overwriting anything. - Write the description as: what it does, then "Use when I say" plus the trigger phrases, including the plain-English ways I'd ask, not just the slash command.
- Write the body: one line on the goal, the steps as a numbered list, the good example, then a "Never" list.
- Keep it under 80 lines. If it needs a template or a checklist, put that in a separate file in the same folder and tell the skill when to read it.
- Save it to
~/.claude/skills/<name>/SKILL.md. - Show me the finished file and the path you saved it to.
Test it
Tell me to open a fresh session and ask for the job in plain words, without the slash command. If it doesn't fire, the description is wrong. Add the words I actually used and save again.
Never
- Never write a skill for a one-time task.
- Never pad the body with general advice Claude already follows.
- Never overwrite an existing skill without asking.
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.