What are Claude Code skills?

Skills are reusable instruction folders — each contains a SKILL.md file describing a process, plus any supporting resources. Claude Code loads a skill automatically when your request matches its description. Write your procedure once (brand voice, report format, publishing checklist) and every future session follows it without re-explaining.

How do I create a Claude Code skill?

Make a folder under .claude/skills/ in your project, add a SKILL.md file with a name and a description of when to use it, then write the instructions in plain language below. Easier still: ask Claude Code to interview you about your process and write the skill itself, then edit what it drafts.

Do Claude Code skills cost extra?

No. Skills are plain files in your project — there's no marketplace fee or add-on price. They use your existing Claude subscription when they run. The only real cost is the 20 minutes it takes to write down a process you currently keep in your head.

What's the difference between a skill and a slash command?

A slash command is a shortcut you fire deliberately — you type it. A skill is knowledge the AI reaches for on its own when the task matches its description. Commands suit "do this exact thing now"; skills suit "whenever this kind of work comes up, do it our way."

Can I reuse skills across projects?

Yes. Project skills live in that project, but personal skills — kept in the .claude folder of your home directory — are available everywhere you use Claude Code. Your voice guide belongs there; a skill specific to one client project belongs with that project.

Do skills work outside Claude Code?

Increasingly, yes. As of July 2026, Anthropic's skill format also works in the Claude apps and via the API, so a well-written skill travels with you. The format is plain markdown, which is the quiet superpower: readable by you, portable by design, and never locked inside one vendor's dashboard.

Claude Code Skills: SOPs Your AI Actually Follows

You’ve written the perfect prompt. Once. It’s in a chat thread somewhere — three weeks and two hundred conversations ago — and this morning you’re typing your brand voice rules into a fresh session from memory. Again.

If you use AI daily, some version of this is your daily tax.

Claude Code skills are the end of that tax, and they’re the feature I’d point every business builder at second — right after the file-editing paradigm itself.

Searches for them exploded from nothing in under a year, but the tutorials are (as usual) written for developers. Here’s the business-builder version: skills are standard operating procedures your AI actually follows.

What a skill literally is

A folder with an instruction file in it. That’s the whole mystery.

Inside your project there’s a .claude/skills/ directory; each skill is a folder containing a file called SKILL.md with two parts: a short header saying what the skill is called and when it should be used, and then your instructions in plain language.

Claude Code reads the descriptions, and when your request matches one — “draft this week’s newsletter” matching your newsletter skill — it pulls in those instructions automatically. You don’t invoke anything. It just starts doing the job your way.

A minimal real example, so it stops being abstract:

.claude/skills/voice-guide/SKILL.md

---
name: voice-guide
description: How to write anything in my voice.
  Use for every email, post, or page draft.
---

Rules for writing as me:
- Short sentences. Plain words. No hype.
- Never promise income or timelines I haven't lived.
- One idea per paragraph.
- Sign off: "Keep building."

That’s a production-grade skill. No code. The hard part — and this is the honest part — isn’t syntax. It’s sitting down and writing what you actually do, which most of us have never once put into words.

Why skills are the durable layer

Here’s a belief we hold at the Academy, stated as a belief: code is a commodity now — the artifact got cheap. The skill that summons it didn’t.

We call those incantations: the written, refined knowledge of how to direct AI at your business. A skill file is an incantation made permanent. Every correction you fold into it compounds; every session starts smarter than the last.

And notice what skills are made of: markdown. Plain text. Readable by you, editable by you, portable anywhere — as of July 2026 the same skill format works in the Claude apps and API too.

After watching audiences lose a year of platform-specific automation skills to tool churn, I weight this heavily: your SOPs should never live inside somebody’s dashboard. Files you own are the fourth layer of your harness, and they survive every model swap.

Build your first skill in 20 minutes

Pick the process you repeat most.For most solo builders it’s voice: you correct the AI’s drafts the same way every time. Those corrections are the skill.
Don’t write it — dictate it.In Claude Code: “Interview me about how I like my writing to sound — ask one question at a time, at least eight questions. Then create a skill at .claude/skills/voice-guide/ that captures my answers.” (New to Claude Code? Do the first-session walkthrough first.)
Test and tighten.Ask for a short draft on any topic. Where it misses, don’t just fix the draft — say “update the voice-guide skill so that mistake can’t happen again.” That sentence is the whole improvement loop.

The three skills every solo business should have

voice-guide — how you sound, what you never say, how you sign off. Feeds every other skill.
weekly-review — where your numbers live, which ones matter, the format of the Monday summary you actually read.
repurpose — how one piece of long-form becomes platform drafts: lengths, hooks you like, hooks you ban, where drafts get saved for review.

Three files, maybe an hour of honest work, and you’ve converted your taste — the thing that actually differentiates your business — into infrastructure. Honest caveat: expect to revise each one several times over the first month. SOPs are drafts of how you think you work until reality edits them.

Skills vs. commands vs. subagents (30-second tour)

You’ll meet three cousins in the docs. Slash commands are shortcuts you fire on purpose — reusable prompts you trigger by typing.

Skills are knowledge the AI reaches for by itself when the work matches. Subagents are separate workers you can delegate whole jobs to. Start with skills; the others make sense once your skills folder is earning its keep.

In the Academy’s Armory, our deployable Rigs are, under the hood, exactly this: curated skills, agents, and instructions bundled around one business job — battle-tested versions of what you’re starting to build here. If you want to skip ahead to working systems and get feedback on your own, the Academy includes the full Armory at every tier ($83/month or $497/year, 7-day free trial).

Questions people actually ask

What are Claude Code skills?: Skills are reusable instruction folders — each contains a SKILL.md file describing a process, plus any supporting resources. Claude Code loads a skill automatically when your request matches its description. Write your procedure once (brand voice, report format, publishing checklist) and every future session follows it without re-explaining.
How do I create a Claude Code skill?: Make a folder under .claude/skills/ in your project, add a SKILL.md file with a name and a description of when to use it, then write the instructions in plain language below. Easier still: ask Claude Code to interview you about your process and write the skill itself, then edit what it drafts.
Do Claude Code skills cost extra?: No. Skills are plain files in your project — there's no marketplace fee or add-on price. They use your existing Claude subscription when they run. The only real cost is the 20 minutes it takes to write down a process you currently keep in your head.
What's the difference between a skill and a slash command?: A slash command is a shortcut you fire deliberately — you type it. A skill is knowledge the AI reaches for on its own when the task matches its description. Commands suit "do this exact thing now"; skills suit "whenever this kind of work comes up, do it our way."
Can I reuse skills across projects?: Yes. Project skills live in that project, but personal skills — kept in the .claude folder of your home directory — are available everywhere you use Claude Code. Your voice guide belongs there; a skill specific to one client project belongs with that project.
Do skills work outside Claude Code?: Increasingly, yes. As of July 2026, Anthropic's skill format also works in the Claude apps and via the API, so a well-written skill travels with you. The format is plain markdown, which is the quiet superpower: readable by you, portable by design, and never locked inside one vendor's dashboard.