meeting

Meeting Summary

Turn a meeting transcript into scannable notes that surface themes, decisions, open questions and action items, with every claim traceable to what was said or to a cited source.

Arguments

• $INPUT — the transcript text, a Google Doc URL, or a file path. Any trailing text is context from the user, such as the topic or where related docs live.

Workflow

Work through these in order. The run is complete when every step is done, or skipped with the reason given in the report.

1. Get the complete transcript (§1). Never draft from a truncated tool result: it silently drops the end of the meeting.
2. Gather the sources that settle it (§2): the deck or document the meeting reviewed, the attendee list, and the related project brain.
3. Resolve names, products and dates (§3).
4. Draft topic-grouped notes (§4), then apply provenance markers in a separate pass (§5).
5. Save to the right meetings/ folder using the template (§6).
6. Update stakeholder memory (§7).
7. Offer to update the related project CONTEXT.md with new decisions, status changes, open questions and next steps. Update it if the user confirms or asked for it up front.
8. Report back briefly: the file path; stakeholder changes and anyone not in memory; names or terms left unresolved; any post-meeting check that changes a decision; and the CONTEXT offer. Opening the file in Obsidian follows AGENTS.md.

1. Get the complete transcript

• Pasted text: use it. File path: read it.
• Google Doc URL: the document ID is the string between /d/ and /edit. Read 01-context/agent-tooling.md → cf-portal codemode first, then fetch with codemode.google_workspace_mcp_docs_get({ documentId, format: "markdown" }). If the tool fails, ask the user to paste the transcript.
• Gemini meeting docs have three tabs: Quick notes, Full notes and Transcript. A ?tab= in the URL only names one of them. Markdown export concatenates all three, so the transcript follows both notes tabs. To read one tab alone, fetch format: "raw" with includeTabsContent: true, pick the tab from doc.tabs[] by tabProperties.title, and join textRun.content from documentTab.body.content. The Full notes tab carries the Invited list and a link to the calendar event. Those names are person chips, so read person.personProperties.name too or the line comes back empty (verified 2026-09-22).