Building a skill for Claude is easier than it sounds. In most cases, your first one takes about 15–30 minutes.
A skill is just a small folder that tells Claude how to handle a specific task, so you do not have to repeat yourself every time.
This is the easiest option. Type this in Claude:
Use the skill-creator skill to help me build a skill for [your use case].Claude will guide you through it.
If you want more control, follow the steps below.
Before you create anything, decide what the skill is for. Ask yourself:
Keep it focused. A narrow skill is usually more useful than a broad one.
Create a new folder on your computer. Use kebab-case:
Goodmy-first-skill
meeting-notes-skillAvoidMeeting Notes Skill
meeting_notes_skillInside that folder, create a file named exactly:
CorrectSKILL.mdIncorrectskill.md
SKILL.MDAlso, do not add a README.md file inside the folder.
Paste this at the top of SKILL.md:
---
name: your-skill-name
description: What it does. Use when user asks to [specific phrases].
---This tells Claude two things: what the skill does, and when it should be used.
Below the YAML, write the actual instructions in Markdown. A good skill usually includes:
---
name: meeting-notes-skill
description: Summarizes meeting notes and turns them into action items.
Use when user asks to organize meeting notes, extract next steps,
or summarize a discussion.
---
# Purpose
Help turn messy meeting notes into a clear summary and action list.
# Instructions
1. Read the notes carefully.
2. Identify key decisions.
3. Pull out action items.
4. Organize the output into summary, decisions, and next steps.
# Examples
User: Turn these meeting notes into action items.
Assistant: [structured summary output]
# Troubleshooting
- If the notes are incomplete, summarize what is clear first.
- If the request is too broad, focus on the main decisions and tasks.Open a new chat and try a request that should clearly trigger the skill. Check these three things: