What a Skill Actually Is
The core idea behind a Claude Code Skill: a saved packet of know-how that gets pulled out only when the matching kind of task comes up.
A recipe card, not a cookbook memorized cover to cover
Imagine a chef who keeps a small box of recipe cards on the counter instead of trying to hold every recipe in their head at once. Most of the time the box just sits there. But the moment someone orders the dish on one of those cards, the chef pulls exactly that card, follows it, and puts it back. The rest of the kitchen's knowledge stays quietly out of the way until it's actually needed.
A Skill works the same way inside Claude Code. It's a saved set of instructions for handling one particular kind of task well, written once, kept in a folder, and read only when a task that matches comes up. The rest of the time, it isn't taking up any space in the conversation at all.
Why this beats explaining it every time
Without something like a Skill, doing a specialized task well means either re-explaining the specifics every single time ("here's exactly how we review a pull request on this team," "here's our checklist for deploying") or hoping the same quality happens to come out again by chance. Neither scales. A Skill fixes this by making the good version of the instructions permanent and reusable: write the recipe card once, and every future dish that matches it starts from the same solid instructions.
It's not code, and it's not magic
A Skill isn't a program that runs by itself, and it isn't some hidden capability being unlocked. It's closer to a very well-written note left for a capable assistant: here's what this kind of task usually needs, here's the order to do things in, here's what to watch out for. Claude still does the actual work and still has to use good judgment. The Skill just means it isn't starting that judgment from zero every time.
A Skill describes how to do something well. It doesn't do the thing by itself the way a script would. The difference matters: a Skill can say "check for X, then do Y, unless Z," and rely on judgment to apply that sensibly, in a way a rigid automated script can't.
Think of something you or your team explains from scratch almost every time it comes up: a checklist before shipping, a specific way of writing a certain kind of document, a review process with steps people always forget. That's exactly the shape of task a Skill is built for. Keep it in mind, later chapters build one for real.