Skills = Claude Code’s Recipe Book
Aren’t you tired of telling Claude Code the same thing every time? “Use this format for reports, write in English, include tables…”
Skills let you write those instructions once and never repeat them. From then on, Claude just knows. Like giving a chef a recipe once — after that, you just say “make that dish” and it’s done. That’s exactly what Skills are.
| Cooking | Skills |
|---|---|
| Recipe | SKILL.md file |
| Ingredients (flour, butter, etc.) | Supporting files (templates, formats, etc.) |
| Recipe book (collection of recipes) | Skills folder (~/.claude/skills/) |
| Chef | Claude |
| "Make that dish" — one sentence | "Create a report" — one sentence |
One-line summary
Skills = Claude’s recipe book. Create once, and you never need to explain from scratch again.
How Skills Work — Claude Picks What It Needs
Claude doesn’t memorize the entire recipe book. Instead, it remembers just the titles and opens the relevant recipe when you ask for that dish. This saves memory while still letting it work like an expert when needed.
"Oh right, I have a report recipe" — it only remembers skill names and one-line descriptions
Skimming the recipe book cover
"They asked for a report, let me read that recipe" — it reads the full SKILL.md
Opening to that recipe page and reading it
"I need the template file too, let me check" — it references supporting files
Checking referenced materials in the recipe
This is why Skills are efficient
Even with 100 skills, it only reads the ones it needs. Passing all instructions via prompt every time slows things down, but Skills automatically pick and read only what’s relevant, making things fast and accurate.
A Skill Is Just a Folder
At its core, it’s just a folder with files in it. The minimum requirement: 1 folder + 1 SKILL.md file. That’s it!
my-report-skill/
├── SKILL.md ← This is all you need
├── format.md ← (Optional) Reference material
└── template.txt ← (Optional) Template fileSKILL.md is the core. Just having this one file makes Claude recognize it as a skill. Add other files as needed later.
Don't overthink it
One folder, one file = a skill. Start with just SKILL.md, and add reference materials or templates later if needed.
SKILL.md File — What It Looks Like
Let’s look at a real example first, then explain it.
---
name: Daily Report
description: A skill that collects news and creates an English report every morning
---
# Daily Report Rules
## Tasks
1. Collect 5 AI-related news articles
2. Summarize each article in 2 lines
3. Save as report.html
## Rules
- Write in English
- Include the date in the title (e.g., 2026-03-15 AI News)
- Use a clean card layout designThe section between --- markers is the ‘name tag’. Below that is the ‘actual instructions’.
| Section | Role | Example |
|---|---|---|
| name | Skill name — for human readability | Daily Report |
| description | One-line intro — Claude uses this to decide whether to use the skill | A skill that collects news and creates an English report every morning |
| Body below --- | Actual instructions — rules and procedures Claude follows | Tasks, rules, formats, etc. |
The description is the most important part. Claude reads this one line to decide “should I use this skill or not.” The more specific, the more accurately it works.
The format is just Markdown
No special programming language needed. You can create it in any text editor. Copy the example above and change the content — instant custom skill.
Built-in Skills
Claude Code already comes with several built-in skills. No installation needed — ready to use immediately.
Excel Spreadsheets
Just tell Claude:
Create an Excel file from this dataPowerPoint Presentations
Just tell Claude:
Make a PPT from this contentWord Documents
Just tell Claude:
Create a Word document for this reportPDF Forms
Just tell Claude:
Fill out this PDF formThese already exist! Just ask
No installation needed — tell Claude “Make a PPT” or “Analyze this Excel file” and the built-in skills activate automatically.
Skills = Claude’s Recipe Book
Create once, and Claude works like an expert without you explaining from scratch.
Create Your Own Skill — 2 Methods
Method 1: Ask Claude to Do It (Recommended)
The easiest way. Just say this to Claude Code:
Create a daily report skill for me.
It should collect 5 AI news articles every day
and save them as report.html.Claude creates the folder, writes SKILL.md, and it’s done!
Method 2: Create It Manually (4 Steps)
mkdir ~/.claude/skills/my-report-skill
Copy the example above and modify the content
Restart so it recognizes the new skill
"Create a daily report" — if the skill activates, success!
Strongly recommend Method 1
Claude handles everything automatically. Folder structure, SKILL.md writing, testing — all at once. Knowing how to do it manually is nice, but in practice, asking Claude is much faster.
5 Real-World Skills — Here’s What You Can Build
Concrete examples will give you a feel for it. For each skill, we show what to say to Claude and what to put in the SKILL.md.
1. Daily News Briefing
“Summarize AI news for me every morning”
---
name: Daily News Briefing
description: Collects the latest AI news and generates a summary report in English
---
## Rules
- Collect 5 news articles and summarize each in 2 lines
- Save as news-YYYY-MM-DD.html
- Card layout, English2. Weekly Report
“Organize this week’s work into a report”
---
name: Weekly Report
description: Classifies this week's tasks as completed/in-progress/upcoming and writes a report
---
## Rules
- Collect this week's work from git log
- Highlight key achievements and issues
- Save as weekly-report.html3. Email Templates
“Write a customer inquiry reply email”
---
name: Customer Response Email
description: Writes appropriate reply emails by customer inquiry type
---
## Rules
- Polite and friendly tone
- Auto-classify inquiry type (shipping/refund/technical, etc.)
- Structure: greeting → answer → additional info → closing4. Design Guide
“Create in our brand style”
---
name: Brand Design Guide
description: Applies our brand colors, fonts, and layout rules to designs
---
## Rules
- Primary color: #3e6ae1, background: white
- Font: Pretendard, rounded card layout
- Logo always placed top-left5. Meeting Notes
“Organize meeting content and extract action items”
---
name: Meeting Notes Organizer
description: Structures meeting content and extracts action items per person
---
## Rules
- Organize date, attendees, and agenda
- Separate decisions from action items
- Specify assignee + deadlinePick one and build it yourself!
You can copy any example above directly into a SKILL.md, or ask Claude to “create a skill like this.”
Sharing Skills
There are 3 ways to store your skills. Usually option 1 is enough.
Just put it in the ~/.claude/skills/ folder. Skills created in Claude Code are automatically saved here.
To use on the web as well, upload in Claude.ai > Settings > Skills.
On Team/Enterprise plans, admins can deploy skills to the entire team at once.
Option 1 is enough
When you create a skill in Claude Code, it’s automatically saved to ~/.claude/skills/. No need to move or configure anything.
Skills vs MCP — What’s the Difference?
Many people confuse these two, but the chef analogy makes it crystal clear.
Skills = The chef’s recipe book
What Claude knows (internal knowledge). “Write reports in this format,” “Use this tone for emails” — rules and procedures you teach it.
MCP = The tools the chef can use
What Claude can access (external tools). “Send a message on Slack,” “Query the database” — connections to external systems.
Give a chef who knows recipes (Skills) great tools (MCP) and you get the best dishes possible. They’re not competitors — they’re a combination.
| Item | Skills | MCP |
|---|---|---|
| In one word | What Claude knows | What Claude can use |
| Analogy | Chef's recipe book | Chef's tools (oven, mixer, etc.) |
| Setup | Add files to a folder | Connect an MCP server |
| Internet | Not required (local files) | May be required |
| Together | Recipes + tools = perfect automation |
Using both creates synergy
If Skills knows “write Slack messages in this tone” and MCP provides the tool to actually send messages on Slack —recipe + tool combine for perfect automation. Not competition, but combination.
Plugins — Upgraded Version of Skills
A Plugin is Skills + tools bundled as a package. Like installing an app from a smartphone app store, just use /plugin install and you’re done.
For example, installing the Playwright plugin gives you “web automation skills + browser control tools” all at once. More powerful than Skills alone.
# Search for plugins
/plugin search data-analysis
# Install a plugin
/plugin install @anthropic/data-analysis
# Check installed list
/plugin listIf you're still a beginner, Plugins can wait
Plugins are an extension of Skills. Once you’re comfortable with Skills, you’ll naturally start using Plugins. Start with Skills first.
How Skills Have Evolved
Saved frequently used prompts as "/commands" — the precursor to Skills
Systematized as folder + SKILL.md. Works across Claude.ai, Claude Code, and API
Skills + tools bundled into installable/manageable packages
More stable, faster. Monthly updates continue
In just 6 months, it evolved from “saved prompts” to “expert systems.” Understanding Skills now means you’ll naturally keep up with future features as they arrive.
5 Tips for Great Skills
Keep these in mind when creating your first skill.
1. Make the description clear
Claude reads this to decide “use it or not.” “Report skill” is too vague. “Collects AI news daily and creates an HTML report” works much better.
2. One skill = one topic
Don’t cram “reports + translations + emails” into one skill. Separate them into report skill, translation skill, email skill — each works more accurately.
3. Be specific
“Write a good report” is too vague. “3 pages, include tables, summary first, card layout” is better. The more specific, the more accurately Claude follows.
4. Review external skills
Always read the SKILL.md before installing skills made by others. Malicious instructions could be hidden. Stick to verified sources (Anthropic official, etc.).
5. Iterate and improve
It doesn’t need to be perfect from the start. Try it, and if something’s off, edit the SKILL.md. Gradually refine it and it keeps getting better.
Try It Yourself
Pick one of these two exercises.
Exercise 1: Ask Claude to Create It (Easiest)
Copy and paste the following into Claude Code.
Create a skill that automatically generates a weekly report every Monday.
Classify this week's tasks as completed/in-progress/next-week,
and highlight key achievements.Then say “Create the weekly report” to test it. If the skill activates, success!
Exercise 2: Create It Manually (4 Steps)
Follow along in your terminal line by line.
# Step 1: Create skill folder
mkdir -p ~/.claude/skills/weekly-report
# Step 2: Create SKILL.md file
cat > ~/.claude/skills/weekly-report/SKILL.md << 'EOF'
---
name: Weekly Report
description: Organizes this week's work and generates an HTML weekly report
---
## Procedure
1. Collect this week's work
2. Classify as completed/in-progress/next-week
3. Save as weekly-report.html
EOF
# Step 3: Restart Claude Code
# Step 4: Test
claude "Create the weekly report"Verification Checklist
If the skill isn’t working, try making the description more specific. Claude decides whether to use a skill based on its description, so clearer content means better results.
Tips + Sources
When you see a repeated task, make it a skill immediately
If you think “I’m doing this again,” just say “Turn what I just did into a skill.” Claude analyzes the conversation and creates it automatically.
Even better with CLAUDE.md
CLAUDE.md provides project-wide context, Skills provide task-specific recipes. Use both together and Claude knows the context and works expertly.
Start simple, grow complex
Skills get better the more you use them. Start with a simple 3-line skill, then add rules as you go.
Skills = Claude’s Recipe Book
Create once, and Claude works like an expert without you explaining from scratch.
When you see a repeated task, turn it into a skill right away.
| Mistake | Result | Prevention |
|---|---|---|
| Vague description | Skill doesn't activate or triggers at wrong times | Write a specific one-line summary |
| Cramming everything into one skill | Claude gets confused | One skill = one topic |
| Installing unverified external skills | Risk of malicious instructions | Check SKILL.md content before installing |
| Trying to make it perfect from the start | Never getting started | Start simple, iterate |
References
- Anthropic Skills Introduction — anthropic.com/news/skills
- Agent Skills Technical Docs — anthropic.com/engineering/equipping-agents-for-the-real-world-with-agent-skills
- Complete Guide to Building Skills PDF — resources.anthropic.com/hubfs/The-Complete-Guide-to-Building-Skill-for-Claude.pdf
- Anthropic Skills GitHub — github.com/anthropics/skills
- Claude Code Plugins — github.com/anthropics/claude-code/tree/main/plugins
- Claude Code Changelog — github.com/anthropics/claude-code/blob/main/CHANGELOG.md