How to create a Claude Code skill, step by step (no coding needed)

You keep typing the same long instructions into Claude Code. Same checklist, same format, same "and don't forget to...". A skill saves those instructions once, so you never type them again.

This guide builds a real one from scratch. It takes about 20 minutes, and you only need a text editor.

🧠 What a skill actually is

A skill is a saved set of instructions that Claude Code loads when it needs them.

Claude works the same way:

• At the start of a session it reads only each skill's name and description.
• When your request matches a description, it reads the full instructions.
• You can also run one on purpose by typing / and its name.

That is why you can have dozens of skills without slowing anything down. New to the idea? What are Claude Code skills? covers the background.

🪜 The four steps

🎯 Step 1: pick the right job

Good first skills share three traits:

• Repeated. You do it weekly or more.
• Same shape each time. The input changes, the steps do not.
• Checkable. You can look at the result and say "right" or "wrong".

Examples that work well:

• Turn messy meeting notes into a summary with action items
• Write release notes from what changed this week
• Check a project for passwords or keys before sharing it
• Rename a folder of invoices to date-supplier-amount

We will build the first one: meeting notes.

📁 Step 2: make the folder in the right place

Where the folder lives decides where the skill works.

The ~ means your home folder:

• Windows: C:\Users\YourName\.claude\skills\
• Mac: /Users/yourname/.claude/skills/
• Linux: /home/yourname/.claude/skills/

Folders starting with a dot are hidden by default. The easiest route is to ask Claude Code itself: "create the folder ~/.claude/skills/meeting-notes".

✍️ Step 3: write SKILL.md

The file has two parts:

• The header between two --- lines. Claude reads this at startup.
• The body below it. Claude reads this only when the skill is used.

Here is the complete file. Copy it into meeting-notes/SKILL.md.

---
name: meeting-notes
description: Turns raw meeting notes into a short summary,
  decisions, and action items with owners and dates. Use when the
  user pastes meeting notes, shares a notes file, or says "tidy my
  notes", "summarise this meeting", or "what are the action items".
---

# Meeting notes

## Steps
1. Read the notes the user gave (pasted text or a file path).
2. Write a summary of at most 3 sentences.
3. List every decision as a bullet, one decision per line.
4. List action items as: owner, task, due date.
   If no owner or date is written, write "unassigned" or "no date".
   Never guess a name or a date.
5. Save the result to notes/YYYY-MM-DD-meeting.md,
   using today's date. Create the notes folder if missing.
6. Show the user the file path and the action item list.

## Done means
- Every name in the action items appears in the original notes.
- Nothing in the summary is missing from the original notes.
- The file exists at the path shown.

## Example
Input: "Sam to send quote by Fri. Agreed blue logo. Budget TBC."
Action items:
- Sam, send quote, Friday
Decisions:
- Blue logo

Why each part is there

• name: matches the folder name. It becomes the /meeting-notes command.
• description: says what it does, then the exact phrases that should trigger it.
• Steps: numbered, one action each. Claude follows numbered steps more reliably than a paragraph.
• "Never guess": names the mistake you most fear. Say it out loud in the file.
• Done means: a checklist Claude can tick before it tells you it finished.
• Example: one tiny before and after beats three paragraphs of explanation.

🔎 The description is the whole game

If Claude never uses your skill, the description is almost always why. Claude only sees the name and description until it decides to open the file.

A strong description has:

• What it does, with a concrete output.
• When to use it, starting with "Use when".
• Trigger phrases in the words you actually type.

🧪 Step 4: test it properly

1. Start a fresh Claude Code session. A new session is the surest way to load a new skill.
2. Ask: "what skills do you have?" Your skill should be in the list.
3. Run it on purpose: type /meeting-notes and paste real notes.
4. Run it by accident: in another fresh session, say "tidy my notes" without the slash. It should still kick in.
5. Check the "Done means" list yourself. Any miss is a wording fix in SKILL.md.

Skill still not showing up or not kicking in? Work through the 9 reasons a Claude Code skill does not trigger, in order.

🚧 Five mistakes that break skills

Long files are the sneaky one. Our own audit found that skill files that grow too long quietly lose steps.

🧰 When a skill needs more than one file

Plain instructions cover most jobs. Add extra files when:

• Reference detail is long: a price list or style guide goes in its own file. SKILL.md says "read prices.md when quoting".
• Steps must be exact every time: renaming 400 files or doing maths belongs in a small script the skill runs.
• It touches other tools: Gmail, Google Sheets, Shopify, a database. Now you need logins, error handling and a safe test run.

That last group is where do-it-yourself usually stalls. The instructions are easy. Making it run reliably against your real accounts is the slow part.

⚖️ Build it yourself, or have it built?

❓ Quick answers

Where do Claude Code skills go?

~/.claude/skills/skill-name/SKILL.md for every project. .claude/skills/skill-name/SKILL.md for one project.

Do I need to code?

No. A skill is sentences in a text file. Scripts are optional.

Why does Claude ignore my skill?

The description. Add what it does, "Use when", and the phrases you type.

How do I run a skill on purpose?

Type / and the skill name, for example /meeting-notes.

Can someone build one for me?

Yes. Godmode's custom build is a fixed $250, scope first, pay after.