[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JYYYK7XTP3CCTC9MRHNGY":3,"skill-same:01M71JYYYK7XTP3CCTC9MRHNGY":84},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M71JYYYK7XTP3CCTC9MRHNGY","pmstudio-comms",null,"Generate templated stakeholder communications from project context. Use when someone asks to \"write a go-live email\", \"create a status update\", \"onboard someone\", \"write an announcement\", \"steerco update\", \"incident summary\", \"change notification\", or any stakeholder communication task. Reads project memory, stakeholder directory, PRD, and meeting notes to pre-fill real names, dates, and context. Produces ready-to-send Markdown.","coco-research\u002Fcoco","coco-research","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F68911604?v=4","01M71JRE9C4NM4NSZM4JD0BJTB","Coco Research","01M71JREA0ZMR0PMH3CKA99SN1",631,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Fstakeholder-comms\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"pmstudio comms","pmstudio","comms","incident","when","send","project memory","communications","project","pm","memory","ready","markdown","communication","announcement","generate","create","incident summary","notes","change","2026-11-10 10:12:30",false,"---\nname: pmstudio-comms\ndescription: Generate templated stakeholder communications from project context. Use when someone asks to \"write a go-live email\", \"create a status update\", \"onboard someone\", \"write an announcement\", \"steerco update\", \"incident summary\", \"change notification\", or any stakeholder communication task. Reads project memory, stakeholder directory, PRD, and meeting notes to pre-fill real names, dates, and context. Produces ready-to-send Markdown.\ndomain: pm\n---\n\n# Stakeholder Comms — Templated Communications Generator\n\n## Purpose\n\nGenerates stakeholder communications pre-filled with project context. Not generic templates — these pull real stakeholder names, real dates, real scope from project artifacts.\n\n## Process\n\n### Step 1: Identify Template\n\nFrom user request or by asking:\n\n| Command | Template | When to Use |\n|---------|----------|-------------|\n| `\u002Fstakeholder-comms go-live` | Go-Live Announcement | Product\u002Ffeature launching |\n| `\u002Fstakeholder-comms status` | Status Update | Periodic reporting (weekly\u002Fbiweekly) |\n| `\u002Fstakeholder-comms onboard {name}` | Onboarding Brief | New team member joining |\n| `\u002Fstakeholder-comms change` | Change Notification | Planned change to live product |\n| `\u002Fstakeholder-comms incident` | Incident Summary | Post-incident communication |\n| `\u002Fstakeholder-comms steerco` | SteerCo Update | Leadership\u002Fgovernance meeting prep |\n\nIf no subcommand, ask: \"What type of communication do you need?\"\n\n### Step 2: Read Context\n\n**All templates read:**\n- `CLAUDE.local.md` — project overview, key decisions, stakeholders, recent changes\n- `.sync-watch.json` — project name\n\n**Template-specific reads:**\n\n| Template | Additional Sources |\n|----------|-------------------|\n| Go-Live | PRD (scope, success metrics), Meeting-Notes (launch decisions) |\n| Status | PRD (milestones, timeline), Meeting-Notes (recent), Change-Log (recent entries) |\n| Onboard | Stakeholder Directory, PRD (overview), Presentations (links to share) |\n| Change | PRD (affected components), DR-Plan (rollback procedures if exists) |\n| Incident | IRP (severity definitions if exists), Meeting-Notes (incident details) |\n| SteerCo | PRD (timeline, risks), Change-Log (period changes), all recent Meeting-Notes |\n\n### Step 3: Ask Clarifying Questions\n\nOnly ask what can't be inferred from context:\n\n- **Audience:** Who receives this? (all stakeholders \u002F specific group \u002F leadership)\n- **Tone:** Formal (board) \u002F professional (cross-team) \u002F casual (own team)\n- **Period:** For status updates — what date range?\n- **Specific content:** For incident — what happened? For change — what's changing?\n\n### Step 4: Generate Communication\n\n**Output location:** `Comms\u002F{Type}-{Date}-{Audience}.md`\n\nIf `Comms\u002F` directory doesn't exist, create it.\n\n### Templates\n\nSee `references\u002Ftemplates.md` for the full template content for each type. Summary:\n\n#### Go-Live Announcement\n- Subject line, TL;DR (2 sentences), What's Live (scope), Who It Affects, What To Do (action items per audience group), Known Limitations, Support Contacts, Timeline (what's next)\n\n#### Status Update\n- Period, RAG Status (Red\u002FAmber\u002FGreen with explanation), Key Accomplishments (bulleted), Decisions Made, Risks & Blockers (with owners), Upcoming Milestones (next 2 weeks), Action Items (table: item\u002Fowner\u002Fdue), Help Needed\n\n#### Onboarding Brief\n- Welcome, Product Overview (2-paragraph summary), Your Role, Key Contacts (table: name\u002Frole\u002Femail\u002Fwhen-to-contact), Access Setup Checklist, Key Documents (links), First-Week Actions, Glossary (10 most-used terms)\n\n#### Change Notification\n- What's Changing, When, Why, Who's Affected, What You Need To Do, Rollback Plan, Support Contacts\n\n#### Incident Summary\n- Severity, Timeline (bullet list: detected\u002Fresponded\u002Fresolved), Impact, Root Cause, Resolution, Prevention (what we're doing so this doesn't happen again), Action Items\n\n#### SteerCo Update\n- Executive Summary (3 bullets max), RAG Status with trend arrow, Decisions Needed (numbered, with context and recommendation), Budget & Timeline (table), Key Risks (top 3 with mitigation status), Accomplishments Since Last SteerCo, Next Period Focus\n\n### Step 5: Present and Refine\n\nShow the generated communication. Ask:\n- \"Ready to save, or would you like to adjust anything?\"\n- For emails: \"Want me to include a subject line suggestion?\"\n\n## Critical Rules\n\n1. **Use real data.** Pull actual names, dates, and scope from project files. Never use placeholders like \"[Name]\" if the information exists in context.\n2. **Appropriate detail level.** SteerCo updates are concise (1 page). Onboarding briefs are comprehensive. Match the template.\n3. **Action-oriented.** Every communication should make clear what the reader should DO. No information-only dumps.\n4. **Tone matching.** Leadership comms use formal language. Team comms can be direct. Incident comms are factual and calm.\n5. **Don't fabricate.** If you don't have incident details, ask. Don't guess root causes or timelines.\n","# Stakeholder Comms — Templated Communications Generator\n\n## Purpose\n\nGenerates stakeholder communications pre-filled with project context. Not generic templates — these pull real stakeholder names, real dates, real scope from project artifacts.\n\n## Process\n\n### Step 1: Identify Template\n\nFrom user request or by asking:\n\n| Command | Template | When to Use |\n|---------|----------|-------------|\n| `\u002Fstakeholder-comms go-live` | Go-Live Announcement | Product\u002Ffeature launching |\n| `\u002Fstakeholder-comms status` | Status Update | Periodic reporting (weekly\u002Fbiweekly) |\n| `\u002Fstakeholder-comms onboard {name}` | Onboarding Brief | New team member joining |\n| `\u002Fstakeholder-comms change` | Change Notification | Planned change to live product |\n| `\u002Fstakeholder-comms incident` | Incident Summary | Post-incident communication |\n| `\u002Fstakeholder-comms steerco` | SteerCo Update | Leadership\u002Fgovernance meeting prep |\n\nIf no subcommand, ask: \"What type of communication do you need?\"\n\n### Step 2: Read Context\n\n**All templates read:**\n- `CLAUDE.local.md` — project overview, key decisions, stakeholders, recent changes\n- `.sync-watch.json` — project name\n\n**Template-specific reads:**\n\n| Template | Additional Sources |\n|----------|-------------------|\n| Go-Live | PRD (scope, success metrics), Meeting-Notes (launch decisions) |\n| Status | PRD (milestones, timeline), Meeting-Notes (recent), Change-Log (recent entries) |\n| Onboard | Stakeholder Directory, PRD (overview), Presentations (links to share) |\n| Change | PRD (affected components), DR-Plan (rollback procedures if exists) |\n| Incident | IRP (severity definitions if exists), Meeting-Notes (incident details) |\n| SteerCo | PRD (timeline, risks), Change-Log (period changes), all recent Meeting-Notes |\n\n### Step 3: Ask Clarifying Questions\n\nOnly ask what can't be inferred from context:\n\n- **Audience:** Who receives this? (all stakeholders \u002F specific group \u002F leadership)\n- **Tone:** Formal (board) \u002F professional (cross-team) \u002F casual (own team)\n- **Period:** For status updates — what date range?\n- **Specific content:** For incident — what happened? For change — what's changing?\n\n### Step 4: Generate Communication\n\n**Output location:** `Comms\u002F{Type}-{Date}-{Audience}.md`\n\nIf `Comms\u002F` directory doesn't exist, create it.\n\n### Templates\n\nSee `references\u002Ftemplates.md` for the full template content for each type. Summary:\n\n#### Go-Live Announcement\n- Subject line, TL;DR (2 sentences), What's Live (scope), Who It Affects, What To Do (action items per audience group), Known Limitations, Support Contacts, Timeline (what's next)\n\n#### Status Update\n- Period, RAG Status (Red\u002FAmber\u002FGreen with explanation), Key Accomplishments (bulleted), Decisions Made, Risks & Blockers (with owners), Upcoming Milestones (next 2 weeks), Action Items (table: item\u002Fowner\u002Fdue), Help Needed\n\n#### Onboarding Brief\n- Welcome, Product Overview (2-paragraph summary), Your Role, Key Contacts (table: name\u002Frole\u002Femail\u002Fwhen-to-contact), Access Setup Checklist, Key Documents (links), First-Week Actions, Glossary (10 most-used terms)\n\n#### Change Notification\n- What's Changing, When, Why, Who's Affected, What You Need To Do, Rollback Plan, Support Contacts\n\n#### Incident Summary\n- Severity, Timeline (bullet list: detected\u002Fresponded\u002Fresolved), Impact, Root Cause, Resolution, Prevention (what we're doing so this doesn't happen again), Action Items\n\n#### SteerCo Update\n- Executive Summary (3 bullets max), RAG Status with trend arrow, Decisions Needed (numbered, with context and recommendation), Budget & Timeline (table), Key Risks (top 3 with mitigation status), Accomplishments Since Last SteerCo, Next Period Focus\n\n### Step 5: Present and Refine\n\nShow the generated communication. Ask:\n- \"Ready to save, or would you like to adjust anything?\"\n- For emails: \"Want me to include a subject line suggestion?\"\n\n## Critical Rules\n\n1. **Use real data.** Pull actual names, dates, and scope from project files. Never use placeholders like \"[Name]\" if the information exists in context.\n2. **Appropriate detail level.** SteerCo updates are concise (1 page). Onboarding briefs are comprehensive. Match the template.\n3. **Action-oriented.** Every communication should make clear what the reader should DO. No information-only dumps.\n4. **Tone matching.** Leadership comms use formal language. Team comms can be direct. Incident comms are factual and calm.\n5. **Don't fabricate.** If you don't have incident details, ask. Don't guess root causes or timelines.\n",{"name":5,"domain":38,"description":7},"main","cd89f013b617f7eea982a9bbc60e992974fda2aa","skills\u002Fstakeholder-comms",15,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco","https:\u002F\u002Fcocoresearch.org\u002Fcoco\u002F","https:\u002F\u002Fgithub.com\u002Fcoco-research","https:\u002F\u002Fcocoresearch.org","Local-first, open-source tools for people who work with AI agents: governed memory, agents that check their own work, and data that stays on your machine.","2026-11-11 12:18:13",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add coco-research\u002Fcoco --skill pmstudio-comms",{"tool":70,"command":71},"bunx","bunx skills add coco-research\u002Fcoco --skill pmstudio-comms",{"tool":73,"command":74},"pnpm","pnpm dlx skills add coco-research\u002Fcoco --skill pmstudio-comms","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Fstakeholder-comms\u002FSKILL.md",true,[78],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Ftemplates.md","REFERENCE","参考文档",5743,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Fstakeholder-comms\u002Freferences\u002Ftemplates.md",[85,110,120,136,169,188],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":92,"publishedAt":49},"01M71KEJXF9KMT0BWCMRSRFA4M","trading-super-intelligence","Trading Super Intelligence Team. Named real-world personas across 8 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Ftrading\u002FSKILL.md",[91],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109],"super","trading super intelligence","intelligence","trading","validator","personas","local","composites","studio","team","across","world","first","gated","2026","lm studio","local-first",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":117,"publishedAt":49},"01M71KEFWS3CMAP7DF1P0FWTDE","strategy-super-intelligence","Strategy Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fstrategy\u002FSKILL.md",[116],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[118,93,119,95,97,98,99,100,101,102,103,104,105,106,107,108,109],"strategy","strategy super intelligence",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":130,"publishedAt":49},"01M71KED56ZEPK2QE84QSQPMT0","risk-compliance-super-intelligence","Risk & Compliance (GRC) Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Frisk-compliance\u002FSKILL.md",[126,127],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":128,"categoryName":129,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[131,93,132,133,134,95,97,98,99,100,135,101,102,103,104,105,106,107,108,109],"risk","risk compliance super intelligence","compliance","risk compliance","grc",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":153,"publishedAt":49},"01M71KE9A2FWSC74VA96W1EZSN","product-design-super-intelligence","Your product + design brain trust and decision partner. Named personas across 8 cells spanning product strategy, discovery\u002Fresearch, growth\u002Fmetrics, design foundations\u002Fusability, design leadership\u002Fcraft, UX\u002Fcontent, design systems, and a…","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fproduct-design\u002FSKILL.md",[142,145,148,149,150],{"categoryNo":143,"categoryName":144,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},{"categoryNo":151,"categoryName":152,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[154,155,95,156,93,157,158,159,160,161,162,102,103,163,164,107,165,166,167,168],"design","product","product design","product design super intelligence","foundations","product-design","decision","design systems","usability","leadership","ux","brain","craft","metrics","trust",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":177,"publishedAt":49},"01M71KE6H9FPSD9TECYFBPXZ8Y","legal-ip-super-intelligence","Your legal, IP, and regulatory brain trust. 31 named personas across 7 cells covering patent strategy, tech licensing, regulatory litigation, AI governance, open-source compliance, privacy law, and antitrust.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Flegal-ip\u002FSKILL.md",[175,176],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":128,"categoryName":129,"taxonomyType":26,"taxonomyTypeDesc":27},[178,93,179,95,180,181,168,182,98,183,184,185,118,102,103,186,133,187,107,165],"ip","legal ip super intelligence","legal","sep","tech","litigation","ai governance","open","open-source","governance",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":195,"publishedAt":49},"01M71KE36QRY610V6YVB9JWRND","healthcare-life-sciences-super-intelligence","Your healthcare and life sciences brain trust. 25 named personas across 7 cells covering drug discovery, medtech, biotech strategy, health policy, genomics, clinical trials, and healthcare economics.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fhealthcare-life-sciences\u002FSKILL.md",[194],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[196,93,197,198,95,181,168,199,200,98,201,202,118,102,103,203,204,205,206,107],"healthcare","healthcare life sciences super intelligence","life","economics","discovery","policy","clinical","clinical trials","health","trials","genomics"]