[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M749E2GHQFN7XN7R1EYD9YYC":3,"skill-same:01M749E2GHQFN7XN7R1EYD9YYC":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M749E2GHQFN7XN7R1EYD9YYC","summarize-meeting",null,"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.","phuryn\u002Fpm-skills","phuryn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7837354?v=4","01M727RY5RDZZWVRDN2X5F4B1W","Pawel Huryn","01M727RY6H19NE8H5PABTR7A59",27991,"MIT","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-execution\u002Fskills\u002Fsummarize-meeting\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: summarize-meeting\ndescription: \"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.\"\n---\n\n# Summarize Meeting\n\n## Purpose\n\nYou 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.\n\n## Context\n\nMeeting 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.\n\n## Instructions\n\n1. **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.\n\n2. **Think Step by Step**:\n   - Who attended and what were their roles?\n   - What was the main topic or agenda?\n   - What decisions were made?\n   - What are the next steps and who owns them?\n   - Are there open questions or blockers?\n\n3. **Extract Key Information**:\n   - Identify main discussion topics\n   - Note decisions made during the meeting\n   - Flag any disagreements or concerns\n   - Determine action items with owners and due dates\n\n4. **Create Structured Summary**: Use this template:\n\n   ```\n   ## Meeting Summary\n\n   **Date & Time**: [Date and start\u002Fend time]\n\n   **Participants**: [Full names and roles, if available]\n\n   **Topic**: [Short title—what was the meeting about?]\n\n   **Summary**\n\n   - **Point 1**: [Key discussion point or decision]\n   - **Point 2**: [Key discussion point or decision]\n   - **Point 3**: [Key discussion point or decision]\n   - [Additional points as needed]\n\n   **Action Items**\n\n   | Due Date | Owner | Action |\n   |----------|-------|--------|\n   | [Date] | [Name] | [What needs to happen] |\n   | [Date] | [Name] | [What needs to happen] |\n\n   **Decisions Made**\n   - [Decision 1]\n   - [Decision 2]\n\n   **Open Questions**\n   - [Unresolved question 1]\n   - [Unresolved question 2]\n   ```\n\n5. **Use Accessible Language**: Write for a primary school graduate. Use simple terms. Avoid jargon or explain it briefly.\n\n6. **Prioritize Clarity**: Focus on:\n   - What decisions affect the roadmap or strategy?\n   - What does each person need to do?\n   - By when do they need to do it?\n\n7. **Save the Output**: Save as a markdown document: `Meeting-Summary-[date]-[topic].md`\n\n## Notes\n\n- Be objective—summarize what was discussed, not personal opinions\n- Highlight action items clearly so nothing falls through the cracks\n- If the meeting was large or complex, consider breaking points into sections by topic\n- Use \"we\" language to keep the team feel inclusive and collaborative\n","# Summarize Meeting\n\n## Purpose\n\nYou 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.\n\n## Context\n\nMeeting 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.\n\n## Instructions\n\n1. **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.\n\n2. **Think Step by Step**:\n   - Who attended and what were their roles?\n   - What was the main topic or agenda?\n   - What decisions were made?\n   - What are the next steps and who owns them?\n   - Are there open questions or blockers?\n\n3. **Extract Key Information**:\n   - Identify main discussion topics\n   - Note decisions made during the meeting\n   - Flag any disagreements or concerns\n   - Determine action items with owners and due dates\n\n4. **Create Structured Summary**: Use this template:\n\n   ```\n   ## Meeting Summary\n\n   **Date & Time**: [Date and start\u002Fend time]\n\n   **Participants**: [Full names and roles, if available]\n\n   **Topic**: [Short title—what was the meeting about?]\n\n   **Summary**\n\n   - **Point 1**: [Key discussion point or decision]\n   - **Point 2**: [Key discussion point or decision]\n   - **Point 3**: [Key discussion point or decision]\n   - [Additional points as needed]\n\n   **Action Items**\n\n   | Due Date | Owner | Action |\n   |----------|-------|--------|\n   | [Date] | [Name] | [What needs to happen] |\n   | [Date] | [Name] | [What needs to happen] |\n\n   **Decisions Made**\n   - [Decision 1]\n   - [Decision 2]\n\n   **Open Questions**\n   - [Unresolved question 1]\n   - [Unresolved question 2]\n   ```\n\n5. **Use Accessible Language**: Write for a primary school graduate. Use simple terms. Avoid jargon or explain it briefly.\n\n6. **Prioritize Clarity**: Focus on:\n   - What decisions affect the roadmap or strategy?\n   - What does each person need to do?\n   - By when do they need to do it?\n\n7. **Save the Output**: Save as a markdown document: `Meeting-Summary-[date]-[topic].md`\n\n## Notes\n\n- Be objective—summarize what was discussed, not personal opinions\n- Highlight action items clearly so nothing falls through the cracks\n- If the meeting was large or complex, consider breaking points into sections by topic\n- Use \"we\" language to keep the team feel inclusive and collaborative\n",{"name":5,"description":7},"main","9af7bfd0bc47fdad43c2eaa7a43cd13918e7aaef","pm-execution\u002Fskills\u002Fsummarize-meeting",2885,"https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills","https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fpm-skills-2-red-team-ship","https:\u002F\u002Fgithub.com\u002Fphuryn","https:\u002F\u002Fwww.productcompass.pm\u002F","AI PM Coach, ex-CPO, Builder | 400K+ Follow","2026-11-09 07:10:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add phuryn\u002Fpm-skills --skill summarize-meeting",{"tool":40,"command":41},"bunx","bunx skills add phuryn\u002Fpm-skills --skill summarize-meeting",{"tool":43,"command":44},"pnpm","pnpm dlx skills add phuryn\u002Fpm-skills --skill summarize-meeting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-execution\u002Fskills\u002Fsummarize-meeting\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M749K1XJGDQ1FA90BGD6MJ6Z","review-resume","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.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Freview-resume\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M749JVQ3SER9X0V501S82BRX","privacy-policy","Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Fprivacy-policy\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M749JRFCNDADS61HFWMBHJJD","grammar-check","Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Fgrammar-check\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M749JMXFX9KSXV4JP6J1K7QX","draft-nda","Draft a detailed Non-Disclosure Agreement between two parties covering information types, jurisdiction, and clauses needing legal review. Use when creating confidentiality agreements or preparing an NDA for a partnership.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Fdraft-nda\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M749JGY34DGZ9BGFS2YCET6N","value-proposition","Design a detailed value proposition using a 6-part JTBD template — Who, Why, What before, How, What after, Alternatives. Use when creating a value proposition, analyzing customer value delivery, or articulating why customers should choose your product.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-product-strategy\u002Fskills\u002Fvalue-proposition\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M749JE27D1APC1PWWPFMF2GN","swot-analysis","Perform a detailed SWOT analysis — strengths, weaknesses, opportunities, and threats with actionable recommendations. Use when doing strategic assessment, competitive analysis, or evaluating a product or business position.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-product-strategy\u002Fskills\u002Fswot-analysis\u002FSKILL.md",[],[]]