In this guide you'll build a "meeting-notes" skill that turns a messy transcript into clean notes with decisions and action items, every time, in the same format.
What you need
- A Claude account (skills are available in the Claude apps, Claude Code and the API).
- A text editor.
- 20 minutes.
Step 1: Create the folder
A skill is just a folder. Create one named after your skill:
meeting-notes/
└── SKILL.mdStep 2: Write the front matter
SKILL.md must start with a name and a description between --- lines. The description is what Claude reads to decide when to use the skill, so describe both what it does and when it applies.
---
name: meeting-notes
description: Turns meeting transcripts or rough notes into structured meeting notes with decisions and action items. Use when the user shares a transcript, call notes, or asks to summarise a meeting.
---Tip
Include words people will actually say, such as "transcript", "call notes" or "summarise a meeting". That makes the skill trigger reliably.
Step 3: Write the instructions
Below the front matter, write instructions as if you were briefing a new assistant:
# Meeting notes
## Output format
Always produce these sections, in this order:
1. **Summary**: 3 sentences maximum.
2. **Decisions**: bullet list. Write "None recorded" if there are none.
3. **Action items**: a table with columns Owner | Task | Due date.
Use "Unassigned" when no owner is mentioned. Never invent dates.
4. **Open questions**: anything left unresolved.
## Rules
- Use names exactly as they appear in the transcript.
- Remove small talk and filler.
- Keep the language of the transcript (French in, French out).Step 4 (optional): Add resources
Skills can bundle extra files. Claude reads them only when needed, so they don't slow anything down.
meeting-notes/
├── SKILL.md
├── examples/good-notes.md ← an example of perfect output
└── scripts/to_docx.py ← optional script to export notes as WordMention them in SKILL.md, for example: "See examples/good-notes.md for the expected style."
Step 5: Install the skill
In the Claude app (web or desktop):
- Zip the
meeting-notesfolder. - Open Settings → Capabilities and find Skills.
- Upload the zip and make sure the skill is switched on.
In Claude Code: copy the folder into your skills directory:
mkdir -p ~/.claude/skills
cp -r meeting-notes ~/.claude/skills/Use .claude/skills/ inside a project instead to share it with everyone working on that repository.
Step 6: Test it
Start a new chat and paste a transcript:
Here are the notes from today's call, can you clean them up?
[paste transcript]Claude should mention that it is using the meeting-notes skill and answer in your exact format. If it does not trigger, make the description more specific and try again.
Troubleshooting
| Problem | Fix |
|---|---|
| Skill never triggers | Add trigger words to the description; check the skill is enabled |
| Format is slightly off | Add a complete example of the expected output |
| Instructions too long | Move reference material into separate files |
Warning
Only install skills from people you trust. A skill can contain scripts that Claude may run.
Next: connect Claude to your apps with MCP.
Last checked: mid-2026. Menus and button names in AI apps change often, so if something looks different, look for the closest match.
Comments 0
Share tips, prompts that worked for you, or questions.
No comments yet. Be the first to share a tip.
Log in or create a free account to comment.