Build your first Claude Skill in 15 minutes (no coding required)

7 min read  ·  Walkthrough with the exact prompts  ·  Last updated 13 May 2026

Part of Learn Claude Code: The Complete Operator's Guide. For the operator's overview of Skills, Connectors, Cowork, and Artifacts, start there.

This is the shortest path from "I do not know what a Claude skill is" to "I have one running on my computer right now".

Fifteen minutes. No YAML by hand. No file structure to memorise. No prior tutorials needed.

If you have not yet read the plain-English explainer on what a skill actually is, do that first.

This post assumes you already know the answer is "a folder that teaches Claude a workflow once".

If you have done Claude Code 101, you already have Claude Code installed and a terminal open.

If you have not, the walkthrough still works, you will just need 20 minutes of setup before the 15-minute build.

The skill we are going to build

The workflow: summarise a meeting note in your voice.

You paste raw notes. The skill turns them into a tight summary, written like you would write it.

Decisions at the top. Owners and dates next. Open questions at the bottom.

No filler. No "moving forward". No "stakeholders".

We picked this because almost everyone has done it manually at least once.

You know what good looks like. You will spot the difference instantly when the skill nails your voice versus when it does not.

If meeting notes are not your thing, swap the topic. Pick something you already re-explain to Claude two or three times a week.

The five-step process below is identical.

The secret weapon: skill-creator

You are not going to write the skill.

A built-in tool called skill-creator is going to write it for you.

You answer five questions in plain English. skill-creator produces a properly formatted skill folder, valid frontmatter, the lot.

You stay out of YAML. You stay out of file naming rules. You stay out of every technical bit that gives developers heartburn the first time they try this manually.

The only skill you need to install skill-creator itself is being able to type.

It ships with Claude Code on most installs.

Step 1: Open Claude Code

Open your terminal.

On Mac, that is Spotlight, type Terminal. On Windows with WSL, type Ubuntu. On Linux, Ctrl plus Alt plus T.

We cover the terminal in full in Module 2 of Claude Code 101 if any of that sounds like Greek.

Then run:

claude

You will see a prompt. You are in.

Every interaction from here is plain English.

Step 2: Invoke skill-creator

Type a forward slash to see your installed skills.

If skill-creator is in the list, you are ready.

If not, the Anthropic skills repo at github.com/anthropics/skills has it, and dropping the folder into ~/.claude/skills/ is the install.

Now ask Claude Code to use it:

Use the skill-creator skill to help me build a skill that

Claude Code loads skill-creator and starts asking questions.

This is the magic. Plain English questions, plain English answers.

4. Are there examples of good output?

Paste two of your own meeting summaries from when you have done this manually.

The skill learns your voice from real examples. This step matters more than the others.

Two examples beats ten adjectives.

5. What is the skill name?

"meeting-notes-summary". Lowercase, hyphens not spaces, no capitals.

skill-creator will reject anything else, which is fine because the convention exists for a reason.

That is the whole questionnaire.

skill-creator writes the skill, drops it in ~/.claude/skills/meeting-notes-summary/, and offers to enable it for you. Say yes.

Step 4: Test it on a real note

Open a new chat (no restart needed).

Paste a raw meeting note from a recent call. Then ask:

Summarise this meeting:

You should see something tight.

Decisions at the top. Owners and dates next. Open questions last. Short sentences.

If the format is right but the voice still feels generic, that is normal first time.

Step 5 fixes it.

Step 5: Iterate until it sounds like you

The first version is rarely the final version.

skill-creator exists to make iteration fast.

That summary was too formal. Loop back to skill-creator and

skill-creator edits the skill in place.

Test again. Keep going until it reads like you wrote it.

Three iterations is normal. Some people get there in one. Some in five.

None of those iterations involve YAML or file structure.

Students at our Claude Code training across New Zealand and Australia hit this iteration loop within the first hour. Once you have the rhythm with one skill, the second takes 5 minutes.

What you just built

A folder at ~/.claude/skills/meeting-notes-summary/, with one file (SKILL.md) inside.

It is plain text. You can open it like any document and read what Claude knows about your voice.

Right now, that skill is only enabled for you, on this computer.

Sharing it is the next thing to learn, covered in Module 6 of the full course.

Common stumbles, in case yours hits one

The skill does not trigger when I ask for a summary.

The description field is too vague. Loop back to skill-creator and ask it to add specific trigger phrases like "summary", "recap", and "action items".

Module 5 of the course has the full debug guide.

The skill triggers on the wrong inputs.

Description is too broad. Ask skill-creator to add a "Do NOT use for" clause excluding the wrong-cases you have seen.

The skill triggers but ignores my voice instructions.

Instructions buried. Ask skill-creator to move the critical voice rules to the top of the file under a "Critical" heading.

What to do next

Use the skill for a week. Notice when it works and when it does not.

Each "does not" is a small skill-creator iteration.

Then build a second skill. The first one is the hardest.

Once you have the rhythm, you will start spotting candidates everywhere. "I do this every Monday" is a skill. "I always tell Claude to skip the introduction" is a skill. "Our team has a checklist" is a skill.

If you want to go deeper, the full Claude Skills 101 course is one hour, free, and covers the four other things this post does not.