summarize-meeting
by phurynsummarize-meeting turns transcripts, notes, or meeting recordings into structured meeting notes with attendees, topic, key decisions, summary points, and action items. Use it for meeting minutes, post-call recaps, and accountability-focused summaries when you need a repeatable summarize-meeting workflow.
This skill scores 71/100, which means it is good enough to list for directory users who want a focused meeting-summary workflow, but they should expect some incomplete operational detail and no bundled automation. The repo gives a clear install/use case, enough structure to understand the output format, and real workflow guidance, but it would benefit from more concrete execution support before it feels fully turnkey.
- Clear trigger language for meeting transcripts, recordings, notes, and recaps, making it easy for agents to know when to use it.
- Provides an explicit structured-summary goal with date, participants, decisions, summary points, and action items, which increases agent leverage over generic prompting.
- Includes stepwise instructions and a template, helping agents execute with less guesswork than an open-ended summarization prompt.
- No support files or scripts are included, so the skill appears to rely entirely on prompt instructions rather than reusable tooling.
- The excerpt shows some workflow guidance but limited practical examples and edge-case handling, which may reduce consistency on messy transcripts.
Overview of summarize-meeting skill
The summarize-meeting skill turns raw transcripts, notes, or meeting recordings into structured meeting notes with decisions, action items, participants, and a clear topic summary. It is best for teams that need a repeatable summarize-meeting workflow for meeting notes, minutes, or post-call recaps rather than a freeform recap.
This skill is most useful when the real job is accountability: who attended, what was decided, what happens next, and what still needs follow-up. If you need a clean artifact that others can scan quickly, the summarize-meeting skill is a stronger fit than a generic “summarize this” prompt.
Who should use summarize-meeting
Use summarize-meeting if you work from long calls, async notes, or messy transcripts and want a consistent output format. It is especially practical for product, ops, and cross-functional teams where meeting notes need to be shared after the fact.
What makes summarize-meeting different
The skill is optimized for structured meeting output, not generic summarization. It emphasizes decisions, action items, and ownership, which are the details people usually lose in a plain recap. That makes summarize-meeting for Meeting Notes a better decision when the output needs to be reused by a team.
When it is a good fit
Choose this skill when your source material is already meeting-like: transcripts, recording notes, agenda notes, or discussion logs. It is less useful for marketing content, research synthesis, or documents that need heavy rewriting beyond meeting minutes.
How to Use summarize-meeting skill
summarize-meeting install and setup
Install with:
npx skills add phuryn/pm-skills --skill summarize-meeting
The summarize-meeting install step is simple because the repository is centered on one skill file. After install, start with pm-execution/skills/summarize-meeting/SKILL.md and then inspect the surrounding tree for any supporting conventions your environment expects.
What input the skill needs
The best input is a transcript, meeting notes, or a recording transcript with enough context to identify speakers and topics. If you only provide a vague prompt, the output will usually miss owners, decisions, or unresolved questions. For stronger summarize-meeting usage, include:
- the meeting date or time range
- participant names and roles if known
- the agenda or expected outcome
- the raw transcript or notes text
- any required output format, such as internal minutes or a client-ready recap
A practical prompt pattern
Turn a rough request into a complete prompt by stating the meeting type, audience, and required sections. Example:
“Summarize this product kickoff transcript into meeting notes for the team. Include date, attendees, topic, key decisions, open questions, and action items with owners. Keep it concise and ready to paste into Notion.”
That framing improves summarize-meeting results because it tells the skill what completeness looks like.
What to read first in the repo
Start with SKILL.md because it contains the actual workflow and output shape. If your local setup exposes more files, check adjacent docs or folders for environment-specific instructions, but this repository is intentionally lightweight. In practice, the main value is in understanding the template and matching it to your own note-taking system.
summarize-meeting skill FAQ
Is summarize-meeting only for transcripts?
No. The skill works with transcripts, speaker notes, or partial meeting notes. It is still strongest when the source material preserves who said what and what was decided.
Do I need the skill instead of a normal prompt?
Use the summarize-meeting skill when you want a repeatable meeting-notes format and fewer missed details. A normal prompt can work for one-off summaries, but it is easier to forget action owners, blockers, or open questions.
Is summarize-meeting beginner friendly?
Yes. The workflow is straightforward and the install path is simple. The main requirement is giving it enough meeting context; without that, even a good skill cannot infer reliable action items.
When should I not use it?
Do not use summarize-meeting for documents that are not meeting-shaped, such as long reports, product specs, or research papers. Those need different extraction rules and a different summary structure.
How to Improve summarize-meeting skill
Give it better source material
The biggest quality gain comes from cleaner inputs. If your transcript is noisy, strip timestamps, speaker labels, or duplicate text only if that does not remove meaning. For summarize-meeting to perform well, the source must still preserve decisions and ownership.
Ask for the right output shape
Be explicit about the format you want: internal notes, client recap, action log, or meeting minutes. If you want summarize-meeting for Meeting Notes, say whether you need bullet points, headings, or a table of owners and due dates. Format guidance reduces ambiguity and makes the first draft more usable.
Watch for common failure modes
The most common misses are vague action items, unnamed owners, and overcompressed summaries that hide disagreement. If that happens, rerun with a tighter request: “List each decision separately, include the owner for every action item, and call out unresolved questions.”
Iterate after the first draft
Treat the first pass as a structured extraction, then refine it. Ask for a shorter executive version, a version with action items first, or a more complete minutes-style rewrite. That workflow usually improves summarize-meeting usage more than trying to perfect the first prompt.