# Summarize Meeting

Summarize a meeting transcript into structured notes with date, participants, topic...

- Repository: https://github.com/phuryn/pm-skills (27597 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add phuryn/pm-skills --skill summarize-meeting -g -a claude-code -y`
Codex: `npx skills add phuryn/pm-skills --skill summarize-meeting -g -a codex -y`
Cursor: `npx skills add phuryn/pm-skills --skill summarize-meeting -g -a cursor -y`
Gemini CLI: `npx skills add phuryn/pm-skills --skill summarize-meeting -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add phuryn/pm-skills`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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]

The rest: https://github.com/phuryn/pm-skills/blob/HEAD/pm-execution/skills/summarize-meeting/SKILL.md