phuryn/summarize-meeting
pm-execution/skills/summarize-meeting/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add phuryn/pm-skills summarize-meetingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
70%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 21, 2026, 1:49 PM146.2s1 file scanned
SKILL.md
- 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
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
Related Skills
phuryn/shipping-artifacts
tools
VerifiedTrustedCommunity
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
22,371SKILL.mdUpdated Jun 6, 2026
phuryn/intended-vs-implemented
development
VerifiedTrustedCommunity
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
22,371SKILL.mdUpdated Jun 6, 2026
phuryn/strategy-red-team
testing
VerifiedTrustedCommunity
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/review-resume
testing
VerifiedTrustedCommunity
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
7,806SKILL.mdUpdated Mar 20, 2026