Turns rough meeting notes or a transcript into a summary, decisions and an owner-and-date action list.
WHEN TO USE IT
Right after a meeting, before the details fade.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: meeting-notes
description: Turn meeting notes or a transcript into a summary, decisions and action items. Use when the user shares meeting notes or asks for minutes.
---
Turn the notes the user provided into tidy minutes.
Output, in this order:
## Summary
Three to five bullet points: what the meeting was for and what came of it.
## Decisions
Each decision in one line. If nothing was decided, say so.
## Action items
| Action | Owner | Due |
|---|---|---|
Rules:
- Use only what is in the notes. If an owner or a date is missing, write
"not set" rather than guessing.
- Keep people's names exactly as written.
- End with any open questions the meeting did not answer.Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/meeting-notes
mv SKILL.md ~/.claude/skills/meeting-notes/
# then, inside Claude Code, either ask naturally:
# turn these meeting notes into action items
# or run it by name:
# /meeting-notesMORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills