Loading interactive tool…

This page in plain text

Write your first Claude skill

A skill is a way of doing one job, written down once, that Claude picks up by itself when the job comes along. It is one folder and one text file, with nothing to install and no code to write. We wrote one, ran it in Claude Code and kept the output, so every step here is one we took.

What a skill is

  • A file called SKILL.md. It sits in a folder named after the skill.
  • A description that says when. Two lines at the top. Claude reads them at the start of a session and uses them to decide whether your request is this job.
  • A body that says how. The steps, the headings you want, the rules. Claude opens it only when it has decided the skill fits.

The four steps

  1. Make the folder. Inside your project: .claude/skills/meeting-notes/. One folder per skill.
  2. Write the file. Save the text below in that folder as SKILL.md, in capitals.
  3. Start Claude Code there. Open a new session in the project folder. Ours listed meeting-notes among its skills before we typed a word.
  4. Ask the way you always do. Do not mention the skill. We typed: “Here are my notes from today’s call, can you write them up?”

A skill in your project works in that project. Put the same folder in the .claude/skills folder of your home folder and it works in every project.

The file, as we ran it

---
name: meeting-notes
description: Turn rough meeting notes into a short summary. Use when the user pastes notes from a meeting or call, or asks to tidy, summarise or write up meeting notes.
---

# Meeting notes

Turn the notes into three sections, in this order, with these exact headings:

## Decisions
What was agreed. One line each.

## Actions
Who does what, by when. Write each as: Name - task - date.
If the notes give no name or no date, write "not said". Never guess one.

## Open questions
Anything raised and not settled.

Rules:
- Use only what is in the notes. Add nothing.
- Plain words, no introduction and no closing line.
- If a section has nothing, write "None".

What came back

We gave Claude Code five lines of rough notes and the same sentence twice: once in a folder with the skill, once in a folder without it. The notes said the launch moves to the 14th, Luis is to send the price list to Dana by Friday, someone needs to check the signup form on phones, Dana asked about a second reviewer with no answer yet, and the webinar idea is dropped.

  • With the skill, Claude called meeting-notes by itself; we never said “skill”. The reply was the three headings in order, with nothing before or after them: two decisions, two actions and one open question.
  • It did not guess. Nobody was named for the phone check, so that action reads “not said – check the signup form on phones – not said”, as the file told it to.
  • Without the skill, the reply was a list in a shape Claude chose, and “the 14th” became “Nov 14” and “friday” became “Fri, Nov 20”. The notes name no month. Those are guesses.

That was one run in each folder, on 20 November 2026, with Claude Code 2.1.278. A single run shows what can happen, not what always will.

If yours does not trigger

Ours worked the first time, so we did not have to fix it. These are the three places the steps can go wrong.

  1. The path. The file must be SKILL.md, inside a folder of its own, inside .claude/skills.
  2. The description. Write it in the words you would use to ask. Ours says “notes from a meeting or call” because that is what we type.
  3. The session. Our session found the skill as it started. If you added the file while a session was open, start a new one.

Before you install someone else’s

Your own skill says only what you wrote. A skill from somewhere else can say anything, and some carry scripts. Read every file in it before you add it. Our skills directory lists skills published by their makers, and the brief guide has the five parts that also make a good skill.

Ask Another AI Guy

I'm just Another AI Guy.

You're chatting with our fast model. Create a free account for the more thorough one, and more messages.