summarize-meeting

summarize-meeting is a skill for Claude Code from phuryn/pm-skills. It costs 51 tokens per session (675 once invoked), scanned A, original, MIT.

A meeting-notes guide that turns a transcript or notes into a structured record of the date, attendees, topics, decisions, summary, and follow-up tasks.

In plain words
What is it for?
Use it to create meeting minutes, recap discussions, record who needs to do what, and note deadlines or blockers.
Why use it?
It prevents important decisions, unanswered questions, and task ownership from being lost after a meeting.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the pm-execution plugin — 16 skills, 11 commands shipped together

Good fit Use it to create meeting minutes, recap discussions, record who needs to do what, and note deadlines or blockers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/phuryn/pm-skills/summarize-meeting
About the project

phuryn/pm-skills is a marketplace of reusable skills, commands, and plugins that guide AI assistants through product-management work such as discovery, strategy, planning, metrics, launches, and growth. It is for product managers and teams using Claude Code, Cowork, or compatible assistants. The catalogue entries are the project's own workflows and extensions.

phuryn/pm-skills · 26,161 stars · on GitHub · productcompass.pm

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add phuryn/pm-skills --skill summarize-meeting
Clone the repo
git clone --depth 1 https://github.com/phuryn/pm-skills

Made for: Claude Code.

Or install pm-execution, the plugin that ships this one along with the rest of its 16 skills, 11 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for summarize-meeting

README.md
[![agentmods](https://agentmods.dev/badge/skills/phuryn/pm-skills/summarize-meeting/github.svg)](https://agentmods.dev/skills/phuryn/pm-skills/summarize-meeting)
Your own site
<a href="https://agentmods.dev/skills/phuryn/pm-skills/summarize-meeting"><img src="https://agentmods.dev/badge/skills/phuryn/pm-skills/summarize-meeting/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for summarize-meeting

Your own site · 80×15
<a href="https://agentmods.dev/skills/phuryn/pm-skills/summarize-meeting"><img src="https://agentmods.dev/badge/skills/phuryn/pm-skills/summarize-meeting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 675 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk warn 4 Mar 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.00675
Opus 5 $0.00026 $0.00338
Sonnet 5 $0.00010 $0.00135
Haiku 4.5 $0.00005 $0.00068

Measured 11d ago against content hash 4deabdd7f99c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

summarize-meeting scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

pm-execution/skills/summarize-meeting/SKILL.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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]
    

Read the full file on GitHub · 82 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 82 lines · 51 tokens per session scan A 4deabdd7f99c

Subscribe to this mod's changes

summarize-meeting is a skill published in the GitHub repository phuryn/pm-skills (26,161 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 675 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

pmm-resume

Resume reviewer and tailoring engine for Product Marketing Managers (IC to VP, including AI PMM roles). Takes baseline resume + job description → dissects JD → ranks bullets by impact fit → rebuilds complete resume in one pass. Trigger on: resume + JD paste, "tailor this", "which bullets for this role", "rebuild for…

stefanoskarakasis/Product-Marketing-Skills · 103 tokens

prd

Guides Product Managers and Product Marketing Managers to co-create complete Product Requirements Documents with embedded Solution Stories. Reads brain context (positioning, ICP, Revenue Levers) to anchor PRDs in strategy. Outputs: structured Solution Story for GTM communications + full PRD for execution alignment.

stefanoskarakasis/Product-Marketing-Skills · 59 tokens

pre-mortem

Identifies and pressure-tests failure modes for any strategic initiative (product launch, pricing change, GTM pivot, new market entry, feature rollout) by running a cross-functional risk exercise. Loads brain context (ICP, positioning, competitive landscape) and, when available, guardrails from prior pre-mortems…

stefanoskarakasis/Product-Marketing-Skills · 82 tokens

prioritization-frameworks

Selects and applies the right prioritization framework (9 frameworks: Opportunity Score, ICE, RICE, Eisenhower, Impact vs Effort, Risk vs Reward, Kano, Weighted Decision Matrix, MoSCoW) with PMM interpretation layer and GTM launch tier output (T1–T4). Reads brain context (ICP, positioning, revenue levers) and, when…

stefanoskarakasis/Product-Marketing-Skills · 92 tokens

stakeholder-maps

Builds political maps (not org charts) showing who can kill your launch, who champions it, and what to say to each stakeholder. Reads brain context (ICP, positioning, GTM motion) and guardrails from prior stakeholder mapping sessions; produces Power × Interest grid with political role assignment, conflict map, and…

stefanoskarakasis/Product-Marketing-Skills · 74 tokens

beachhead-segment

Identifies and scores your highest-priority beachhead segment using four-dimension scoring (Burning Pain, Willingness to Pay, Winnability, Referral Potential) with blocking gates. Reads brain context (ICP, positioning, competitive landscape, proof points) and, when available, guardrails from prior beachhead decisions…

stefanoskarakasis/Product-Marketing-Skills · 88 tokens