Summarize Meeting

Turns meeting transcripts into structured markdown summaries with the standard stuff you actually need: decisions made, action items with owners and due dates, open questions, and a clean bulleted recap. It's built around a product manager's template, so you get consistent formatting every time. The instructions push for accessible language and objectivity, which helps when you're sharing notes across teams who weren't in the room. Saves output as a dated markdown file. If you're constantly wrestling meeting recordings into something actionable or trying to remember who agreed to do what, this handles the grunt work of extraction and formatting so you can just review and send.

skills.sh installs: 3.2K
GitHub stars: 27.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add phuryn/pm-skills --skill summarize-meeting --agent claude-code

Installs into .claude/skills of the current project.

Files

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

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?