How to write a Claude skill. A working example in two files and a first test

We write a small skill from scratch that turns meeting notes into a summary in the company format. You get the SKILL.md, a supporting file, a test in Claude Code and Anthropic's rules that make Claude reach for the skill at the right moment.

Part of the guideClaude Code, the complete guide. From installation to your own skills and plugins

In this article
  1. How to write a Claude skill, step by step
  2. How to test the skill in Claude Code
  3. Anthropic's rules that make the biggest difference
  4. Skill-creator, a skill for writing skills

In short

You write a Claude skill as a folder with a SKILL.md file, where the header says when to use it and the rest says what to do. We show a working example in two files, a test in Claude Code and the rules from Anthropic's docs. Most of the result depends on one sentence in the description field.

After every client meeting someone retypes messy notes into the same layout. Who was there, what we agreed, who does what and by when. That makes a perfect first skill. The task comes back every week, it has a fixed format, and you can easily tell whether the result is right. Below we write it from scratch and show how to write a Claude skill so that Claude actually uses it.

We follow the Claude Code skills docs and Anthropic's skill authoring best practices, as of 10 November 2026. If you are not sure what a skill is yet, start with what is a Claude skill. The whole series is collected in our Claude Code guide.

How to write a Claude skill, step by step

The skill will have two files. SKILL.md with the instructions and template.md with the summary layout. We build it in Claude Code as a personal skill, which works in all your projects.

  1. Create the skill folder with mkdir -p ~/.claude/skills/meeting-notes in a terminal.
  2. Save a SKILL.md file in it with the content below.
  3. Save template.md with the layout next to it.
  4. Run claude in any folder and test the skill as described further down.
SKILL.md
---
name: meeting-notes
description: Turns raw meeting notes into a summary in the company format. Use when someone pastes notes from a meeting, asks for a recap of a client call or for a list of decisions and action items.
---

Write the meeting summary using the layout in template.md.

Rules
- Write only what is in the notes. Do not add decisions or dates.
- Every action item has an owner and a due date. If there is no date, write no date.
- Copy amounts and dates exactly as they appear in the notes.
- At the end, list the questions the notes leave open.
template.md
# Meeting with CLIENT, DATE

Present
Decisions
Action items, owner, due date
Open questions

The name may contain only lowercase letters, numbers and hyphens, at most 64 characters, and must not include the words anthropic or claude. In Claude Code the name field is even optional, because the folder name becomes the name. We set it anyway, since the same skill may later go to the Claude app.

template.md takes no room in the conversation until the skill needs it. Claude opens it because SKILL.md names it directly. Every supporting file works this way, including a script, of which only the output enters the conversation.

How to test the skill in Claude Code

First check that Claude sees the skill at all. Type /skills or simply ask which skills are available. Then test it two ways. Once, paste some notes and say in plain words that you want a summary. Claude should pick the skill on its own, because the request matches the description. The second time, type /meeting-notes and paste the notes.

Claude Code watches the skills folder, so after a fix in SKILL.md you do not need a restart. For testing, though, open a fresh session each time. The docs point out that leftover context from writing the skill can hide gaps in the instructions themselves.

If the skill does not trigger, the problem almost always sits in the description. It lacks the words you really use when you ask for this task. When the header has a syntax error, the skill still runs with a slash, but Claude does not see the description and will not pick it on its own. The command claude plugin validate ~/.claude/skills, run in a normal terminal, checks the headers of all personal skills, from version 2.1.233.

Anthropic's rules that make the biggest difference

Write the description in the third person and be specific. It should say what the skill does and when to use it, with the words you use day to day. Anthropic gives a description along the lines of helps with documents as a bad example.

Keep it short. Anthropic assumes Claude is already very capable, so a skill should hold only what Claude does not know. Your template, your rules, your exceptions. Try to keep the SKILL.md body under 500 lines and move longer material into separate files linked directly from SKILL.md, without chains from one file to the next.

Put the most important rules at the top. When a conversation is summarized to free up room, Claude Code keeps only the first 5000 tokens of each skill that was used. Write paths with forward slashes, on Windows too.

A skill that changes something outside, such as sending a message or publishing a page, is better run only by hand. The line disable-model-invocation: true in the header does that. Claude will then not start it on its own, even if it thinks it fits.

If the same skill should work in the Claude app, keep in mind the limit the Help Center gives there. The description can have at most 200 characters.

Skill-creator, a skill for writing skills

Anthropic offers skill-creator, which helps write and improve skills. In Claude Code you install it as a plugin from the official marketplace.

/plugin install skill-creator@claude-plugins-official

After installing it, ask Claude to evaluate an existing skill. Skill-creator stores test cases in evals/evals.json, runs each one in a clean context with and without the skill, compares the results and suggests a better description if the skill fires on the wrong requests. How plugins work is explained in Claude Code plugins, and ready skills to learn from are in official Claude skills.

Start with one task you already do from a template, and add to the skill only what Claude gets wrong without it. If you want to see which tasks like that in your company are worth handing to AI, our free AI audit looks at where AI can take work off your team.

Documentation for this topic

What would you like to change in your business?

Leave your number. We will talk about your process and see whether we can help. The first call is free.

When is the best time to call?
Controller: Oleksandr Bondarenko (BondSoft)Privacy PolicyTerms of Service
Legal details

The data controller is Oleksandr Bondarenko, trading as Oleksandr Bondarenko Software Solutions (BondSoft), ul. Jana Heweliusza 11, 80-890 Gdańsk, Poland, NIP 5833576264, e-mail: office@bondsoft.pl.

We process your data solely to contact you about your enquiry and to present an offer — on the basis of your consent (Art. 6(1)(a) GDPR and Art. 398 of the Polish Electronic Communications Law) and our legitimate interest in handling the enquiry (Art. 6(1)(f) GDPR).

Providing the data is voluntary but necessary for us to reply. You may withdraw your consent at any time by writing to office@bondsoft.pl — this does not affect the lawfulness of processing before the withdrawal.

You have the right to access your data, rectify it, erase it, restrict its processing, transfer it, and lodge a complaint with the President of the Polish Personal Data Protection Office.

Full information: Privacy Policy.

Send us an email

The service this text is about

Automation and AI / OCR

Automation of document re-typing, OCR and checking rules, and your data stays with you.