Structured meeting summarization that captures decisions, action items, and open questions in a consistent format.
SkillScore77Maintained
Automatic
◆Knowledge Management pack
Last verified 8/20/2026
What it changes
Passed 17 of 22 test cases with the skill, and 9 of 22 without it.
Without skill41%
With skill77%
Checks it passed that the model alone missed
Lists explicit assumptions at the top of the generated summary
Declines strategic decision framework analysis as out of scope
Directs action item ticket creation to the jira-expert integration
and 6 more in the full report
9 fixed8 passed either way4 still failing1 broke
Pass-rate lift
+36 pp
Tokens
+100%
Agent turns
0%
Response time
-2%
Model gemini-3.6-flashMeasured 8/20/2026v117 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
Here are raw notes from today's product sync. 'We need to update the staging environment SSL certificates. Alex and Sam said they would handle it together by next Friday.' Please summarize this action item into our standard format.
What was checked, without and with the skill
Checked
Without skill
With skill
Assigns exactly one primary owner to the SSL certificate update action item
Missed
Passed
case-02 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md65 lines8 filesincludes scripts
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.
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.
References
Load the reference that matches the task — keep this file lean and pull detail on demand:
references/summarization-process.md — the full six-step methodology (metadata → discussion → actions → decisions → open questions → distribute), the output template, focus priorities, troubleshooting table, and success criteria. Read when producing a summary.
references/meeting-facilitation-guide.md — meeting types, note-taking strategies, and anti-patterns. Read to tailor the summary to the meeting type or improve input quality.
references/red-flags.md — common ways summaries go wrong with bad/good examples. Read before posting, emailing, or linking a summary.
assets/meeting_summary_template.md — ready-to-use fill-in template. Use to draft the summary directly.
Guide red-green-refactor TDD with test generation, coverage-gap analysis, and multi- framework support. Use when writing tests first, analyzing coverage, generating test stubs, or converting tests between Jest, Pytest, JUnit, and Vitest.