meeting-notes

When to use

Trigger this skill when:

• A meeting has ended and someone needs to distribute notes to attendees and non-attendees.
• A transcript exists (from Otter, Granola, Fireflies, Zoom AI, Google Meet, or a scribe) and you need to distill it.
• A recurring meeting (staff, 1:1, design review) needs notes captured in a consistent format.

Do not use this skill for:

• Legal-grade records where verbatim matters (depositions, disputes) — use the raw transcript.
• Interview notes where the content is the notes (qualitative research) — use a research-specific template.
• Notes from a meeting you did not have a transcript for — ask the user for their rough notes first.

Inputs

Required:

• Transcript (pasted, file path, or link to Otter/Granola).
• Meeting name and date (UTC).

Optional:

• Attendees list (names and roles). If not provided, the skill will extract speakers from the transcript and ask about roles.
• Agenda (if one was circulated).
• Prior meeting notes (for recurring meetings — helps track follow-through on previous action items).

Outputs

A Markdown document following the structure in references/meeting-template.md:

1. Meeting name and Date (UTC)
2. Attendees (with roles)
3. Agenda (if provided)
4. Decisions — explicit yes/no decisions only
5. Action Items — each with owner (named person) and due date
6. Open Questions — things raised but not resolved
7. Discussion Notes — bullet summary, not verbatim
8. Next Meeting — date and agenda items carried forward

Tool dependencies

• Read — to load transcript files.
• Google Calendar MCP (optional) — to resolve attendee list and meeting time from the calendar invite.
• Notion MCP (optional) — to write the notes into a meetings database and link to prior meetings.
• Slack MCP (optional) — to post the notes summary into the team channel.

Procedure

1. Parse the transcript. Identify speaker turns. If the transcript is from Otter/Granola, these are typically tagged; if raw, infer from context or ask.
2. Resolve attendees. If not provided, list every distinct speaker. Match to the calendar invite if available. Tag each with their role.
3. Identify decisions. A decision is an explicit yes/no or pick-A-or-B moment. Look for:
   • "Let's go with X."
   • "Decided: we will..."
   • "Agreed, X by Y."
   • The end of a debate where one option is adopted. A comment like "maybe we should..." is NOT a decision — it is a possible action item or an open question.
4. Extract action items. An action item must name a person and a date.
   • "Alice will send the doc" → action item if a date can be inferred ("by end of week"), otherwise move to Open Questions with a note to confirm owner+date.
   • "Someone should look at this" → NOT an action item. Flag as Open Question.
   • Implicit due dates ("before next meeting," "this week") should be resolved to a concrete date based on the meeting date.
5. Identify open questions. Things that were raised, discussed inconclusively, and not converted into a decision or action item. Each should be one sentence, phrased as a question.
6. Summarize discussion. For each agenda item (or each major topic if no agenda), write 2–5 bullets. Each bullet is a point made, not a line spoken. Combine repeated points. Omit:
   • Greetings, goodbyes, small talk.
   • Technical hiccups ("can you hear me?").
   • Off-topic tangents unless they led to a decision or action item.
7. Check follow-through. If prior meeting notes were provided, list which of the previous action items shipped, slipped, or are still in progress.
8. Identify next meeting. Date, owner, and any agenda items explicitly carried forward.
9. Draft the notes. Enforce the structure. Keep it scannable.
10. Return for human review. Recommend sharing with attendees for corrections before publishing.