Meeting Notes Processor
You are processing a meeting transcript (from any transcription tool) into a clean, structured markdown file saved locally.
What to extract
Work through the transcript carefully and pull out:
- Meeting metadata — date, time, participants (with roles/titles if mentioned), meeting title or topic
- Executive summary — 3-5 sentences capturing the core purpose, key discussion points, and outcome of the meeting. Write this for someone who wasn't on the call.
- Key decisions — concrete things the group agreed on or resolved. Distinguish from action items: decisions are outcomes, action items are tasks.
- Action items — every task, follow-up, or commitment mentioned. Assign each to a specific person based on context. If a task is clearly unassigned, make your best guess based on who would logically own it, and flag it with
[UNASSIGNED - suggested owner].
- Open questions — things raised but not resolved, questions that need answers, or topics tabled for later.
- Next steps — any mentioned next meeting, deadline, or shared team goal.
Action item assignment rules
- If someone says "I'll handle X" or "can you take care of Y?" — assign directly.
- If no one claims a task but a domain expert is on the call (e.g., task is about design and a designer is present) — assign to them and flag as
[UNASSIGNED - suggested: Name].
- If it's truly ambiguous with no reasonable inference — mark
[UNASSIGNED].
- Never invent assignments with confidence — flag uncertainty clearly.
Output format
Save the file to ~/meeting-notes/ (create the folder if it doesn't exist) using this filename pattern:
YYYY-MM-DD_[meeting-topic-slug].md
Use the date from the transcript. If no date is found, use today's date. Slugify the topic (lowercase, hyphens, no special chars). Example: 2026-03-05_q1-product-review.md
Use exactly this markdown structure:
# [Meeting Title]
**Date:** [Date]
**Duration:** [Duration if available]
**Participants:** [Name (Role), Name (Role), ...]
---
## Executive Summary
[3-5 sentences]
---
## Key Decisions
- [Decision 1]
- [Decision 2]
---
## Action Items
### [Person Name]
- [ ] [Task description] — *due [date if mentioned]*
### [Person Name]
- [ ] [Task description]
### Unassigned
- [ ] [Task description] — *[UNASSIGNED - suggested: Name]*
---
## Open Questions
- [Question or unresolved topic]
---
## Next Steps
- [Next meeting, deadline, or shared goal]
If a section has nothing to add (e.g., no open questions), omit it entirely — don't include an empty section.
After saving
Tell the user:
- The filename and full path where it was saved
- A brief one-sentence summary of the meeting (different from the executive summary — even more condensed, like a subject line)
- How many action items were found and how many were flagged as unassigned
- Ask if they'd like any section expanded or adjusted
1---2name: meeting-notes3description: Process meeting transcripts into structured markdown summaries. Use this skill whenever the user pastes a meeting transcript, shares meeting notes, or says anything like "process this meeting", "summarize this call", "extract action items", "here's a transcript from my call", or "here are my meeting notes". Works with transcripts from any tool (Fireflies, Otter, Granola, Zoom, etc.). Trigger even if the user just pastes a block of text that looks like a speaker-labeled transcript.4---56# Meeting Notes Processor78You are processing a meeting transcript (from any transcription tool) into a clean, structured markdown file saved locally.910## What to extract1112Work through the transcript carefully and pull out:13141. **Meeting metadata** — date, time, participants (with roles/titles if mentioned), meeting title or topic152. **Executive summary** — 3-5 sentences capturing the core purpose, key discussion points, and outcome of the meeting. Write this for someone who wasn't on the call.163. **Key decisions** — concrete things the group agreed on or resolved. Distinguish from action items: decisions are outcomes, action items are tasks.174. **Action items** — every task, follow-up, or commitment mentioned. Assign each to a specific person based on context. If a task is clearly unassigned, make your best guess based on who would logically own it, and flag it with `[UNASSIGNED - suggested owner]`.185. **Open questions** — things raised but not resolved, questions that need answers, or topics tabled for later.196. **Next steps** — any mentioned next meeting, deadline, or shared team goal.2021## Action item assignment rules2223- If someone says "I'll handle X" or "can you take care of Y?" — assign directly.24- If no one claims a task but a domain expert is on the call (e.g., task is about design and a designer is present) — assign to them and flag as `[UNASSIGNED - suggested: Name]`.25- If it's truly ambiguous with no reasonable inference — mark `[UNASSIGNED]`.26- Never invent assignments with confidence — flag uncertainty clearly.2728## Output format2930Save the file to `~/meeting-notes/` (create the folder if it doesn't exist) using this filename pattern:31`YYYY-MM-DD_[meeting-topic-slug].md`3233Use the date from the transcript. If no date is found, use today's date. Slugify the topic (lowercase, hyphens, no special chars). Example: `2026-03-05_q1-product-review.md`3435Use exactly this markdown structure:3637```38# [Meeting Title]39**Date:** [Date]40**Duration:** [Duration if available]41**Participants:** [Name (Role), Name (Role), ...]4243---4445## Executive Summary46[3-5 sentences]4748---4950## Key Decisions51- [Decision 1]52- [Decision 2]5354---5556## Action Items5758### [Person Name]59- [ ] [Task description] — *due [date if mentioned]*6061### [Person Name]62- [ ] [Task description]6364### Unassigned65- [ ] [Task description] — *[UNASSIGNED - suggested: Name]*6667---6869## Open Questions70- [Question or unresolved topic]7172---7374## Next Steps75- [Next meeting, deadline, or shared goal]76```7778If a section has nothing to add (e.g., no open questions), omit it entirely — don't include an empty section.7980## After saving8182Tell the user:83- The filename and full path where it was saved84- A brief one-sentence summary of the meeting (different from the executive summary — even more condensed, like a subject line)85- How many action items were found and how many were flagged as unassigned86- Ask if they'd like any section expanded or adjusted
duncan-buildroom