Every time you ask the AI for your weekly report or a quote review, you paste the same ten-step checklist again. A skill keeps those instructions in a SKILL.md file. Then you call it with /name, or Claude picks it up on its own when it needs it.
Who this is NOT for
If you do not use Claude Code yet, do not start here: this only works inside Claude Code, and the page explains how to extend it, not how to get started. You also do not need it if you have not pasted the same instruction at least three times. And if what you want to store is a fact, like your opening hours or your brand's tone, it does not belong in a skill. The documentation keeps skills for procedures, not facts.
Almost nobody notices this difference: whatever you write in CLAUDE.md loads in every conversation, while a skill's body only loads when it is used. That is why a long manual costs almost nothing until you need it. The usual mistake runs the other way: someone discovers skills, creates thirty in a week and forgets them. The documentation itself has a section for finding skills nobody uses, which says a lot. Make one skill for each process you truly repeat, refine it as you use it, and delete it once it stops helping. Note: we could not verify the project's license or star count.
Your first step
Take the instruction you have pasted into the AI most often and save it as .claude/skills/<name>/SKILL.md inside your project. Then type /<name> in Claude Code and check whether it follows it to the letter.
The Claude Code Skills implementation guide
The project belongs to code.claude.com and it is free: the link beside asks for nothing. The guide to set it up without getting lost is ours: step by step, common mistakes and a checklist. Leave your email and we will send it.
No spam. Unsubscribe anytime.