Summarize Meeting
Turn raw meeting transcripts or recordings into structured minutes with decisions and owned action items for solo builders and tiny product teams.
Overview
Summarize Meeting is an agent skill most often used in Build (also Validate, Grow, Operate) that turns meeting transcripts into structured notes with decisions and action items.
Install
npx skills add https://github.com/phuryn/pm-skills --skill summarize-meetingWhat is this skill?
- Structured output: date, participants, topic, key decisions, summary bullets, and action items
- Step-by-step extraction of roles, agenda, decisions, blockers, and open questions
- Accepts transcripts, recordings, or notes files; can pull background via web search when context is thin
- Action items with clear ownership for accountability across async teams
- Written for experienced-PM tone—accessible to people who did not attend
Adoption & trust: 1.3k installs on skills.sh; 12.3k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You finished a call but only have a messy transcript and no shared record of who decided what or who owns the next steps.
Who is it for?
Indie PMs and solo founders who record or transcribe calls and need fast, consistent minutes after discovery, planning, or retro sessions.
Skip if: Live real-time captioning during the meeting, legal verbatim court reporting, or cases where you already have a signed-off minutes template and only need formatting without analysis.
When should I use this skill?
Processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.
What do I get? / Deliverables
You get structured meeting minutes with participants, decisions, summary points, and accountable action items ready to paste into docs or tickets.
- Structured meeting summary with date, participants, topic, decisions, summary points, and action items
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Meeting summaries are classic product-management artifacts; the build → pm shelf is where solo builders file standups, planning calls, and stakeholder syncs before coding. The skill outputs PM-grade notes (participants, topic, decisions, actions)—the same deliverable you need when running backlog and execution without a dedicated ops person.
Where it fits
Summarize a scope call with a design partner into decisions and open questions before committing to an MVP cut.
Turn a weekly standup transcript into owned action items tied to the current sprint.
Capture launch-readiness meeting decisions and owners before release day.
Recap a customer success check-in with agreed follow-ups for lifecycle email or docs.
Document a post-incident review with decisions and remediation tasks.
How it compares
Use for structured recap from transcripts instead of asking the agent to free-form summarize chat without a decisions-and-actions schema.
Common Questions / FAQ
Who is summarize-meeting for?
Solo builders and small product teams who run customer, planning, or engineering meetings and need structured notes with decisions and action items—not a raw transcript dump.
When should I use summarize-meeting?
Use it when processing meeting recordings or transcripts, writing minutes, or recapping discussions—e.g. after a Validate scope call, a Build standup, a Ship launch sync, or an Operate incident review.
Is summarize-meeting safe to install?
Review the Security Audits panel on this Prism page for ingest risk; the skill reads meeting content you provide and may use web search for background—avoid pasting secrets you would not share in normal meeting notes.
SKILL.md
READMESKILL.md - Summarize Meeting
# Summarize Meeting ## Purpose You are an experienced product manager responsible for creating clear, actionable meeting summaries from $ARGUMENTS. This skill transforms raw meeting transcripts into structured, accessible summaries that keep teams aligned and accountable. ## Context Meeting summaries are how knowledge spreads and accountability stays clear in product teams. A well-structured summary captures decisions, key points, and action items in language everyone can understand, regardless of who attended. ## Instructions 1. **Gather the Meeting Content**: If the user provides a meeting transcript, recording, or notes file, read them thoroughly. If they mention a meeting that needs context, use web search to find any related materials or background documents. 2. **Think Step by Step**: - Who attended and what were their roles? - What was the main topic or agenda? - What decisions were made? - What are the next steps and who owns them? - Are there open questions or blockers? 3. **Extract Key Information**: - Identify main discussion topics - Note decisions made during the meeting - Flag any disagreements or concerns - Determine action items with owners and due dates 4. **Create Structured Summary**: Use this template: ``` ## Meeting Summary **Date & Time**: [Date and start/end time] **Participants**: [Full names and roles, if available] **Topic**: [Short title—what was the meeting about?] **Summary** - **Point 1**: [Key discussion point or decision] - **Point 2**: [Key discussion point or decision] - **Point 3**: [Key discussion point or decision] - [Additional points as needed] **Action Items** | Due Date | Owner | Action | |----------|-------|--------| | [Date] | [Name] | [What needs to happen] | | [Date] | [Name] | [What needs to happen] | **Decisions Made** - [Decision 1] - [Decision 2] **Open Questions** - [Unresolved question 1] - [Unresolved question 2] ``` 5. **Use Accessible Language**: Write for a primary school graduate. Use simple terms. Avoid jargon or explain it briefly. 6. **Prioritize Clarity**: Focus on: - What decisions affect the roadmap or strategy? - What does each person need to do? - By when do they need to do it? 7. **Save the Output**: Save as a markdown document: `Meeting-Summary-[date]-[topic].md` ## Notes - Be objective—summarize what was discussed, not personal opinions - Highlight action items clearly so nothing falls through the cracks - If the meeting was large or complex, consider breaking points into sections by topic - Use "we" language to keep the team feel inclusive and collaborative