Short answer: a Skill is a folder with a SKILL.md file of instructions that Claude loads when a task matches its description [1]. Write one for any job you explain to Claude more than a few times: your proposal format, your weekly report, how you publish a post. Skills know how to do a task. They don't know what's true about your business; that needs a different fix.
What a Skill is
Anthropic's own split: Projects say "here's what you need to know," Skills say "here's how to do things" [2]. A Skill is:
- A folder with a required SKILL.md, plus optional scripts, reference files and assets [1].
- A name and a description at the top. The description is the only part Claude reads before deciding to load the Skill, so it does all the work of getting the Skill used [1].
- Instructions in plain markdown. Anthropic suggests keeping SKILL.md under 500 lines and moving long reference material into separate files it points to [1].
Skills work in the Claude app, Claude Desktop, Cowork, Claude Code and the API [1].
How to create one
- Pick a task you've done at least a few times. A one-off task isn't worth a Skill [1].
- Ask Claude to draft it with the built-in skill-creator Skill, then edit what it produces [1]. Or write SKILL.md by hand.
- Write a specific description. Say when the Skill applies, in the words you'd actually use to ask for the task [1].
- Show the output you expect. An example beats a paragraph of rules [1].
- Upload and turn it on. Zip the folder (the folder itself at the top of the zip), then go to Customize > Skills in claude.ai or the desktop app and turn it on [1]. In Claude Code, put the folder in
~/.claude/skills/[1]. - Test after each change [1].
On Team and Enterprise plans you can share a Skill or publish it to your organization from the same Customize > Skills screen [1].
What Skills can't do
- Reach your other tools. Live data from another service needs a connector, not a Skill [1].
- Hold instructions for every chat. A Skill loads only when a task matches; standing preferences belong in your preferences or project instructions [1].
- Know your company. A Skill for writing proposals still needs your current prices, customers and positioning, and those change. Put them in a Skill and you'll be editing five Skills every time a price moves.
The setup that works: Skills for how, one dated company folder for what. Each Skill says "read the company folder first," and when a fact changes you fix it once.
Do it yourself, or have it done
Chet sets up that company folder (we call it Start) from your own documents, grades your Claude setup, and fixes what breaks. $99 a month, cancel anytime.
Maximize Claude with Chet: https://www.coworkers.global/get-chet?utm_source=blog&utm_medium=internal&utm_campaign=chet&utm_content=what-are-claude-skills-cta
FAQ
What's the difference between Claude Skills and Projects? Projects hold background knowledge for the chats inside them; Skills hold procedures Claude loads when a task calls for one [2].
Do Skills use up my context? Only the name and description sit in context until a Skill is needed; then Claude reads the whole SKILL.md [1]. That's why long material belongs in separate files.
Can I put passwords or API keys in a Skill? No. Everyone you share a Skill with gets its files [1].
Sources
- Claude docs, create custom skills: https://claude.com/docs/skills/how-to
- Claude, Skills explained: https://claude.com/resources/articles/skills-explained
Regards,
Charles Stack
Founder, Coworkers.Global
Coworkers.Global is not affiliated with Anthropic. Claude is a trademark of Anthropic, PBC.