A skill is an IKEA instruction manual for an AI. That's the whole idea. You hand a model a clear, step-by-step set of instructions for how to do one specific thing, and it follows them.
Not magic. Not a new model. Not a plug-in app store. Just a written set of instructions the AI loads when it needs to do that specific job.
01 / The metaphorThink IKEA, not iPhone app
Imagine you've got a flatpack and a screwdriver. You don't need a smarter screwdriver. You need the instructions. A skill is that. The instructions. For the AI you already have.
02 / What it actually isIt's a text file. Really.
Under the hood, a skill is a SKILL.md file. A regular Markdown document. The top has a few lines of metadata (name, description). The rest is the manual. That's it.
Which means: if you can write a paragraph explaining how you do something, you can write a skill. No code required for the simple ones. The complex ones can pull in scripts and tools, but the spine is always the same. A Markdown file with a clear job.
The shift is from "talking to the AI every time" to "writing the instructions once and letting the AI re-read them whenever the situation comes up." Same effort, repeated forever.
03 / What you'd actually use one forReal examples
This is where it clicks. A few skills I run:
Notice the pattern: repetitive jobs with a clear right answer. That's the sweet spot. Anything you do more than twice a week is a skill candidate.
04 / Where skills liveThe hierarchy (this matters)
Skills don't all live in the same place. They stack, like CSS. The AI checks the closest layer first, then walks outward. Same name in two layers? The closer one wins.
| Layer | Where it lives | Who sees it | Use it for | |
|---|---|---|---|---|
| Project | .claude/skills/ | Just this project | Repo-specific stuff. Build steps. House rules. | |
| Personal | ~/.claude/skills/ | You, everywhere | Your own workflows. Same skill in every project. | |
| Plugin / shared | marketplace plugin | Your team or the public | Skills you ship to others. Versioned. Installable. | |
| Built-in | ships with Claude | Everyone | The defaults Anthropic ships. PDF reading, Excel, etc. |
The practical version: start at the personal layer (the one in your home folder). It follows you across every project. Once a skill earns its keep there, you'll know whether to push it into a specific project or share it as a plugin.
05 / Why custom beats off-the-shelfThe honest take
You can install other people's skills. They're fine. They'll get you 70%.
But the real unlock is this: nothing is ever going to be as good as a skill built exactly for you. Your tone. Your tools. Your shortcuts. Your sequence. The way you like the email written.
The first skill you build feels like a toy. The tenth one feels like leverage. By the fiftieth, you stop thinking about "using AI" and start thinking about what you want done.
06 / Where skills come fromInstall, share, or write your own
You're not limited to skills you write yourself. There's a growing ecosystem of shared ones. The honest map:
~/.claude/skills/.One thing to be aware of, though. A skill is just text. Whoever wrote it can say anything in those instructions. Most of the time it's helpful. Sometimes it's careless. Rarely, it can be hostile (prompt injection, asking the model to do something you didn't intend).
07 / Where to go nextThe official docs
If you want to dig into how to actually write one, the Anthropic docs are short and good:
→ claude.com/skills (the overview).
→ support.claude.com: What are skills? (the FAQ-style explainer).
That's the whole 101. Now go build one.
Get the next one in your inbox.
I write about the AI tools I'm testing, what just shipped, and what's actually worth your time. Weekly, no fluff.
Subscribe to the newsletterOr join the community of AI builders and creators. DMs, AMAs, and behind-the-build.