Skip to content
Mia Automation
NLEN Sign in Put Mia to workGet started

How to Create Claude Skills That Load at the Right Moment

To create a Claude skill, write a folder with a SKILL.md: a description that says what it does and when to use it, a short numbered core, and longer details in separate files. Then test it with requests that should and shouldn't trigger it. Our meeting-notes skill was right on 9 of 10 test requests the first time. One change to the description fixed the miss, and one test run showed a rule we'd forgotten. Here is the whole process, with the files.

Claude in practiceUpdated 5 min read

Tested by us on 11 November 2026.

Animated table filling row by row with ten test requests for the meeting-notes skill: five meant to load it and five not; nine came out right, the recap email request did not load the skill

Step 1: pick one job that comes back

A good skill does one job you'd otherwise explain again and again. Ours turns raw meeting notes into decisions, action items with owners and open questions. It's narrow enough to describe in one sentence, and the output is easy to check against the notes.

Step 2: write the description first

Claude decides whether to load a skill from its name and description alone, so this is the part that matters most. Say what the skill does, then when to use it, in the words people type. Anthropic's limits: a name of at most 64 lowercase letters, numbers and hyphens, without "claude" or "anthropic", and a description of at most 1,024 characters.

Step 3: keep the core short, put details next to it

The body of SKILL.md is read in full when the skill loads. Ours is twelve lines: five numbered steps. The output format lives in TEMPLATE.md beside it, which Claude reads only when step 2 points there. Long reference material, examples and scripts belong in separate files too; they cost nothing until they're opened.

markdown
---
name: meeting-notes
description: Turns raw meeting or call notes into decisions, action items with owners and deadlines, and open questions, or into a recap email built on that structure. Use whenever the user pastes notes from a meeting, call, standup or interview, whatever they want back: actions, a recap or recap email, who does what, or a cleanup.
---

# Meeting notes to actions

1. Read the notes once. Don't add facts that aren't in them, and copy numbers as written: no currency or units the notes don't give.
2. Fill in the structure from `TEMPLATE.md` in this folder.
3. Every action item needs an owner and a deadline. If the notes don't name one, write "owner?" or "deadline?" instead of guessing.
4. For a recap email, put this structure in the body under a one-line greeting.
5. End with one line: "Missing from the notes:" and list what someone should confirm, or "nothing".

meeting-notes/SKILL.md, final version after the tests below.

markdown
## Decisions
- <decision> (<who decided, if stated>)

## Action items
| What | Owner | Deadline |
|---|---|---|
| <action> | <name or owner?> | <date or deadline?> |

## Open questions
- <question>

Missing from the notes: <items or "nothing">

meeting-notes/TEMPLATE.md

PowerShell window on Windows 10: folder .claude\skills\meeting-notes with SKILL.md and TEMPLATE.md, the full SKILL.md with its description and five steps, and a line count of 12 (opens at full size)
Put the folder in .claude/skills/ in a project, or in ~/.claude/skills/ for all your projects.

Step 4: test with ten requests

Write five requests that should load the skill and five that shouldn't, including two near misses: a request that mentions a meeting but isn't about notes, and one that asks for a summary of something else. Run each once with Claude Code and check whether the skill loaded. This script does that for a project skill:

bash
#!/usr/bin/env bash
# trigger-test.sh: run each request once, report whether the skill loaded.
# Usage: ./trigger-test.sh meeting-notes requests.txt   (one request per line)
skill="$1"; while IFS= read -r q; do
  claude -p "$q" --setting-sources project --output-format stream-json --verbose \
    < /dev/null > /tmp/run.jsonl 2>&1
  if grep -q "\"skill\":\"$skill\"" /tmp/run.jsonl; then r=loaded; else r=skipped; fi
  printf '%-8s %s\n' "$r" "${q:0:60}"
done < "$2"

--setting-sources project keeps your personal skills out of the test, so only the skill under test competes.

Claude Code 2.1.321 on Linux, November 11, 2026. Every run took between 2 and 10 seconds.
RoundWhat we changedResult
1First description9 of 10 right. "Write a recap email of this meeting" didn't load the skill.
2Added "or into a recap email" and "whatever they want back" to the descriptionRecap email loaded 3 of 3. Agenda and tagline requests still skipped it.
3Added "copy numbers as written: no currency" to step 1The budget came back as "6000" instead of "€6000".

The mistakes we made

  1. We described the input, not the requests. The first description listed actions and recaps, but a request for a recap *email* didn't match strongly enough. Naming the output people ask for fixed it.
  2. We trusted "don't add facts" to cover numbers. In the first run Claude wrote "€6000" and in the same breath noted that the currency wasn't stated. A general rule didn't stop a specific habit; a specific line did.
  3. We almost skipped the near misses. The agenda request mentions a meeting. It's the kind of request that shows whether a description is too broad, and it stayed unloaded in every run.

One more lesson from earlier tests with another skill: even a good description isn't a guarantee. Across eleven runs, one short request skipped the skill entirely. When the format matters, start the message with /meeting-notes and Claude Code always runs it.

Use the skill in claude.ai too

The same folder works in claude.ai. Zip it with the folder name matching the skill name, then go to Customize > Skills, click +, Create skill and Upload a skill. Code execution has to be on under Settings. Skills don't sync between Claude Code and claude.ai, so upload it again after every change.

Questions

How do I create a Claude skill?

Make a folder with a SKILL.md that starts with name and description, followed by short numbered instructions. Put it in .claude/skills/ for Claude Code, or upload it as a zip in claude.ai.

How long should a skill be?

As short as the job allows. Ours is twelve lines; Anthropic's guidance keeps the body of SKILL.md under 500 lines and moves the rest into separate files.

How do I know when my skill loads?

Test it with requests that should and shouldn't trigger it, and look for the Skill call in the transcript or in stream-json output.

Can a skill include scripts?

Yes. Scripts in the skill folder run when the instructions call them, and only their output enters the conversation.

Sources