Agent skill · writing content · borghei
summarize-meeting
Structured meeting summarization that captures decisions, action items, and open questions in a consistent format.
Why this skill is useful
Provides a structured template and methodology for summarizing meetings that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Meeting Summary Expert Overview Transform meeting notes, transcripts, or recordings into clear, actionable summaries. Every summary follows a consistent structure that makes it easy for attendees and non-attendees alike to understand what was discussed, what was decided, and who is doing what by when. Core Capabilities Metadata capture — date, time, participants with roles, topic, location Discussion synthesis — summarize substantive topics in plain language; note disagreements and resolutions Action extraction — one owner, concrete deliverable, and a specific calendar due date per item Decision logging — numbered decisions with rationale and decision-maker Open-question tracking — unresolved items with owner and target date Consistent output — fixed template plus naming convention and 24-hour distribution discipline When to Use After any meeting where decisions were made or actions were assigned. Sprint ceremonies -- planning, retro, backlog refinement, sprint review. Stakeholder meetings -- steering committees, executive reviews, client calls. Ad-hoc discussions -- when an impromptu conversation produces commitments that need tracking. Clarify First Before summarizing, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] The source material and its fidelity — raw notes, transcript, or recording (summary quality is bounded by input; missing owners/dates for action items cannot be invented) [ ] Meeting type — planning, retro, steering committee, or client call (tailors discussion synthesis and which decisions matter) [ ] Distribution scope + confidentiality — attendees, non-attendees, or execs, and any sensitivity limits (determines whether standard 24-hour distribution applies) Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/summarize-meeting