What Are Claude Code Skills? A Plain-English Guide (With Book Examples)

Search "claude code skills" and you'll get GitHub repos, config docs, and threads full of people talking past each other. Almost nobody explains the basic thing plainly: what a skill actually is, and why you'd want one.

Here's the short version. A skill is a file that teaches your AI assistant a repeatable workflow — a procedure it follows every time, with your situation as the input. Instead of prompting from scratch and hoping, you run a command and the assistant walks you through a proven framework step by step, asking questions and producing a concrete output.

The mechanics: one file, loaded on demand

A Claude Code skill lives in a folder on your machine:

~/.claude/skills/<skill-name>/SKILL.md

That SKILL.md file contains the workflow: what the skill does, the steps it runs, the questions it asks you, and the format of what it produces. Claude Code loads it when you invoke it, so a library of fifty skills doesn't slow down or clutter your everyday chats — each one only wakes up when called.

Skills surface as slash commands. Type the command, answer the questions, get the output. That's the whole interaction model, and it's why skills beat saved prompts: a prompt is a paragraph you paste and then improvise around; a skill is a procedure the assistant executes the same way every time.

Installing one takes under five minutes. Download the skill file, create its folder, move the file in as SKILL.md:

mkdir -p ~/.claude/skills/atomic-habits
mv ~/Downloads/atomic-habits.md ~/.claude/skills/atomic-habits/SKILL.md

The full walkthrough, including setup for Claude, ChatGPT, and Gemini, is in the setup guide.

What makes a good skill

Not every document deserves to become a skill. The best raw material has three properties:

1. A procedure, not just ideas. Steps, exercises, checklists — something you do, in an order.
2. Personal inputs. The workflow has to run on your numbers, your habits, your team — otherwise it's just an article.
3. A defined output. A plan, a scorecard, a script, a decision — something you walk away holding.

Which is why business and self-improvement books are nearly perfect source material. A good business book is a procedure wearing a narrative costume: the chapters are steps, the exercises are inputs, the frameworks are outputs. Reading extracts the story. A skill extracts the procedure and runs it on your life.

Example: Atomic Habits as a skill

James Clear's Atomic Habits is built on the 4 Laws of Behavior Change, and its exercises map one-to-one onto commands. The Atomic Habits skill has seven:

• /habit-scorecard — list your current habits and score each one: effective, ineffective, or neutral. Awareness before change.
• /habit-stack — attach a new habit to one you already do reliably, using Clear's stacking formula.
• /habit-audit — a structured review of what's actually running your day.
• /environment-design — redesign your surroundings so good habits are obvious and bad ones are invisible.
• /two-minute-rule — shrink any new habit to a version that takes two minutes, so starting is never the bottleneck.
• /identity-shift — reframe the habit around the person you're becoming, not the outcome you're chasing.
• /habit-tracker — set up the tracking loop that keeps the system honest.

Run /habit-scorecard and you're not reading about someone else's morning routine — you're scoring your own, and the assistant pushes back where your scores are generous. That pushback is the part a book can never give you.

It's free, and there's no signup: download it, drop it in the folder, run it. It's the fastest way to understand what a skill feels like from the inside.

Example two: diagnosing instead of building

Charles Duhigg's The Power of Habit is the diagnostic counterpart — where Clear builds habits, Duhigg dissects them. Its skill leads with /habit-loop-decode: pick a habit you want to change, and it walks you through the cue, the routine, and — the hard part — the real reward driving the loop. The Power of Habit skill is $7 one-time, and pairing the two is the standard play: decode the loop with Duhigg, build the replacement with Clear.

Can you just write your own?

Yes — honestly. A skill is a markdown file; nothing stops you from opening a book, extracting its exercises, and writing your own SKILL.md. People do it, and for a single framework you love, it's a fine weekend project.

The catch is arithmetic. A good skill takes hours to write and test per book: extracting the procedure, sequencing the questions, tuning the outputs. Most people who want to use frameworks from ten or twenty books will never spend ten or twenty weekends building them. That's the entire reason BookSkills exists — done-for-you curation for people who'd rather run the frameworks than manufacture them.

The catalog currently holds 43 book skills — habits, negotiation, productivity, strategy, finance — each one the full command set from the book, not a summary. Singles are $7 one-time. Annual Access unlocks all 43, plus every future release, for $79.99/year — the math wins as soon as you'd use a second book.

Start where everyone starts: the free Atomic Habits skill. Five minutes from now you'll know exactly what a Claude Code skill is — because you'll have run one.