Claude Code Skills: Teach Claude Your Playbooks

Claude Code skills are saved playbooks: small text files that teach Claude a procedure once so you never paste the same instructions twice. You write a file called SKILL.md, drop it into a folder, and from then on Claude either loads it automatically when the task matches or runs it the moment you type /skill-name.

I think of a skill as a recipe card taped inside a kitchen cabinet. It does not clutter the counter (your context window) all day. It only comes out when you cook that exact dish. That detail matters more than anything else in this guide: a skill costs almost nothing until the moment it is used, so you can grow a whole skills library without slowing Claude down. No skills marketplace shopping spree required to start, either — your first skill is five lines of text.

What is a Claude Code skill, exactly?

If you searched for «Claude Code skills что это» or wondered what these things are: technically, a skill is a folder containing one SKILL.md file. The file has two parts. At the top sits a short header (called frontmatter) between two --- markers — it tells Claude when the skill is relevant. Below it go plain instructions in normal language. The folder name becomes the command you type: a file at ~/.claude/skills/weekly-report/SKILL.md gives you /weekly-report. Personal skills in ~/.claude/skills/ work in all your projects; project skills in .claude/skills/ apply to one project; skills shipped inside plugins get a prefix like /plugin-name:skill-name so names never clash.

Do skills actually work in Claude Code?

Yes — they are a first-class feature, not a hack. Claude Code even ships with bundled skills like /code-review, /debug and /loop, available in every session. There are two trigger paths: Claude reads your skill descriptions and loads one automatically when your request matches, or you invoke one directly by typing slash plus its name. One more thing that confuses people coming from older tutorials: custom slash commands have been merged into skills. A file in .claude/commands/ still works, but a skill folder does the same job and adds extras, like supporting files and control over who is allowed to trigger it.

How do you create and add skills to Claude Code?

mkdir -p ~/.claude/skills/meeting-notes

---
description: Turn raw meeting notes into action items. Use when
  the user pastes notes or asks for follow-ups.
---
From the notes provided, produce:
1. A three-line summary
2. Action items, each with an owner
3. Open questions nobody answered

What skills should you add to Claude Code first?

Skip the «best Claude Code skills» listicles for a week and mine your own chat history instead — the skills best practices crowd agrees on this one. Good first candidates: a writing-voice skill (how you sound, what words you ban), a formatting skill for reports or posts, and a /summarize-changes skill that explains what changed in your project in human language. Three power-ups worth knowing as you go. First, $ARGUMENTS lets a skill accept input: a /fix-issue skill with «Fix issue $ARGUMENTS» inside runs as /fix-issue 123. Second, disable-model-invocation: true in the frontmatter means only you can trigger the skill — Claude cannot fire it on its own, which is exactly what you want for anything with side effects, like publishing. Third, allowed-tools pre-approves specific tools while the skill runs, so Claude stops asking permission for the same safe command ten times.

How is Claude Code so good at coding?

People ask how Claude Code got so good, and a big part of the answer is context discipline: it loads detail only when needed. Skills follow the same philosophy. Only the short description sits in memory by default; the full playbook loads on invocation. That is why the docs recommend keeping SKILL.md under 500 lines and moving long reference material into supporting files inside the skill folder, linked from the main file. Among Claude Code skills examples in the official docs, even a full codebase-visualizer skill keeps its SKILL.md tiny and ships the heavy lifting as a bundled script.

The meta-move that ends this guide: tell Claude — «Watch what I keep asking you to do, then propose three skills with ready SKILL.md files». The best skills library is not downloaded from GitHub. It is distilled from your own repetition.