What Are Claude Code Skills
What Are Claude Code Skills
Claude Code Skills are reusable instruction packages that teach Claude how to perform specific tasks within Claude Code.
A Skill is defined by a SKILL.md file containing structured instructions, context, and examples. When you reference a Skill, Claude reads these instructions and applies them to your current task.
Claude Code Skills Explained in Plain English
Think of Skills as specialized recipe cards for Claude.
Without Skills:
> "Claude, create a React component with proper TypeScript types and accessibility."
Claude must infer best practices from general training.
With Skills:
> Use Skill: /frontend-react-component
Claude loads specific instructions covering:
- TypeScript strict mode requirements
- Accessibility attribute patterns
- Component structure conventions
- Testing expectations
The key difference: Skills provide consistent, repeatable instructions across projects. Your team can standardize on the same patterns by sharing Skill files.
How Claude Code Skills Work Under the Hood
Skills are plain text Markdown files with a specific structure.
Basic workflow:
- You create or install a SKILL.md file — Claude Code currently documents personal skills in
~/.claude/skills/<skill-name>/SKILL.mdand project skills in.claude/skills/<skill-name>/SKILL.md. - You reference the Skill — Claude uses skills when relevant to your task, or you can invoke one directly with
/skill-name. - Claude Code loads the Skill instructions — Reads the SKILL.md file, injects instructions into context, and applies guidance to your task.
- Claude generates output following Skill rules — Uses patterns defined in SKILL.md, follows examples and constraints, and maintains consistency across similar tasks.
Claude Code Skills vs MCP Servers: Key Differences
Skills and MCP Servers serve different purposes.
Claude Code Skills:
- Purpose: Instruction templates and workflow patterns
- Format: Markdown files with guidance and examples
- What they do: Tell Claude how to approach tasks
- Example use: "Always use TypeScript strict mode in React components"
- Storage: Markdown files, version-controlled
- Execution: Passive (guidance for Claude's generation)
MCP Servers:
- Purpose: External tool integration and data access
- Format: Executable programs exposing tools via MCP protocol
- What they do: Give Claude capabilities to execute actions
- Example use: Query a database, read files, call APIs
- Storage: Installed as packages or services
- Execution: Active (Claude calls tools to perform operations)
Analogy:
- Skills = Cookbooks (instructions on how to cook)
- MCP Servers = Kitchen appliances (tools to execute tasks)
You use both together:
A Skill might instruct Claude to "always check database schema before writing queries," while an MCP Server provides the actual database connection to execute those queries.
How to Get Started with Claude Code Skills
Start using Skills in three steps.
Step 1: Check for official Skills
Anthropic has published an official public skills repository. The public repository includes examples of skill structure and patterns.
The official starting point is Claude Code's skills documentation, which covers bundled skills, personal skills, and project skills.
- Bundled skills that ship with Claude Code
- The public skills format and frontmatter model
- Current placement rules for personal and project skills
Step 2: Create or install a Skill
Create the skill in ~/.claude/skills/<skill-name>/SKILL.md if you want it across projects, or in .claude/skills/<skill-name>/SKILL.md if you only want it inside the current repo.
Step 3: Reference the Skill
Claude uses skills when relevant, or you can invoke one directly:
/my-skill-name
Create a user authentication module following our standard patterns.Claude Code loads the Skill instructions and applies them to your request.
Tips for getting started:
- Start with simple, focused Skills (one task type per Skill)
- Use existing code in your project as examples within SKILL.md
- Share Skills with your team through version control
- Iterate on Skill instructions based on actual usage
Claude Code Skills in a Real Team Setup
Claude Code skills become tangible when teams use them to package repeatable workflows instead of relying on ad hoc prompting.
What this shows: This screenshot uses the Claude Code repository as a grounded example of the kind of project context where reusable skills actually matter.
Why this scenario matters: It turns the concept into something concrete: skills matter because teams use them to package repeatable agent behavior around real project work, not one-off prompts.
Typical assistant task: Package repeatable agent behavior so teams can reuse proven coding workflows instead of reprompting every task.
Source: Claude Code Repository
When to Pick What Are Claude Code Skills vs Cursor Rules
This comparison is most useful when both options look plausible on paper but differ in operating model, team fit, and day-to-day workflow cost.
| Decision Lens | This Page's MCP Path | Competitor |
|---|---|---|
| Best For | Teams trying to understand skills as reusable operating units rather than one-off prompt tricks. | Teams that primarily need broad behavior guidance and persistent policy around coding assistants. |
| Where MCP Wins | Claude Code skills win when the value comes from packaging repeatable workflows into explicit reusable units. | |
| Tradeoff to Watch | They are more opinionated than rule files, which may be enough if you only need consistent guardrails. | |
| Choose This Path When | Choose Claude Code skills when reusable workflow packaging matters; choose Cursor Rules when broad behavior policy is enough. | |
| Sources | ||
Frequently Asked Questions
Are Skills the same as prompts?
Do I need to be a prompt engineer to create Skills?
Can Skills call MCP servers?
Are there official Skills from Anthropic?
How many Skills can I have?
Do Skills work in Claude Desktop?
Can Skills conflict with each other?
Use Skills in Verdent
Verdent provides pre-configured Skills for common development workflows.
Access curated Skills for frontend frameworks, API design, testing patterns, and documentation without manual SKILL.md creation. Skills are available immediately across all Verdent projects.