Meeting Notes
outline/outline
Create meeting notes in Outline from a template; use when the user wants an agenda, notes, or a follow-up document for a meeting.
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items.
Install Summarize Meeting
$ npx skills add phuryn/pm-skills --skill summarize-meeting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install phuryn/pm-skills summarize-meeting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pm-execution/skills/summarize-meeting .claude/skills/summarize-meeting && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "summarize-meeting" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/summarize-meeting into .claude/skills/summarize-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "summarize-meeting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/summarize-meetingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add phuryn/pm-skills --skill summarize-meeting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install phuryn/pm-skills summarize-meeting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/pm-execution/skills/summarize-meeting .agents/skills/summarize-meeting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "summarize-meeting" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/summarize-meeting into .agents/skills/summarize-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "summarize-meeting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add phuryn/pm-skills --skill summarize-meeting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install phuryn/pm-skills summarize-meeting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/pm-execution/skills/summarize-meeting .cursor/skills/summarize-meeting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "summarize-meeting" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/summarize-meeting into .cursor/skills/summarize-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "summarize-meeting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/phuryn/pm-skills.git --path pm-execution/skills/summarize-meeting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add phuryn/pm-skills --skill summarize-meeting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install phuryn/pm-skills summarize-meeting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/pm-execution/skills/summarize-meeting .gemini/skills/summarize-meeting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "summarize-meeting" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/summarize-meeting into .gemini/skills/summarize-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "summarize-meeting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install phuryn/pm-skills summarize-meetingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add phuryn/pm-skills --skill summarize-meeting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/pm-execution/skills/summarize-meeting .github/skills/summarize-meeting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "summarize-meeting" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/summarize-meeting into .github/skills/summarize-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "summarize-meeting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add phuryn/pm-skills --skill summarize-meeting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install phuryn/pm-skills summarize-meeting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/pm-execution/skills/summarize-meeting .opencode/skills/summarize-meeting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "summarize-meeting" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/summarize-meeting into .opencode/skills/summarize-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "summarize-meeting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
summarize-meeting- GitHub stars
- 27k
- Token cost
- ~749 tokens
- SKILL.md length
- 278 words
- Files
- 1
- Skills in repo
- 67
- Repo updated
- First seen
- Licence
- MIT
At a glance
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items.
- Works in 7 steps: Gather the Meeting Content: If the user… → Think Step by Step → Extract Key Information → …
- Processing meeting recordings
- SKILL.md covers Purpose, Context, Instructions and Notes
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Summarize Meeting is an agent skill from phuryn/pm-skills. 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.
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Meeting notes and agendas. The repository describes itself as: PM Skills Marketplace: 100+ agentic skills, commands, and plugins — from discovery to strategy, execution, launch, and growth. The licence is MIT.
When your agent uses it
- Processing meeting recordings
- Creating meeting notes
- Writing meeting minutes
- Recapping discussions
Example prompts
- “/summarize-meeting”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Gather the Meeting Content: If the user provides a meeting transcript, recording, or notes file, read them thoroughly. If they mention a…
- Think Step by Step
- Extract Key Information
- Create Structured Summary: Use this template
- Use Accessible Language: Write for a primary school graduate. Use simple terms. Avoid jargon or explain it briefly.
- Prioritize Clarity: Focus on
- Save the Output: Save as a markdown document: Meeting-Summary-[date]-[topic].md
What it can do on your machine
Read from SKILL.md and the folder at commit 6058e29. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Summarize Meeting loads about 749 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 278 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from phuryn/pm-skills at commit 6058e29, republished under its MIT licence (© phuryn). 278 words, ~749 tokens.
Download SKILL.mdSave it as
.claude/skills/summarize-meeting/SKILL.md (or your agent's skills folder).- 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
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
Show full SKILL.md (44 more words)Show less
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. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in pm-execution/skills/summarize-meeting of phuryn/pm-skills.
Open the folder on GitHubat commit 6058e29
Compare with similar skills
Summarize Meeting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Summarize Meeting this skillphuryn/pm-skills | 27k | — | ~749 | Automated safety check: Pass | MIT | |
| Meeting Notesoutline/outline | 41k | — | ~551 | Automated safety check: Pass | Custom licence | |
| Management Talkthananon/9arm-skills | 3.2k | — | ~3.2k | Automated safety check: Pass | None | |
| Challenge Baseline ModelAgibotTech/genie_sim | 1.4k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Handwriting Stand Uplimin112/min-skill | 454 | — | ~2.5k | Automated safety check: Pass | None | |
| Daily Journalravila4/claude-adhd-skills | 158 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Management Talk
thananon/9arm-skills
Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…
Challenge Baseline Model
AgibotTech/genie_sim
Provision and launch the Simulation Challenge baseline inference model end to end: clone the inference code from a given git repo/branch, download the checkpoints from ModelScope into the repo's…
Handwriting Stand Up
limin112/min-skill
Turn a screen recording of handwriting (or a photo of handwritten text) into a single-file HTML "continuation" — the recording plays, the ink lifts off the page as solid 3D letters, a short animated…
Daily Journal
ravila4/claude-adhd-skills
Draft, organize, or update development journal entries. An agent skill from ravila4/claude-adhd-skills.
Granola
ArtemXTech/claude-code-obsidian-starter
Query and sync Granola meetings to Obsidian vault. An agent skill from ArtemXTech/claude-code-obsidian-starter.
More from phuryn/pm-skills
All 67 skills in this repoAgreement-Based Code Review
phuryn/pm-skills
Reviews a diff by anchoring on agreements between two sides of a boundary, forcing a concrete violating execution, and refuting each finding before reporting it.
A/B Test Analysis
phuryn/pm-skills
Validates an experiment's setup, works out lift, p-value and confidence interval from A/B test data, and recommends whether to ship, extend or stop.
Team OKR Brainstorm
phuryn/pm-skills
Drafts three alternative sets of team OKRs, each with an inspiring objective and measurable key results, tied to the company strategy you provide.
Cohort Analysis and Retention Explorer
phuryn/pm-skills
Analyzes uploaded cohort data to compute retention curves and feature adoption trends, builds heatmaps and charts, and suggests qualitative follow-up research.
Dummy Dataset Generator
phuryn/pm-skills
Generates realistic test datasets with custom columns, row counts and business constraints, output as CSV, JSON, SQL inserts or a runnable Python script.
Grammar and Flow Checker
phuryn/pm-skills
Reviews a draft for grammar, logic and flow problems and returns located, prioritized fix suggestions without rewriting the whole text.
Related
Categories
Questions about Summarize Meeting
What does Summarize Meeting do?
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Summarize Meeting is an agent skill from phuryn/pm-skills. Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items.
When should I use Summarize Meeting?
Summarize Meeting fits situations like: processing meeting recordings; creating meeting notes; writing meeting minutes; recapping discussions.
How do I install Summarize Meeting in Claude Code?
Run `npx skills add phuryn/pm-skills --skill summarize-meeting -a claude-code`. Or copy the skill folder (pm-execution/skills/summarize-meeting in phuryn/pm-skills) into .claude/skills/summarize-meeting in your project. Claude Code loads it when a task matches its description.
How do I install Summarize Meeting in Codex?
Run `npx skills add phuryn/pm-skills --skill summarize-meeting -a codex`. Or copy the skill folder (pm-execution/skills/summarize-meeting in phuryn/pm-skills) into .agents/skills/summarize-meeting in your project. Codex loads it when a task matches its description.
Can I use Summarize Meeting in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add phuryn/pm-skills --skill summarize-meeting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/summarize-meeting, .gemini/skills/summarize-meeting, .github/skills/summarize-meeting and .opencode/skills/summarize-meeting in your project.
What does Summarize Meeting need to run?
SKILL.md names no scripts, command-line tools or credentials: Summarize Meeting is instructions for the agent only.
Does Summarize Meeting access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Summarize Meeting safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Summarize Meeting use?
Summarize Meeting is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Summarize Meeting use?
About 749 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Summarize Meeting?
Skills that share tags, products or a category with Summarize Meeting: Meeting Notes (outline/outline, 41k stars), Management Talk (thananon/9arm-skills, 3.2k stars), Challenge Baseline Model (AgibotTech/genie_sim, 1.4k stars) and Handwriting Stand Up (limin112/min-skill, 454 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Summarize Meeting?
phuryn (a GitHub user) maintains it in phuryn/pm-skills, which has 26,862 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on October 9, 2026.
Source: phuryn/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.