Meeting Notes Summarizer
Turns a raw meeting transcript or messy notes into a clear summary — decisions, action items with owners, and open questions — without inventing anything.
What this skill does
Key features
- Extracts decisions, action items, and open questions separately
- Attributes action items to an owner only when the notes state one
- Adds due dates only when explicitly mentioned
- Never invents attendees, decisions, or numbers not in the source
Use cases
- Summarising a call transcript into shareable minutes
- Cleaning up rough notes after a planning meeting
- Producing a follow-up recap email draft
SKILL.md
The skill definition — its metadata and the exact instructions an agent follows. Copy it into a SKILL.md file in your agent's skills folder.
| name | meeting-summary |
|---|---|
| description | Summarise a meeting transcript or notes into decisions, owned action items, and open questions. |
| allowed-tools | Read, Write |
| output | markdown summary |
| input | transcript or notes |
Musts
- Read the full transcript or notes before summarising anything.
- Separate the output into Decisions, Action items, and Open questions.
- Attribute each action item to an owner only when the source names one; otherwise list it as Unassigned.
- Include a due date only when it is explicitly stated in the source.
- Never invent attendees, decisions, numbers, or commitments that are not in the input.
Guidelines
- Keep each bullet to one clear sentence; merge duplicate points.
- Write decisions as settled outcomes, not discussion recaps.
- Put anything unresolved, deferred, or unclear under Open questions rather than guessing.
Output format
# Meeting summary — <title / date>
## Decisions
- <decision that was actually agreed>
## Action items
- <task> — @<owner> (due <date, if stated>)
- Unassigned: <task with no stated owner>
## Open questions
- <unresolved or deferred item>FAQ
Will it guess who owns an action item?
No. It attributes an action to a person only when the notes explicitly assign it. Unowned items are listed under an 'Unassigned' heading so nothing is silently misattributed.
What if the notes are incomplete or ambiguous?
It summarises what is present and flags gaps under Open questions rather than filling them in. It never fabricates decisions, attendees, or dates to make the summary look complete.
Before running any skill, read its instructions and the tools it's allowed to use, and test it on a safe target first. See LLM security best practices.