Claude Code skills are folders of instructions, scripts, and resources that Claude Code discovers and activates on its own when your task matches — so your AI coding agent stops forgetting your stack, conventions, and workflow between sessions. You explain your preferences once; Claude applies them every time, without being reminded.
This guide covers what Claude Code skills are, the two kinds you'll use, how they auto-activate, where they live, and a battle-tested workflow for shipping real features with them.
The problem they solve
AI coding assistants forget everything between conversations. Without help, you re-explain your framework, your folder structure, your naming rules, and your review standards in every new session. A skill captures that knowledge once, so Claude Code follows your conventions consistently instead of defaulting to generic patterns that produce "AI slop."
The two kinds of Claude Code skills
- Capability uplift — skills that give Claude new abilities it didn't have: things like document generation, web app testing, or scraping. They extend what the agent can do.
- Encoded preference — skills that make Claude execute your way: frontend design rules, React best practices, your team's commit conventions. They constrain how the work gets done.
Most developers end up with a mix: a few capability skills for new powers, and several preference skills that enforce house style.
How they activate
You don't have to call a skill by name. Claude Code watches the conversation and activates a skill on its own when what you describe matches the skill's description. Mention reviewing code for vulnerabilities, and a security-review skill can fire automatically; ask for a component, and your React-standards skill kicks in. The description in each skill's SKILL.md is what controls this, which is why writing a sharp description matters more than anything else.
Where Claude Code skills live
Skills sit in a skills directory and load at startup:
-
Personal:
~/.claude/skills/<name>/— available across all your projects. -
Project:
.claude/skills/<name>/— committed to the repo so the whole team shares it.
Confirm a valid SKILL.md sits at the folder root, restart Claude Code, and run /skills to verify it loaded. Installing a packaged skill is often just unzip skill.zip -d ~/.claude/skills/.
A proven workflow: research → plan → implement
The most reliable way to ship a non-trivial feature with Claude Code is to separate thinking from typing:
-
Research. Ask Claude to map the relevant code first — existing patterns, dependencies, and extension points — into a short
research.md. No code yet. - Plan. Have Claude draft a plan with no implementation. Open it in your editor, annotate everywhere it's wrong, then send it back with: "address all notes, don't implement yet." Repeat until every decision is resolved.
- Implement. Only now let Claude write code, following the agreed plan.
A "feature-dev" preference skill can encode exactly this loop so it runs the same way every time — which is the whole point of skills: turning a good workflow into a repeatable one.
Where to get Claude Code skills
You can write your own, or install ready-made ones. If you'd rather start from tested files, browse the Claude Code skills collection or the broader Tech & Development library. New to skills entirely? Start with how to install a Claude Skill or grab a free skill to see the structure.
Frequently asked questions
Do I have to invoke a Claude Code skill manually?
No. Claude Code activates a skill automatically when your task matches its description. You can also reference one explicitly, but the auto-trigger is the main benefit.
What's the difference between personal and project skills?
Personal skills in ~/.claude/skills/ follow you across all projects; project skills in .claude/skills/ live in the repo so your whole team uses the same ones.
Why isn't my skill triggering?
Usually the description is too vague. Make it specific about when to use the skill, confirm a valid SKILL.md is at the folder root, restart Claude Code, and run /skills to verify it loaded.
Are Claude Code skills the same as MCP?
No. Skills teach Claude how to work; MCP connects Claude to external systems. Many setups use both.
Start with one skill
Pick the part of your workflow you re-explain most — your stack, your review rules, your commit style — and encode it. Browse the Claude Code skills collection for tested starting points, or read what Claude Skills are first.