Skip to main content
affpapa.org
RU EN
skill Claude Code CX Codex Cursor GitHub Copilot

summarize-meeting — Claude Code skill: structured meeting notes

Transforms meeting transcripts into organized notes with participants, decisions, key points, and action items assigned to owners. Use it to process meeting recordings or create meeting minutes quickly.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add phuryn/pm-skills --skill summarize-meeting -a claude-code
Open on GitHub

What summarize-meeting does

The skill takes a meeting transcript and breaks it down: who attended, what was discussed, what decisions were made, and what comes next. It outputs a structured markdown document with an action items table, decisions list, and open questions.

Internally, it works step by step: identify participants and their roles, extract key discussion points, flag decisions, determine actions with owners and due dates. Everything is written in plain language so everyone understands—no corporate jargon. The output is a markdown file with consistent structure: date, topic, discussion points, decisions, and an action table with owners and deadlines.

Runs on six platforms: Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. Saves the file as Meeting-Summary-[date]-[topic].md.

What it helps with

  • create a meeting protocol from a recording or raw transcript
  • separate decisions from general discussion points
  • assign action items to team members with deadlines
  • reformat a meeting into a shareable document for the team
  • identify open questions and blockers that could be overlooked

Example prompts for the agent

  • Here's a transcript from our release planning meeting—create structured notes with decisions and who owns each item
  • Process this stand-up recording and pull out action items with due dates and owners
  • Extract key decisions, actions, and open questions from this meeting transcript

How to install summarize-meeting

1Skills CLI (Vercel)

npx skills add phuryn/pm-skills --skill summarize-meeting -a claude-code

2Manually: put the files in place

~/.claude/skills/summarize-meeting/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/summarize-meeting/

From the same set61

The whole set →
create-prd phuryn This skill builds a lean PRD from an 8-section template. Use it to define a feature, document product requirements, or review an existing PRD. Claude Code CX Codex Cursor +1 10,800installs pre-mortem phuryn Runs a pre-mortem risk assessment on PRDs and launch plans. Catches critical launch blockers, surfaces hidden team assumptions, and maps action items. Claude Code CX Codex Cursor +1 10,200installs outcome-roadmap phuryn Rewrites feature-heavy roadmaps into outcome-focused statements tied to business and customer impact. Helps teams replace rigid feature lists with measurable strategic goals. Claude Code CX Codex Cursor +1 9,900installs prioritization-frameworks phuryn Reference guide to 9 prioritization frameworks: RICE, ICE, Opportunity Score, Kano, MoSCoW and more. Helps you pick the right method, compare approaches, and rank tasks by importance. Claude Code CX Codex Cursor +1 9,900installs strategy-red-team phuryn Stress-tests PRDs, roadmaps, and strategies by attacking load-bearing assumptions before reality does, returning kill criteria and cheap tests. Claude Code CX Codex Cursor +1 9,200installs competitor-analysis phuryn This skill researches direct competitors and compares their positioning, strengths, weaknesses, and pricing. Use it to prepare a competitive brief or find ways to differentiate a product. Claude Code CX Codex Cursor +1 3,800installs business-model phuryn Skill generates a Business Model Canvas with all 9 building blocks: from key partners and activities to channels and revenue streams. Use it to create a business model, document how value flows, or analyze an existing business. Claude Code CX Codex Cursor +1 3,700installs privacy-policy phuryn Skill drafts a detailed privacy policy accounting for GDPR, CCPA, and other regulations. Use it when building a new product, updating data protection docs, or preparing for compliance audits. Claude Code CX Codex Cursor +1 3,500installs

Similar

resume-quantifier Paramchoudhary A skill that spots resume bullets without numbers and helps estimate metrics when exact data is missing. Useful when your experience section has no quantifiable results. Claude Code CX Codex Cursor +1 10,000installs brainstorming sickn33 Turns raw ideas into validated design specifications through structured dialogue. It helps plan feature architecture before any code implementation starts. Claude Code CX Codex Cursor +1 2,300installs openviking-memory volcengine Connects agents to OpenViking MCP long-term memory to retrieve relevant past knowledge at task start and save durable takeaways afterward. Claude Code CX Codex Cursor +1 502installs gtm-positioning-strategy official Smit Patel (https://linkedin.com/in/smitkpatel) This skill helps identify product differentiation and test whether buyers respond to positioning claims. Use it before changing messaging or committing to a rebrand. GitHub Copilot 1,900installs find-skills vercel-labs Discovers and installs agent skills from skills.sh directly inside your coding assistant. Handy when you need domain-specific workflows for a project. Claude Code CX Codex Cursor +1 4,000,000installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. Claude Code 1,424,476installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. Claude Code 1,219,756installs handoff Matt Pocock Creates a handoff document from the current conversation so another agent can continue the work. Use it when a task moves to a new session or agent. Claude Code 1,038,491installs

Questions about summarize-meeting

How do I install summarize-meeting in Claude Code?

Run npx skills add phuryn/pm-skills --skill summarize-meeting -a claude-code in your terminal, then find the installed skill at ~/.claude/skills/summarize-meeting/SKILL.md. For other platforms, change the -a flag: codex, cursor, gemini-cli, or opencode.

What does the summarize-meeting skill do?

It transforms a meeting transcript into structured notes: extracts participants, topic, key discussion points, decisions, and action items with owners and deadlines. Saves as markdown file named Meeting-Summary-[date]-[topic].md.

Which platforms support this skill?

Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. Each platform has its own install command, but the process is the same: add the repository and specify the platform with the -a flag.

Source text

SKILL.md · MIT 
---
name: summarize-meeting
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."
---

# 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

© phuryn · MIT · phuryn/pm-skills

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor