Summarize Meeting Agent Skill
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/phuryn/pm-skills --skill summarize-meetingThe instruction itself
5 sections, as written by the authorSummarize 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
- 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.
- 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?
- 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
- 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]
- Use Accessible Language: Write for a primary school graduate. Use simple terms. Avoid jargon or explain it briefly.
- 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?
- 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
Other skills for the same job
different authors, same section of the catalogue
A/B test subject line variations using proven copywriting frameworks. Predict open rates based on historical performance.
Draft and review professional emails that match your personal writing style. Analyzes your sent emails for tone, greeting, structure, and sign-off patterns via WorkIQ, then generates context-aware drafts for any recipient. USE FOR: draft email, write email, compose email, reply email, follow-up email, analyze email tone, email style.
Board meeting preparation, investor updates, and executive communication. Use when preparing board decks, writing investor updates, handling bad news with the board, structuring QBRs, or building board-level metric discipline. Includes the "Three Things" narrative model, the 4-tier metric hierarchy, and the pre-brief pattern that prevents board surprises.
> Reads a forwarded customer email or ticket, pulls order/refund status from PayPal and account history from HubSpot, drafts a tone-matched reply in the owner's writing voice, and can issue a PayPal refund with explicit owner approval. Use when the user says "draft a response," "answer this customer," "where's my order," or "I want a refund."
智能语音转文字助手，基于 Qwen3-ASR 模型，支持实时语音识别和智能文本改写。可以将录音转换为文字，并一键改写成邮件、笔记、社交媒体文案，支持复制、分享和录音拼接。适用于会议纪要、语音备忘、内容创作等多种场景。
British business English writing style for professional communications — polished, understated, EN-GB spelling (colour, organise, centre). Use whenever the user is writing for a British audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.
American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center). Use whenever the user is writing for an American audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on stakeholder update, status report, executive summary, exec review, manage up, communicate bad news, project comms, status meeting, weekly update. Also triggers when a project is going off track and the team needs to communicate it.
How to use it
Take phuryn/summarize-meeting from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.