[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-anthropic-stakeholder-update":3,"mdc--q4b6d0-key":34,"related-repo-anthropic-stakeholder-update":1479,"related-org-anthropic-stakeholder-update":1596},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":29,"sourceUrl":32,"mdContent":33},"stakeholder-update","generate stakeholder updates by audience","Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"anthropic","Anthropic","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fanthropic.png","anthropics",[13,17,20],{"name":14,"slug":15,"type":16},"Reporting","reporting","tag",{"name":18,"slug":19,"type":16},"Product Management","product-management",{"name":21,"slug":22,"type":16},"Communications","communications",22885,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","2026-04-06T17:59:07.637932",null,2736,[],{"repoUrl":24,"stars":23,"forks":27,"topics":30,"description":31},[],"Open source repository of plugins primarily intended for knowledge workers to use in Claude Cowork","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Ftree\u002FHEAD\u002Fproduct-management\u002Fskills\u002Fstakeholder-update","---\nname: stakeholder-update\ndescription: Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.\nargument-hint: \"\u003Cupdate type and audience>\"\n---\n\n# Stakeholder Update\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nGenerate a stakeholder update tailored to the audience and cadence.\n\n## Usage\n\n```\n\u002Fstakeholder-update $ARGUMENTS\n```\n\n## Workflow\n\n### 1. Determine Update Type\n\nAsk the user what kind of update:\n- **Weekly**: Regular cadence update on progress, blockers, and next steps\n- **Monthly**: Higher-level summary with trends, milestones, and strategic alignment\n- **Launch**: Announcement of a feature or product launch with details and impact\n- **Ad-hoc**: One-off update for a specific situation (escalation, pivot, major decision)\n\n### 2. Determine Audience\n\nAsk who the update is for:\n- **Executives \u002F leadership**: High-level, outcome-focused, strategic framing, brief\n- **Engineering team**: Technical detail, implementation context, blockers, decisions needed\n- **Cross-functional partners**: Context-appropriate detail, focus on shared goals and dependencies\n- **Customers \u002F external**: Benefits-focused, clear timelines, no internal jargon\n- **Board**: Metrics-driven, strategic, risk-focused, very concise\n\n### 3. Pull Context from Connected Tools\n\nIf **~~project tracker** is connected:\n- Pull status of roadmap items and milestones\n- Identify completed items since last update\n- Surface items that are at risk or blocked\n- Pull sprint or iteration progress\n\nIf **~~chat** is connected:\n- Search for relevant team discussions and decisions\n- Find blockers or issues raised in channels\n- Identify key decisions made asynchronously\n\nIf **~~meeting transcription** is connected:\n- Pull recent meeting notes and discussion summaries\n- Find decisions and action items from relevant meetings\n\nIf **~~knowledge base** is connected:\n- Search for recent meeting notes\n- Find decision documents or design reviews\n\nIf no tools are connected, ask the user to provide:\n- What was accomplished since the last update\n- Current blockers or risks\n- Key decisions made or needed\n- What is coming next\n\n### 4. Generate the Update\n\nStructure the update for the target audience using the templates and frameworks below.\n\n**For executives**: TL;DR, status color (G\u002FY\u002FR), key progress tied to goals, decisions made, risks with mitigation, specific asks, and next milestones. Keep it under 300 words.\n\n**For engineering**: What shipped (with links), what is in progress (with owners), blockers, decisions needed (with options and recommendation), and what is coming next.\n\n**For cross-functional partners**: What is coming that affects them, what you need from them (with deadlines), decisions that impact their team, and areas open for input.\n\n**For customers**: What is new (framed as benefits), what is coming soon, known issues with workarounds, and how to provide feedback. No internal jargon.\n\n**For launch announcements**: What launched, why it matters, key details (scope, availability, limitations), success metrics, rollout plan, and feedback channels.\n\n### 5. Review and Deliver\n\nAfter generating the update:\n- Ask if the user wants to adjust tone, detail level, or emphasis\n- Offer to format for the delivery channel (email, chat post, doc, slides)\n- If **~~chat** is connected, offer to draft the message for sending\n\n## Update Templates by Audience\n\n### Executive \u002F Leadership Update\nExecutives want: strategic context, progress against goals, risks that need their help, decisions that need their input.\n\n**Format**:\n```\nStatus: [Green \u002F Yellow \u002F Red]\n\nTL;DR: [One sentence — the most important thing to know]\n\nProgress:\n- [Outcome achieved, tied to goal\u002FOKR]\n- [Milestone reached, with impact]\n- [Key metric movement]\n\nRisks:\n- [Risk]: [Mitigation plan]. [Ask if needed].\n\nDecisions needed:\n- [Decision]: [Options with recommendation]. Need by [date].\n\nNext milestones:\n- [Milestone] — [Date]\n```\n\n**Tips for executive updates**:\n- Lead with the conclusion, not the journey. Executives want \"we shipped X and it moved Y metric\" not \"we had 14 standups and resolved 23 tickets.\"\n- Keep it under 200 words. If they want more, they will ask.\n- Status color should reflect YOUR genuine assessment, not what you think they want to hear. Yellow is not a failure — it is good risk management.\n- Only include risks you want help with. Do not list risks you are already handling unless they need to know.\n- Asks must be specific: \"Decision on X by Friday\" not \"support needed.\"\n\n### Engineering Team Update\nEngineers want: clear priorities, technical context, blockers resolved, decisions that affect their work.\n\n**Format**:\n```\nShipped:\n- [Feature\u002Ffix] — [Link to PR\u002Fticket]. [Impact if notable].\n\nIn progress:\n- [Item] — [Owner]. [Expected completion]. [Blockers if any].\n\nDecisions:\n- [Decision made]: [Rationale]. [Link to ADR if exists].\n- [Decision needed]: [Context]. [Options]. [Recommendation].\n\nPriority changes:\n- [What changed and why]\n\nComing up:\n- [Next items] — [Context on why these are next]\n```\n\n**Tips for engineering updates**:\n- Link to specific tickets, PRs, and documents. Engineers want to click through for details.\n- When priorities change, explain why. Engineers are more bought in when they understand the reason.\n- Be explicit about what is blocking them and what you are doing to unblock it.\n- Do not waste their time with information that does not affect their work.\n\n### Cross-Functional Partner Update\nPartners (design, marketing, sales, support) want: what is coming that affects them, what they need to prepare for, how to give input.\n\n**Format**:\n```\nWhat's coming:\n- [Feature\u002Flaunch] — [Date]. [What this means for your team].\n\nWhat we need from you:\n- [Specific ask] — [Context]. By [date].\n\nDecisions made:\n- [Decision] — [How it affects your team].\n\nOpen for input:\n- [Topic we'd love feedback on] — [How to provide it].\n```\n\n### Customer \u002F External Update\nCustomers want: what is new, what is coming, how it benefits them, how to get started.\n\n**Format**:\n```\nWhat's new:\n- [Feature] — [Benefit in customer terms]. [How to use it \u002F link].\n\nComing soon:\n- [Feature] — [Expected timing]. [Why it matters to you].\n\nKnown issues:\n- [Issue] — [Status]. [Workaround if available].\n\nFeedback:\n- [How to share feedback or request features]\n```\n\n**Tips for customer updates**:\n- No internal jargon. No ticket numbers. No technical implementation details.\n- Frame everything in terms of what the customer can now DO, not what you built.\n- Be honest about timelines but do not overcommit. \"Later this quarter\" is better than a date you might miss.\n- Only mention known issues if they are customer-impacting and you have a resolution plan.\n\n## Status Reporting Framework\n\n### Green \u002F Yellow \u002F Red Status\n\n**Green** (On Track):\n- Progressing as planned\n- No significant risks or blockers\n- On track to meet commitments and deadlines\n- Use Green when things are genuinely going well — not as a default\n\n**Yellow** (At Risk):\n- Progress is slower than planned, or a risk has materialized\n- Mitigation is underway but outcome is uncertain\n- May miss commitments without intervention or scope adjustment\n- Use Yellow proactively — the earlier you flag risk, the more options you have\n\n**Red** (Off Track):\n- Significantly behind plan\n- Major blocker or risk without clear mitigation\n- Will miss commitments without significant intervention (scope cut, resource addition, timeline extension)\n- Use Red when you genuinely need help. Do not wait until it is too late.\n\n### When to Change Status\n- Move to Yellow at the FIRST sign of risk, not when you are sure things are bad\n- Move to Red when you have exhausted your own options and need escalation\n- Move back to Green only when the risk is genuinely resolved, not just paused\n- Document what changed when you change status — \"Moved to Yellow because [reason]\"\n\n## Risk Communication\n\n### ROAM Framework for Risk Management\n- **Resolved**: Risk is no longer a concern. Document how it was resolved.\n- **Owned**: Risk is acknowledged and someone is actively managing it. State the owner and the mitigation plan.\n- **Accepted**: Risk is known but we are choosing to proceed without mitigation. Document the rationale.\n- **Mitigated**: Actions have reduced the risk to an acceptable level. Document what was done.\n\n### Communicating Risks Effectively\n1. **State the risk clearly**: \"There is a risk that [thing] happens because [reason]\"\n2. **Quantify the impact**: \"If this happens, the consequence is [impact]\"\n3. **State the likelihood**: \"This is [likely\u002Fpossible\u002Funlikely] because [evidence]\"\n4. **Present the mitigation**: \"We are managing this by [actions]\"\n5. **Make the ask**: \"We need [specific help] to further reduce this risk\"\n\n### Common Mistakes in Risk Communication\n- Burying risks in good news. Lead with risks when they are important.\n- Being vague: \"There might be some delays\" — specify what, how long, and why.\n- Presenting risks without mitigations. Every risk should come with a plan.\n- Waiting too long. A risk communicated early is a planning input. A risk communicated late is a fire drill.\n\n## Decision Documentation (ADRs)\n\n### Architecture Decision Record Format\nDocument important decisions for future reference:\n\n```\n# [Decision Title]\n\n## Status\n[Proposed \u002F Accepted \u002F Deprecated \u002F Superseded by ADR-XXX]\n\n## Context\nWhat is the situation that requires a decision? What forces are at play?\n\n## Decision\nWhat did we decide? State the decision clearly and directly.\n\n## Consequences\nWhat are the implications of this decision?\n- Positive consequences\n- Negative consequences or tradeoffs accepted\n- What this enables or prevents in the future\n\n## Alternatives Considered\nWhat other options were evaluated?\nFor each: what was it, why was it rejected?\n```\n\n### When to Write an ADR\n- Strategic product decisions (which market segment to target, which platform to support)\n- Significant technical decisions (architecture choices, vendor selection, build vs buy)\n- Controversial decisions where people disagreed (document the rationale for future reference)\n- Decisions that constrain future options (choosing a technology, signing a partnership)\n- Decisions you expect people to question later (capture the context while it is fresh)\n\n### Tips for Decision Documentation\n- Write ADRs close to when the decision is made, not weeks later\n- Include who was involved in the decision and who made the final call\n- Document the context generously — future readers will not have today's context\n- It is okay to document decisions that were wrong in hindsight — add a \"superseded by\" link\n- Keep them short. One page is better than five.\n\n## Meeting Facilitation\n\n### Stand-up \u002F Daily Sync\n**Purpose**: Surface blockers, coordinate work, maintain momentum.\n**Format**: Each person shares:\n- What they accomplished since last sync\n- What they are working on next\n- What is blocking them\n\n**Facilitation tips**:\n- Keep it to 15 minutes. If discussions emerge, take them offline.\n- Focus on blockers — this is the highest-value part of standup\n- Track blockers and follow up on resolution\n- Cancel standup if there is nothing to sync on. Respect people's time.\n\n### Sprint \u002F Iteration Planning\n**Purpose**: Commit to work for the next sprint. Align on priorities and scope.\n**Format**:\n1. Review: what shipped last sprint, what carried over, what was cut\n2. Priorities: what are the most important things to accomplish this sprint\n3. Capacity: how much can the team take on (account for PTO, on-call, meetings)\n4. Commitment: select items from the backlog that fit capacity and priorities\n5. Dependencies: flag any cross-team or external dependencies\n\n**Facilitation tips**:\n- Come with a proposed priority order. Do not ask the team to prioritize from scratch.\n- Push back on overcommitment. It is better to commit to less and deliver reliably.\n- Ensure every item has a clear owner and clear acceptance criteria.\n- Flag items that are underscoped or have hidden complexity.\n\n### Retrospective\n**Purpose**: Reflect on what went well, what did not, and what to change.\n**Format**:\n1. Set the stage: remind the team of the goal and create psychological safety\n2. Gather data: what went well, what did not go well, what was confusing\n3. Generate insights: identify patterns and root causes\n4. Decide actions: pick 1-3 specific improvements to try next sprint\n5. Close: thank people for honest feedback\n\n**Facilitation tips**:\n- Create psychological safety. People must feel safe to be honest.\n- Focus on systems and processes, not individuals.\n- Limit to 1-3 action items. More than that and nothing changes.\n- Follow up on previous retro action items. If you never follow up, people stop engaging.\n- Vary the retro format occasionally to prevent staleness.\n\n### Stakeholder Review \u002F Demo\n**Purpose**: Show progress, gather feedback, build alignment.\n**Format**:\n1. Context: remind stakeholders of the goal and what they saw last time\n2. Demo: show what was built. Use real product, not slides.\n3. Metrics: share any early data or feedback\n4. Feedback: structured time for questions and input\n5. Next steps: what is coming next and when the next review will be\n\n**Facilitation tips**:\n- Demo the real product whenever possible. Slides are not demos.\n- Frame feedback collection: \"What feedback do you have on X?\" is better than \"Any thoughts?\"\n- Capture feedback visibly and commit to addressing it (or explaining why not)\n- Set expectations about what kind of feedback is actionable at this stage\n\n## Output Format\n\nKeep updates scannable. Use bold for key points, bullets for lists. Executive updates should be under 300 words. Engineering updates can be longer but should still be structured for skimming.\n\n## Tips\n\n- The most common mistake in stakeholder updates is burying the lead. Start with the most important thing.\n- Status colors (Green\u002FYellow\u002FRed) should reflect reality, not optimism. Yellow is not a failure — it is good risk communication.\n- Asks should be specific and actionable. \"We need help\" is not an ask. \"We need a decision on X by Friday\" is.\n- For executives, frame everything in terms of outcomes and goals, not activities and tasks.\n- If there is bad news, lead with it. Do not hide it after good news.\n- Match the length to the audience's attention. Executives get a few bullets. Engineering gets the details they need.\n",{"data":35,"body":37},{"name":4,"description":6,"argument-hint":36},"\u003Cupdate type and audience>",{"type":38,"children":39},"root",[40,48,67,72,79,92,98,105,110,156,162,167,220,226,238,261,271,289,299,312,322,335,340,363,369,374,384,394,404,414,424,430,435,458,464,470,475,485,494,503,531,537,542,550,559,568,591,597,602,610,619,625,630,638,647,656,679,685,691,701,724,734,757,767,790,796,827,833,839,882,888,986,992,1015,1021,1027,1032,1041,1047,1075,1081,1109,1115,1121,1137,1155,1164,1187,1193,1207,1235,1243,1266,1272,1286,1314,1322,1350,1356,1370,1398,1406,1429,1435,1440,1446],{"type":41,"tag":42,"props":43,"children":44},"element","h1",{"id":4},[45],{"type":46,"value":47},"text","Stakeholder Update",{"type":41,"tag":49,"props":50,"children":51},"blockquote",{},[52],{"type":41,"tag":53,"props":54,"children":55},"p",{},[56,58,65],{"type":46,"value":57},"If you see unfamiliar placeholders or need to check which tools are connected, see ",{"type":41,"tag":59,"props":60,"children":62},"a",{"href":61},"..\u002F..\u002FCONNECTORS.md",[63],{"type":46,"value":64},"CONNECTORS.md",{"type":46,"value":66},".",{"type":41,"tag":53,"props":68,"children":69},{},[70],{"type":46,"value":71},"Generate a stakeholder update tailored to the audience and cadence.",{"type":41,"tag":73,"props":74,"children":76},"h2",{"id":75},"usage",[77],{"type":46,"value":78},"Usage",{"type":41,"tag":80,"props":81,"children":85},"pre",{"className":82,"code":84,"language":46},[83],"language-text","\u002Fstakeholder-update $ARGUMENTS\n",[86],{"type":41,"tag":87,"props":88,"children":90},"code",{"__ignoreMap":89},"",[91],{"type":46,"value":84},{"type":41,"tag":73,"props":93,"children":95},{"id":94},"workflow",[96],{"type":46,"value":97},"Workflow",{"type":41,"tag":99,"props":100,"children":102},"h3",{"id":101},"_1-determine-update-type",[103],{"type":46,"value":104},"1. Determine Update Type",{"type":41,"tag":53,"props":106,"children":107},{},[108],{"type":46,"value":109},"Ask the user what kind of update:",{"type":41,"tag":111,"props":112,"children":113},"ul",{},[114,126,136,146],{"type":41,"tag":115,"props":116,"children":117},"li",{},[118,124],{"type":41,"tag":119,"props":120,"children":121},"strong",{},[122],{"type":46,"value":123},"Weekly",{"type":46,"value":125},": Regular cadence update on progress, blockers, and next steps",{"type":41,"tag":115,"props":127,"children":128},{},[129,134],{"type":41,"tag":119,"props":130,"children":131},{},[132],{"type":46,"value":133},"Monthly",{"type":46,"value":135},": Higher-level summary with trends, milestones, and strategic alignment",{"type":41,"tag":115,"props":137,"children":138},{},[139,144],{"type":41,"tag":119,"props":140,"children":141},{},[142],{"type":46,"value":143},"Launch",{"type":46,"value":145},": Announcement of a feature or product launch with details and impact",{"type":41,"tag":115,"props":147,"children":148},{},[149,154],{"type":41,"tag":119,"props":150,"children":151},{},[152],{"type":46,"value":153},"Ad-hoc",{"type":46,"value":155},": One-off update for a specific situation (escalation, pivot, major decision)",{"type":41,"tag":99,"props":157,"children":159},{"id":158},"_2-determine-audience",[160],{"type":46,"value":161},"2. Determine Audience",{"type":41,"tag":53,"props":163,"children":164},{},[165],{"type":46,"value":166},"Ask who the update is for:",{"type":41,"tag":111,"props":168,"children":169},{},[170,180,190,200,210],{"type":41,"tag":115,"props":171,"children":172},{},[173,178],{"type":41,"tag":119,"props":174,"children":175},{},[176],{"type":46,"value":177},"Executives \u002F leadership",{"type":46,"value":179},": High-level, outcome-focused, strategic framing, brief",{"type":41,"tag":115,"props":181,"children":182},{},[183,188],{"type":41,"tag":119,"props":184,"children":185},{},[186],{"type":46,"value":187},"Engineering team",{"type":46,"value":189},": Technical detail, implementation context, blockers, decisions needed",{"type":41,"tag":115,"props":191,"children":192},{},[193,198],{"type":41,"tag":119,"props":194,"children":195},{},[196],{"type":46,"value":197},"Cross-functional partners",{"type":46,"value":199},": Context-appropriate detail, focus on shared goals and dependencies",{"type":41,"tag":115,"props":201,"children":202},{},[203,208],{"type":41,"tag":119,"props":204,"children":205},{},[206],{"type":46,"value":207},"Customers \u002F external",{"type":46,"value":209},": Benefits-focused, clear timelines, no internal jargon",{"type":41,"tag":115,"props":211,"children":212},{},[213,218],{"type":41,"tag":119,"props":214,"children":215},{},[216],{"type":46,"value":217},"Board",{"type":46,"value":219},": Metrics-driven, strategic, risk-focused, very concise",{"type":41,"tag":99,"props":221,"children":223},{"id":222},"_3-pull-context-from-connected-tools",[224],{"type":46,"value":225},"3. Pull Context from Connected Tools",{"type":41,"tag":53,"props":227,"children":228},{},[229,231,236],{"type":46,"value":230},"If ",{"type":41,"tag":119,"props":232,"children":233},{},[234],{"type":46,"value":235},"~~project tracker",{"type":46,"value":237}," is connected:",{"type":41,"tag":111,"props":239,"children":240},{},[241,246,251,256],{"type":41,"tag":115,"props":242,"children":243},{},[244],{"type":46,"value":245},"Pull status of roadmap items and milestones",{"type":41,"tag":115,"props":247,"children":248},{},[249],{"type":46,"value":250},"Identify completed items since last update",{"type":41,"tag":115,"props":252,"children":253},{},[254],{"type":46,"value":255},"Surface items that are at risk or blocked",{"type":41,"tag":115,"props":257,"children":258},{},[259],{"type":46,"value":260},"Pull sprint or iteration progress",{"type":41,"tag":53,"props":262,"children":263},{},[264,265,270],{"type":46,"value":230},{"type":41,"tag":119,"props":266,"children":267},{},[268],{"type":46,"value":269},"~~chat",{"type":46,"value":237},{"type":41,"tag":111,"props":272,"children":273},{},[274,279,284],{"type":41,"tag":115,"props":275,"children":276},{},[277],{"type":46,"value":278},"Search for relevant team discussions and decisions",{"type":41,"tag":115,"props":280,"children":281},{},[282],{"type":46,"value":283},"Find blockers or issues raised in channels",{"type":41,"tag":115,"props":285,"children":286},{},[287],{"type":46,"value":288},"Identify key decisions made asynchronously",{"type":41,"tag":53,"props":290,"children":291},{},[292,293,298],{"type":46,"value":230},{"type":41,"tag":119,"props":294,"children":295},{},[296],{"type":46,"value":297},"~~meeting transcription",{"type":46,"value":237},{"type":41,"tag":111,"props":300,"children":301},{},[302,307],{"type":41,"tag":115,"props":303,"children":304},{},[305],{"type":46,"value":306},"Pull recent meeting notes and discussion summaries",{"type":41,"tag":115,"props":308,"children":309},{},[310],{"type":46,"value":311},"Find decisions and action items from relevant meetings",{"type":41,"tag":53,"props":313,"children":314},{},[315,316,321],{"type":46,"value":230},{"type":41,"tag":119,"props":317,"children":318},{},[319],{"type":46,"value":320},"~~knowledge base",{"type":46,"value":237},{"type":41,"tag":111,"props":323,"children":324},{},[325,330],{"type":41,"tag":115,"props":326,"children":327},{},[328],{"type":46,"value":329},"Search for recent meeting notes",{"type":41,"tag":115,"props":331,"children":332},{},[333],{"type":46,"value":334},"Find decision documents or design reviews",{"type":41,"tag":53,"props":336,"children":337},{},[338],{"type":46,"value":339},"If no tools are connected, ask the user to provide:",{"type":41,"tag":111,"props":341,"children":342},{},[343,348,353,358],{"type":41,"tag":115,"props":344,"children":345},{},[346],{"type":46,"value":347},"What was accomplished since the last update",{"type":41,"tag":115,"props":349,"children":350},{},[351],{"type":46,"value":352},"Current blockers or risks",{"type":41,"tag":115,"props":354,"children":355},{},[356],{"type":46,"value":357},"Key decisions made or needed",{"type":41,"tag":115,"props":359,"children":360},{},[361],{"type":46,"value":362},"What is coming next",{"type":41,"tag":99,"props":364,"children":366},{"id":365},"_4-generate-the-update",[367],{"type":46,"value":368},"4. Generate the Update",{"type":41,"tag":53,"props":370,"children":371},{},[372],{"type":46,"value":373},"Structure the update for the target audience using the templates and frameworks below.",{"type":41,"tag":53,"props":375,"children":376},{},[377,382],{"type":41,"tag":119,"props":378,"children":379},{},[380],{"type":46,"value":381},"For executives",{"type":46,"value":383},": TL;DR, status color (G\u002FY\u002FR), key progress tied to goals, decisions made, risks with mitigation, specific asks, and next milestones. Keep it under 300 words.",{"type":41,"tag":53,"props":385,"children":386},{},[387,392],{"type":41,"tag":119,"props":388,"children":389},{},[390],{"type":46,"value":391},"For engineering",{"type":46,"value":393},": What shipped (with links), what is in progress (with owners), blockers, decisions needed (with options and recommendation), and what is coming next.",{"type":41,"tag":53,"props":395,"children":396},{},[397,402],{"type":41,"tag":119,"props":398,"children":399},{},[400],{"type":46,"value":401},"For cross-functional partners",{"type":46,"value":403},": What is coming that affects them, what you need from them (with deadlines), decisions that impact their team, and areas open for input.",{"type":41,"tag":53,"props":405,"children":406},{},[407,412],{"type":41,"tag":119,"props":408,"children":409},{},[410],{"type":46,"value":411},"For customers",{"type":46,"value":413},": What is new (framed as benefits), what is coming soon, known issues with workarounds, and how to provide feedback. No internal jargon.",{"type":41,"tag":53,"props":415,"children":416},{},[417,422],{"type":41,"tag":119,"props":418,"children":419},{},[420],{"type":46,"value":421},"For launch announcements",{"type":46,"value":423},": What launched, why it matters, key details (scope, availability, limitations), success metrics, rollout plan, and feedback channels.",{"type":41,"tag":99,"props":425,"children":427},{"id":426},"_5-review-and-deliver",[428],{"type":46,"value":429},"5. Review and Deliver",{"type":41,"tag":53,"props":431,"children":432},{},[433],{"type":46,"value":434},"After generating the update:",{"type":41,"tag":111,"props":436,"children":437},{},[438,443,448],{"type":41,"tag":115,"props":439,"children":440},{},[441],{"type":46,"value":442},"Ask if the user wants to adjust tone, detail level, or emphasis",{"type":41,"tag":115,"props":444,"children":445},{},[446],{"type":46,"value":447},"Offer to format for the delivery channel (email, chat post, doc, slides)",{"type":41,"tag":115,"props":449,"children":450},{},[451,452,456],{"type":46,"value":230},{"type":41,"tag":119,"props":453,"children":454},{},[455],{"type":46,"value":269},{"type":46,"value":457}," is connected, offer to draft the message for sending",{"type":41,"tag":73,"props":459,"children":461},{"id":460},"update-templates-by-audience",[462],{"type":46,"value":463},"Update Templates by Audience",{"type":41,"tag":99,"props":465,"children":467},{"id":466},"executive-leadership-update",[468],{"type":46,"value":469},"Executive \u002F Leadership Update",{"type":41,"tag":53,"props":471,"children":472},{},[473],{"type":46,"value":474},"Executives want: strategic context, progress against goals, risks that need their help, decisions that need their input.",{"type":41,"tag":53,"props":476,"children":477},{},[478,483],{"type":41,"tag":119,"props":479,"children":480},{},[481],{"type":46,"value":482},"Format",{"type":46,"value":484},":",{"type":41,"tag":80,"props":486,"children":489},{"className":487,"code":488,"language":46},[83],"Status: [Green \u002F Yellow \u002F Red]\n\nTL;DR: [One sentence — the most important thing to know]\n\nProgress:\n- [Outcome achieved, tied to goal\u002FOKR]\n- [Milestone reached, with impact]\n- [Key metric movement]\n\nRisks:\n- [Risk]: [Mitigation plan]. [Ask if needed].\n\nDecisions needed:\n- [Decision]: [Options with recommendation]. Need by [date].\n\nNext milestones:\n- [Milestone] — [Date]\n",[490],{"type":41,"tag":87,"props":491,"children":492},{"__ignoreMap":89},[493],{"type":46,"value":488},{"type":41,"tag":53,"props":495,"children":496},{},[497,502],{"type":41,"tag":119,"props":498,"children":499},{},[500],{"type":46,"value":501},"Tips for executive updates",{"type":46,"value":484},{"type":41,"tag":111,"props":504,"children":505},{},[506,511,516,521,526],{"type":41,"tag":115,"props":507,"children":508},{},[509],{"type":46,"value":510},"Lead with the conclusion, not the journey. Executives want \"we shipped X and it moved Y metric\" not \"we had 14 standups and resolved 23 tickets.\"",{"type":41,"tag":115,"props":512,"children":513},{},[514],{"type":46,"value":515},"Keep it under 200 words. If they want more, they will ask.",{"type":41,"tag":115,"props":517,"children":518},{},[519],{"type":46,"value":520},"Status color should reflect YOUR genuine assessment, not what you think they want to hear. Yellow is not a failure — it is good risk management.",{"type":41,"tag":115,"props":522,"children":523},{},[524],{"type":46,"value":525},"Only include risks you want help with. Do not list risks you are already handling unless they need to know.",{"type":41,"tag":115,"props":527,"children":528},{},[529],{"type":46,"value":530},"Asks must be specific: \"Decision on X by Friday\" not \"support needed.\"",{"type":41,"tag":99,"props":532,"children":534},{"id":533},"engineering-team-update",[535],{"type":46,"value":536},"Engineering Team Update",{"type":41,"tag":53,"props":538,"children":539},{},[540],{"type":46,"value":541},"Engineers want: clear priorities, technical context, blockers resolved, decisions that affect their work.",{"type":41,"tag":53,"props":543,"children":544},{},[545,549],{"type":41,"tag":119,"props":546,"children":547},{},[548],{"type":46,"value":482},{"type":46,"value":484},{"type":41,"tag":80,"props":551,"children":554},{"className":552,"code":553,"language":46},[83],"Shipped:\n- [Feature\u002Ffix] — [Link to PR\u002Fticket]. [Impact if notable].\n\nIn progress:\n- [Item] — [Owner]. [Expected completion]. [Blockers if any].\n\nDecisions:\n- [Decision made]: [Rationale]. [Link to ADR if exists].\n- [Decision needed]: [Context]. [Options]. [Recommendation].\n\nPriority changes:\n- [What changed and why]\n\nComing up:\n- [Next items] — [Context on why these are next]\n",[555],{"type":41,"tag":87,"props":556,"children":557},{"__ignoreMap":89},[558],{"type":46,"value":553},{"type":41,"tag":53,"props":560,"children":561},{},[562,567],{"type":41,"tag":119,"props":563,"children":564},{},[565],{"type":46,"value":566},"Tips for engineering updates",{"type":46,"value":484},{"type":41,"tag":111,"props":569,"children":570},{},[571,576,581,586],{"type":41,"tag":115,"props":572,"children":573},{},[574],{"type":46,"value":575},"Link to specific tickets, PRs, and documents. Engineers want to click through for details.",{"type":41,"tag":115,"props":577,"children":578},{},[579],{"type":46,"value":580},"When priorities change, explain why. Engineers are more bought in when they understand the reason.",{"type":41,"tag":115,"props":582,"children":583},{},[584],{"type":46,"value":585},"Be explicit about what is blocking them and what you are doing to unblock it.",{"type":41,"tag":115,"props":587,"children":588},{},[589],{"type":46,"value":590},"Do not waste their time with information that does not affect their work.",{"type":41,"tag":99,"props":592,"children":594},{"id":593},"cross-functional-partner-update",[595],{"type":46,"value":596},"Cross-Functional Partner Update",{"type":41,"tag":53,"props":598,"children":599},{},[600],{"type":46,"value":601},"Partners (design, marketing, sales, support) want: what is coming that affects them, what they need to prepare for, how to give input.",{"type":41,"tag":53,"props":603,"children":604},{},[605,609],{"type":41,"tag":119,"props":606,"children":607},{},[608],{"type":46,"value":482},{"type":46,"value":484},{"type":41,"tag":80,"props":611,"children":614},{"className":612,"code":613,"language":46},[83],"What's coming:\n- [Feature\u002Flaunch] — [Date]. [What this means for your team].\n\nWhat we need from you:\n- [Specific ask] — [Context]. By [date].\n\nDecisions made:\n- [Decision] — [How it affects your team].\n\nOpen for input:\n- [Topic we'd love feedback on] — [How to provide it].\n",[615],{"type":41,"tag":87,"props":616,"children":617},{"__ignoreMap":89},[618],{"type":46,"value":613},{"type":41,"tag":99,"props":620,"children":622},{"id":621},"customer-external-update",[623],{"type":46,"value":624},"Customer \u002F External Update",{"type":41,"tag":53,"props":626,"children":627},{},[628],{"type":46,"value":629},"Customers want: what is new, what is coming, how it benefits them, how to get started.",{"type":41,"tag":53,"props":631,"children":632},{},[633,637],{"type":41,"tag":119,"props":634,"children":635},{},[636],{"type":46,"value":482},{"type":46,"value":484},{"type":41,"tag":80,"props":639,"children":642},{"className":640,"code":641,"language":46},[83],"What's new:\n- [Feature] — [Benefit in customer terms]. [How to use it \u002F link].\n\nComing soon:\n- [Feature] — [Expected timing]. [Why it matters to you].\n\nKnown issues:\n- [Issue] — [Status]. [Workaround if available].\n\nFeedback:\n- [How to share feedback or request features]\n",[643],{"type":41,"tag":87,"props":644,"children":645},{"__ignoreMap":89},[646],{"type":46,"value":641},{"type":41,"tag":53,"props":648,"children":649},{},[650,655],{"type":41,"tag":119,"props":651,"children":652},{},[653],{"type":46,"value":654},"Tips for customer updates",{"type":46,"value":484},{"type":41,"tag":111,"props":657,"children":658},{},[659,664,669,674],{"type":41,"tag":115,"props":660,"children":661},{},[662],{"type":46,"value":663},"No internal jargon. No ticket numbers. No technical implementation details.",{"type":41,"tag":115,"props":665,"children":666},{},[667],{"type":46,"value":668},"Frame everything in terms of what the customer can now DO, not what you built.",{"type":41,"tag":115,"props":670,"children":671},{},[672],{"type":46,"value":673},"Be honest about timelines but do not overcommit. \"Later this quarter\" is better than a date you might miss.",{"type":41,"tag":115,"props":675,"children":676},{},[677],{"type":46,"value":678},"Only mention known issues if they are customer-impacting and you have a resolution plan.",{"type":41,"tag":73,"props":680,"children":682},{"id":681},"status-reporting-framework",[683],{"type":46,"value":684},"Status Reporting Framework",{"type":41,"tag":99,"props":686,"children":688},{"id":687},"green-yellow-red-status",[689],{"type":46,"value":690},"Green \u002F Yellow \u002F Red Status",{"type":41,"tag":53,"props":692,"children":693},{},[694,699],{"type":41,"tag":119,"props":695,"children":696},{},[697],{"type":46,"value":698},"Green",{"type":46,"value":700}," (On Track):",{"type":41,"tag":111,"props":702,"children":703},{},[704,709,714,719],{"type":41,"tag":115,"props":705,"children":706},{},[707],{"type":46,"value":708},"Progressing as planned",{"type":41,"tag":115,"props":710,"children":711},{},[712],{"type":46,"value":713},"No significant risks or blockers",{"type":41,"tag":115,"props":715,"children":716},{},[717],{"type":46,"value":718},"On track to meet commitments and deadlines",{"type":41,"tag":115,"props":720,"children":721},{},[722],{"type":46,"value":723},"Use Green when things are genuinely going well — not as a default",{"type":41,"tag":53,"props":725,"children":726},{},[727,732],{"type":41,"tag":119,"props":728,"children":729},{},[730],{"type":46,"value":731},"Yellow",{"type":46,"value":733}," (At Risk):",{"type":41,"tag":111,"props":735,"children":736},{},[737,742,747,752],{"type":41,"tag":115,"props":738,"children":739},{},[740],{"type":46,"value":741},"Progress is slower than planned, or a risk has materialized",{"type":41,"tag":115,"props":743,"children":744},{},[745],{"type":46,"value":746},"Mitigation is underway but outcome is uncertain",{"type":41,"tag":115,"props":748,"children":749},{},[750],{"type":46,"value":751},"May miss commitments without intervention or scope adjustment",{"type":41,"tag":115,"props":753,"children":754},{},[755],{"type":46,"value":756},"Use Yellow proactively — the earlier you flag risk, the more options you have",{"type":41,"tag":53,"props":758,"children":759},{},[760,765],{"type":41,"tag":119,"props":761,"children":762},{},[763],{"type":46,"value":764},"Red",{"type":46,"value":766}," (Off Track):",{"type":41,"tag":111,"props":768,"children":769},{},[770,775,780,785],{"type":41,"tag":115,"props":771,"children":772},{},[773],{"type":46,"value":774},"Significantly behind plan",{"type":41,"tag":115,"props":776,"children":777},{},[778],{"type":46,"value":779},"Major blocker or risk without clear mitigation",{"type":41,"tag":115,"props":781,"children":782},{},[783],{"type":46,"value":784},"Will miss commitments without significant intervention (scope cut, resource addition, timeline extension)",{"type":41,"tag":115,"props":786,"children":787},{},[788],{"type":46,"value":789},"Use Red when you genuinely need help. Do not wait until it is too late.",{"type":41,"tag":99,"props":791,"children":793},{"id":792},"when-to-change-status",[794],{"type":46,"value":795},"When to Change Status",{"type":41,"tag":111,"props":797,"children":798},{},[799,804,809,814],{"type":41,"tag":115,"props":800,"children":801},{},[802],{"type":46,"value":803},"Move to Yellow at the FIRST sign of risk, not when you are sure things are bad",{"type":41,"tag":115,"props":805,"children":806},{},[807],{"type":46,"value":808},"Move to Red when you have exhausted your own options and need escalation",{"type":41,"tag":115,"props":810,"children":811},{},[812],{"type":46,"value":813},"Move back to Green only when the risk is genuinely resolved, not just paused",{"type":41,"tag":115,"props":815,"children":816},{},[817,819,825],{"type":46,"value":818},"Document what changed when you change status — \"Moved to Yellow because ",{"type":41,"tag":820,"props":821,"children":822},"span",{},[823],{"type":46,"value":824},"reason",{"type":46,"value":826},"\"",{"type":41,"tag":73,"props":828,"children":830},{"id":829},"risk-communication",[831],{"type":46,"value":832},"Risk Communication",{"type":41,"tag":99,"props":834,"children":836},{"id":835},"roam-framework-for-risk-management",[837],{"type":46,"value":838},"ROAM Framework for Risk Management",{"type":41,"tag":111,"props":840,"children":841},{},[842,852,862,872],{"type":41,"tag":115,"props":843,"children":844},{},[845,850],{"type":41,"tag":119,"props":846,"children":847},{},[848],{"type":46,"value":849},"Resolved",{"type":46,"value":851},": Risk is no longer a concern. Document how it was resolved.",{"type":41,"tag":115,"props":853,"children":854},{},[855,860],{"type":41,"tag":119,"props":856,"children":857},{},[858],{"type":46,"value":859},"Owned",{"type":46,"value":861},": Risk is acknowledged and someone is actively managing it. State the owner and the mitigation plan.",{"type":41,"tag":115,"props":863,"children":864},{},[865,870],{"type":41,"tag":119,"props":866,"children":867},{},[868],{"type":46,"value":869},"Accepted",{"type":46,"value":871},": Risk is known but we are choosing to proceed without mitigation. Document the rationale.",{"type":41,"tag":115,"props":873,"children":874},{},[875,880],{"type":41,"tag":119,"props":876,"children":877},{},[878],{"type":46,"value":879},"Mitigated",{"type":46,"value":881},": Actions have reduced the risk to an acceptable level. Document what was done.",{"type":41,"tag":99,"props":883,"children":885},{"id":884},"communicating-risks-effectively",[886],{"type":46,"value":887},"Communicating Risks Effectively",{"type":41,"tag":889,"props":890,"children":891},"ol",{},[892,914,930,953,969],{"type":41,"tag":115,"props":893,"children":894},{},[895,900,902,907,909,913],{"type":41,"tag":119,"props":896,"children":897},{},[898],{"type":46,"value":899},"State the risk clearly",{"type":46,"value":901},": \"There is a risk that ",{"type":41,"tag":820,"props":903,"children":904},{},[905],{"type":46,"value":906},"thing",{"type":46,"value":908}," happens because ",{"type":41,"tag":820,"props":910,"children":911},{},[912],{"type":46,"value":824},{"type":46,"value":826},{"type":41,"tag":115,"props":915,"children":916},{},[917,922,924,929],{"type":41,"tag":119,"props":918,"children":919},{},[920],{"type":46,"value":921},"Quantify the impact",{"type":46,"value":923},": \"If this happens, the consequence is ",{"type":41,"tag":820,"props":925,"children":926},{},[927],{"type":46,"value":928},"impact",{"type":46,"value":826},{"type":41,"tag":115,"props":931,"children":932},{},[933,938,940,945,947,952],{"type":41,"tag":119,"props":934,"children":935},{},[936],{"type":46,"value":937},"State the likelihood",{"type":46,"value":939},": \"This is ",{"type":41,"tag":820,"props":941,"children":942},{},[943],{"type":46,"value":944},"likely\u002Fpossible\u002Funlikely",{"type":46,"value":946}," because ",{"type":41,"tag":820,"props":948,"children":949},{},[950],{"type":46,"value":951},"evidence",{"type":46,"value":826},{"type":41,"tag":115,"props":954,"children":955},{},[956,961,963,968],{"type":41,"tag":119,"props":957,"children":958},{},[959],{"type":46,"value":960},"Present the mitigation",{"type":46,"value":962},": \"We are managing this by ",{"type":41,"tag":820,"props":964,"children":965},{},[966],{"type":46,"value":967},"actions",{"type":46,"value":826},{"type":41,"tag":115,"props":970,"children":971},{},[972,977,979,984],{"type":41,"tag":119,"props":973,"children":974},{},[975],{"type":46,"value":976},"Make the ask",{"type":46,"value":978},": \"We need ",{"type":41,"tag":820,"props":980,"children":981},{},[982],{"type":46,"value":983},"specific help",{"type":46,"value":985}," to further reduce this risk\"",{"type":41,"tag":99,"props":987,"children":989},{"id":988},"common-mistakes-in-risk-communication",[990],{"type":46,"value":991},"Common Mistakes in Risk Communication",{"type":41,"tag":111,"props":993,"children":994},{},[995,1000,1005,1010],{"type":41,"tag":115,"props":996,"children":997},{},[998],{"type":46,"value":999},"Burying risks in good news. Lead with risks when they are important.",{"type":41,"tag":115,"props":1001,"children":1002},{},[1003],{"type":46,"value":1004},"Being vague: \"There might be some delays\" — specify what, how long, and why.",{"type":41,"tag":115,"props":1006,"children":1007},{},[1008],{"type":46,"value":1009},"Presenting risks without mitigations. Every risk should come with a plan.",{"type":41,"tag":115,"props":1011,"children":1012},{},[1013],{"type":46,"value":1014},"Waiting too long. A risk communicated early is a planning input. A risk communicated late is a fire drill.",{"type":41,"tag":73,"props":1016,"children":1018},{"id":1017},"decision-documentation-adrs",[1019],{"type":46,"value":1020},"Decision Documentation (ADRs)",{"type":41,"tag":99,"props":1022,"children":1024},{"id":1023},"architecture-decision-record-format",[1025],{"type":46,"value":1026},"Architecture Decision Record Format",{"type":41,"tag":53,"props":1028,"children":1029},{},[1030],{"type":46,"value":1031},"Document important decisions for future reference:",{"type":41,"tag":80,"props":1033,"children":1036},{"className":1034,"code":1035,"language":46},[83],"# [Decision Title]\n\n## Status\n[Proposed \u002F Accepted \u002F Deprecated \u002F Superseded by ADR-XXX]\n\n## Context\nWhat is the situation that requires a decision? What forces are at play?\n\n## Decision\nWhat did we decide? State the decision clearly and directly.\n\n## Consequences\nWhat are the implications of this decision?\n- Positive consequences\n- Negative consequences or tradeoffs accepted\n- What this enables or prevents in the future\n\n## Alternatives Considered\nWhat other options were evaluated?\nFor each: what was it, why was it rejected?\n",[1037],{"type":41,"tag":87,"props":1038,"children":1039},{"__ignoreMap":89},[1040],{"type":46,"value":1035},{"type":41,"tag":99,"props":1042,"children":1044},{"id":1043},"when-to-write-an-adr",[1045],{"type":46,"value":1046},"When to Write an ADR",{"type":41,"tag":111,"props":1048,"children":1049},{},[1050,1055,1060,1065,1070],{"type":41,"tag":115,"props":1051,"children":1052},{},[1053],{"type":46,"value":1054},"Strategic product decisions (which market segment to target, which platform to support)",{"type":41,"tag":115,"props":1056,"children":1057},{},[1058],{"type":46,"value":1059},"Significant technical decisions (architecture choices, vendor selection, build vs buy)",{"type":41,"tag":115,"props":1061,"children":1062},{},[1063],{"type":46,"value":1064},"Controversial decisions where people disagreed (document the rationale for future reference)",{"type":41,"tag":115,"props":1066,"children":1067},{},[1068],{"type":46,"value":1069},"Decisions that constrain future options (choosing a technology, signing a partnership)",{"type":41,"tag":115,"props":1071,"children":1072},{},[1073],{"type":46,"value":1074},"Decisions you expect people to question later (capture the context while it is fresh)",{"type":41,"tag":99,"props":1076,"children":1078},{"id":1077},"tips-for-decision-documentation",[1079],{"type":46,"value":1080},"Tips for Decision Documentation",{"type":41,"tag":111,"props":1082,"children":1083},{},[1084,1089,1094,1099,1104],{"type":41,"tag":115,"props":1085,"children":1086},{},[1087],{"type":46,"value":1088},"Write ADRs close to when the decision is made, not weeks later",{"type":41,"tag":115,"props":1090,"children":1091},{},[1092],{"type":46,"value":1093},"Include who was involved in the decision and who made the final call",{"type":41,"tag":115,"props":1095,"children":1096},{},[1097],{"type":46,"value":1098},"Document the context generously — future readers will not have today's context",{"type":41,"tag":115,"props":1100,"children":1101},{},[1102],{"type":46,"value":1103},"It is okay to document decisions that were wrong in hindsight — add a \"superseded by\" link",{"type":41,"tag":115,"props":1105,"children":1106},{},[1107],{"type":46,"value":1108},"Keep them short. One page is better than five.",{"type":41,"tag":73,"props":1110,"children":1112},{"id":1111},"meeting-facilitation",[1113],{"type":46,"value":1114},"Meeting Facilitation",{"type":41,"tag":99,"props":1116,"children":1118},{"id":1117},"stand-up-daily-sync",[1119],{"type":46,"value":1120},"Stand-up \u002F Daily Sync",{"type":41,"tag":53,"props":1122,"children":1123},{},[1124,1129,1131,1135],{"type":41,"tag":119,"props":1125,"children":1126},{},[1127],{"type":46,"value":1128},"Purpose",{"type":46,"value":1130},": Surface blockers, coordinate work, maintain momentum.\n",{"type":41,"tag":119,"props":1132,"children":1133},{},[1134],{"type":46,"value":482},{"type":46,"value":1136},": Each person shares:",{"type":41,"tag":111,"props":1138,"children":1139},{},[1140,1145,1150],{"type":41,"tag":115,"props":1141,"children":1142},{},[1143],{"type":46,"value":1144},"What they accomplished since last sync",{"type":41,"tag":115,"props":1146,"children":1147},{},[1148],{"type":46,"value":1149},"What they are working on next",{"type":41,"tag":115,"props":1151,"children":1152},{},[1153],{"type":46,"value":1154},"What is blocking them",{"type":41,"tag":53,"props":1156,"children":1157},{},[1158,1163],{"type":41,"tag":119,"props":1159,"children":1160},{},[1161],{"type":46,"value":1162},"Facilitation tips",{"type":46,"value":484},{"type":41,"tag":111,"props":1165,"children":1166},{},[1167,1172,1177,1182],{"type":41,"tag":115,"props":1168,"children":1169},{},[1170],{"type":46,"value":1171},"Keep it to 15 minutes. If discussions emerge, take them offline.",{"type":41,"tag":115,"props":1173,"children":1174},{},[1175],{"type":46,"value":1176},"Focus on blockers — this is the highest-value part of standup",{"type":41,"tag":115,"props":1178,"children":1179},{},[1180],{"type":46,"value":1181},"Track blockers and follow up on resolution",{"type":41,"tag":115,"props":1183,"children":1184},{},[1185],{"type":46,"value":1186},"Cancel standup if there is nothing to sync on. Respect people's time.",{"type":41,"tag":99,"props":1188,"children":1190},{"id":1189},"sprint-iteration-planning",[1191],{"type":46,"value":1192},"Sprint \u002F Iteration Planning",{"type":41,"tag":53,"props":1194,"children":1195},{},[1196,1200,1202,1206],{"type":41,"tag":119,"props":1197,"children":1198},{},[1199],{"type":46,"value":1128},{"type":46,"value":1201},": Commit to work for the next sprint. Align on priorities and scope.\n",{"type":41,"tag":119,"props":1203,"children":1204},{},[1205],{"type":46,"value":482},{"type":46,"value":484},{"type":41,"tag":889,"props":1208,"children":1209},{},[1210,1215,1220,1225,1230],{"type":41,"tag":115,"props":1211,"children":1212},{},[1213],{"type":46,"value":1214},"Review: what shipped last sprint, what carried over, what was cut",{"type":41,"tag":115,"props":1216,"children":1217},{},[1218],{"type":46,"value":1219},"Priorities: what are the most important things to accomplish this sprint",{"type":41,"tag":115,"props":1221,"children":1222},{},[1223],{"type":46,"value":1224},"Capacity: how much can the team take on (account for PTO, on-call, meetings)",{"type":41,"tag":115,"props":1226,"children":1227},{},[1228],{"type":46,"value":1229},"Commitment: select items from the backlog that fit capacity and priorities",{"type":41,"tag":115,"props":1231,"children":1232},{},[1233],{"type":46,"value":1234},"Dependencies: flag any cross-team or external dependencies",{"type":41,"tag":53,"props":1236,"children":1237},{},[1238,1242],{"type":41,"tag":119,"props":1239,"children":1240},{},[1241],{"type":46,"value":1162},{"type":46,"value":484},{"type":41,"tag":111,"props":1244,"children":1245},{},[1246,1251,1256,1261],{"type":41,"tag":115,"props":1247,"children":1248},{},[1249],{"type":46,"value":1250},"Come with a proposed priority order. Do not ask the team to prioritize from scratch.",{"type":41,"tag":115,"props":1252,"children":1253},{},[1254],{"type":46,"value":1255},"Push back on overcommitment. It is better to commit to less and deliver reliably.",{"type":41,"tag":115,"props":1257,"children":1258},{},[1259],{"type":46,"value":1260},"Ensure every item has a clear owner and clear acceptance criteria.",{"type":41,"tag":115,"props":1262,"children":1263},{},[1264],{"type":46,"value":1265},"Flag items that are underscoped or have hidden complexity.",{"type":41,"tag":99,"props":1267,"children":1269},{"id":1268},"retrospective",[1270],{"type":46,"value":1271},"Retrospective",{"type":41,"tag":53,"props":1273,"children":1274},{},[1275,1279,1281,1285],{"type":41,"tag":119,"props":1276,"children":1277},{},[1278],{"type":46,"value":1128},{"type":46,"value":1280},": Reflect on what went well, what did not, and what to change.\n",{"type":41,"tag":119,"props":1282,"children":1283},{},[1284],{"type":46,"value":482},{"type":46,"value":484},{"type":41,"tag":889,"props":1287,"children":1288},{},[1289,1294,1299,1304,1309],{"type":41,"tag":115,"props":1290,"children":1291},{},[1292],{"type":46,"value":1293},"Set the stage: remind the team of the goal and create psychological safety",{"type":41,"tag":115,"props":1295,"children":1296},{},[1297],{"type":46,"value":1298},"Gather data: what went well, what did not go well, what was confusing",{"type":41,"tag":115,"props":1300,"children":1301},{},[1302],{"type":46,"value":1303},"Generate insights: identify patterns and root causes",{"type":41,"tag":115,"props":1305,"children":1306},{},[1307],{"type":46,"value":1308},"Decide actions: pick 1-3 specific improvements to try next sprint",{"type":41,"tag":115,"props":1310,"children":1311},{},[1312],{"type":46,"value":1313},"Close: thank people for honest feedback",{"type":41,"tag":53,"props":1315,"children":1316},{},[1317,1321],{"type":41,"tag":119,"props":1318,"children":1319},{},[1320],{"type":46,"value":1162},{"type":46,"value":484},{"type":41,"tag":111,"props":1323,"children":1324},{},[1325,1330,1335,1340,1345],{"type":41,"tag":115,"props":1326,"children":1327},{},[1328],{"type":46,"value":1329},"Create psychological safety. People must feel safe to be honest.",{"type":41,"tag":115,"props":1331,"children":1332},{},[1333],{"type":46,"value":1334},"Focus on systems and processes, not individuals.",{"type":41,"tag":115,"props":1336,"children":1337},{},[1338],{"type":46,"value":1339},"Limit to 1-3 action items. More than that and nothing changes.",{"type":41,"tag":115,"props":1341,"children":1342},{},[1343],{"type":46,"value":1344},"Follow up on previous retro action items. If you never follow up, people stop engaging.",{"type":41,"tag":115,"props":1346,"children":1347},{},[1348],{"type":46,"value":1349},"Vary the retro format occasionally to prevent staleness.",{"type":41,"tag":99,"props":1351,"children":1353},{"id":1352},"stakeholder-review-demo",[1354],{"type":46,"value":1355},"Stakeholder Review \u002F Demo",{"type":41,"tag":53,"props":1357,"children":1358},{},[1359,1363,1365,1369],{"type":41,"tag":119,"props":1360,"children":1361},{},[1362],{"type":46,"value":1128},{"type":46,"value":1364},": Show progress, gather feedback, build alignment.\n",{"type":41,"tag":119,"props":1366,"children":1367},{},[1368],{"type":46,"value":482},{"type":46,"value":484},{"type":41,"tag":889,"props":1371,"children":1372},{},[1373,1378,1383,1388,1393],{"type":41,"tag":115,"props":1374,"children":1375},{},[1376],{"type":46,"value":1377},"Context: remind stakeholders of the goal and what they saw last time",{"type":41,"tag":115,"props":1379,"children":1380},{},[1381],{"type":46,"value":1382},"Demo: show what was built. Use real product, not slides.",{"type":41,"tag":115,"props":1384,"children":1385},{},[1386],{"type":46,"value":1387},"Metrics: share any early data or feedback",{"type":41,"tag":115,"props":1389,"children":1390},{},[1391],{"type":46,"value":1392},"Feedback: structured time for questions and input",{"type":41,"tag":115,"props":1394,"children":1395},{},[1396],{"type":46,"value":1397},"Next steps: what is coming next and when the next review will be",{"type":41,"tag":53,"props":1399,"children":1400},{},[1401,1405],{"type":41,"tag":119,"props":1402,"children":1403},{},[1404],{"type":46,"value":1162},{"type":46,"value":484},{"type":41,"tag":111,"props":1407,"children":1408},{},[1409,1414,1419,1424],{"type":41,"tag":115,"props":1410,"children":1411},{},[1412],{"type":46,"value":1413},"Demo the real product whenever possible. Slides are not demos.",{"type":41,"tag":115,"props":1415,"children":1416},{},[1417],{"type":46,"value":1418},"Frame feedback collection: \"What feedback do you have on X?\" is better than \"Any thoughts?\"",{"type":41,"tag":115,"props":1420,"children":1421},{},[1422],{"type":46,"value":1423},"Capture feedback visibly and commit to addressing it (or explaining why not)",{"type":41,"tag":115,"props":1425,"children":1426},{},[1427],{"type":46,"value":1428},"Set expectations about what kind of feedback is actionable at this stage",{"type":41,"tag":73,"props":1430,"children":1432},{"id":1431},"output-format",[1433],{"type":46,"value":1434},"Output Format",{"type":41,"tag":53,"props":1436,"children":1437},{},[1438],{"type":46,"value":1439},"Keep updates scannable. Use bold for key points, bullets for lists. Executive updates should be under 300 words. Engineering updates can be longer but should still be structured for skimming.",{"type":41,"tag":73,"props":1441,"children":1443},{"id":1442},"tips",[1444],{"type":46,"value":1445},"Tips",{"type":41,"tag":111,"props":1447,"children":1448},{},[1449,1454,1459,1464,1469,1474],{"type":41,"tag":115,"props":1450,"children":1451},{},[1452],{"type":46,"value":1453},"The most common mistake in stakeholder updates is burying the lead. Start with the most important thing.",{"type":41,"tag":115,"props":1455,"children":1456},{},[1457],{"type":46,"value":1458},"Status colors (Green\u002FYellow\u002FRed) should reflect reality, not optimism. Yellow is not a failure — it is good risk communication.",{"type":41,"tag":115,"props":1460,"children":1461},{},[1462],{"type":46,"value":1463},"Asks should be specific and actionable. \"We need help\" is not an ask. \"We need a decision on X by Friday\" is.",{"type":41,"tag":115,"props":1465,"children":1466},{},[1467],{"type":46,"value":1468},"For executives, frame everything in terms of outcomes and goals, not activities and tasks.",{"type":41,"tag":115,"props":1470,"children":1471},{},[1472],{"type":46,"value":1473},"If there is bad news, lead with it. Do not hide it after good news.",{"type":41,"tag":115,"props":1475,"children":1476},{},[1477],{"type":46,"value":1478},"Match the length to the audience's attention. Executives get a few bullets. Engineering gets the details they need.",{"items":1480,"total":1595},[1481,1497,1513,1529,1547,1566,1582],{"slug":1482,"name":1482,"fn":1483,"description":1484,"org":1485,"tags":1486,"stars":23,"repoUrl":24,"updatedAt":1496},"accessibility-review","run WCAG accessibility audits","Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with \"audit accessibility\", \"check a11y\", \"is this accessible?\", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1487,1490,1493],{"name":1488,"slug":1489,"type":16},"Accessibility","accessibility",{"name":1491,"slug":1492,"type":16},"Design","design",{"name":1494,"slug":1495,"type":16},"WCAG","wcag","2026-04-06T17:58:05.682394",{"slug":1498,"name":1498,"fn":1499,"description":1500,"org":1501,"tags":1502,"stars":23,"repoUrl":24,"updatedAt":1512},"account-research","research accounts for sales intel","Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with \"research [company]\", \"look up [person]\", \"intel on [prospect]\", \"who is [name] at [company]\", or \"tell me about [company]\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1503,1506,1509],{"name":1504,"slug":1505,"type":16},"CRM","crm",{"name":1507,"slug":1508,"type":16},"Research","research",{"name":1510,"slug":1511,"type":16},"Sales","sales","2026-04-06T17:56:41.410418",{"slug":1514,"name":1514,"fn":1515,"description":1516,"org":1517,"tags":1518,"stars":23,"repoUrl":24,"updatedAt":1528},"analyze","answer data questions and run analyses","Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1519,1522,1525],{"name":1520,"slug":1521,"type":16},"Analytics","analytics",{"name":1523,"slug":1524,"type":16},"Data Analysis","data-analysis",{"name":1526,"slug":1527,"type":16},"SQL","sql","2026-04-06T17:57:21.593647",{"slug":1530,"name":1530,"fn":1531,"description":1532,"org":1533,"tags":1534,"stars":23,"repoUrl":24,"updatedAt":1546},"architecture","create and evaluate architecture decision records","Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1535,1538,1540,1543],{"name":1536,"slug":1537,"type":16},"ADR","adr",{"name":1539,"slug":1530,"type":16},"Architecture",{"name":1541,"slug":1542,"type":16},"Documentation","documentation",{"name":1544,"slug":1545,"type":16},"Engineering","engineering","2026-04-06T17:57:49.26444",{"slug":1548,"name":1548,"fn":1549,"description":1550,"org":1551,"tags":1552,"stars":23,"repoUrl":24,"updatedAt":1565},"audit-support","support SOX 404 control testing","Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1553,1556,1559,1562],{"name":1554,"slug":1555,"type":16},"Audit","audit",{"name":1557,"slug":1558,"type":16},"Finance","finance",{"name":1560,"slug":1561,"type":16},"Regulatory Compliance","regulatory-compliance",{"name":1563,"slug":1564,"type":16},"SOX","sox","2026-04-06T17:57:36.714815",{"slug":1567,"name":1567,"fn":1568,"description":1569,"org":1570,"tags":1571,"stars":23,"repoUrl":24,"updatedAt":1581},"brand-review","review content against brand voice","Review content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before\u002Fafter fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1572,1575,1578],{"name":1573,"slug":1574,"type":16},"Branding","branding",{"name":1576,"slug":1577,"type":16},"Marketing","marketing",{"name":1579,"slug":1580,"type":16},"Writing","writing","2026-04-06T17:58:19.548331",{"slug":1583,"name":1583,"fn":1584,"description":1585,"org":1586,"tags":1587,"stars":23,"repoUrl":24,"updatedAt":1594},"brand-voice-enforcement","enforce brand voice in content","This skill applies brand guidelines to content creation. It should be used when the user asks to \"write an email\", \"draft a proposal\", \"create a pitch deck\", \"write a LinkedIn post\", \"draft a presentation\", \"write a Slack message\", \"draft sales content\", or any content creation request where brand voice should be applied. Also triggers on \"on-brand\", \"brand voice\", \"enforce voice\", \"apply brand guidelines\", \"brand-aligned content\", \"write in our voice\", \"use our brand tone\", \"make this sound like us\", \"rewrite this in our tone\", or \"this doesn't sound on-brand\". Not for generating guidelines from scratch (use guideline-generation) or discovering brand materials (use discover-brand).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1588,1589,1590,1593],{"name":1573,"slug":1574,"type":16},{"name":21,"slug":22,"type":16},{"name":1591,"slug":1592,"type":16},"Content Creation","content-creation",{"name":1579,"slug":1580,"type":16},"2026-04-06T18:00:23.528956",200,{"items":1597,"total":1774},[1598,1617,1629,1641,1660,1671,1692,1712,1722,1737,1745,1758],{"slug":1599,"name":1599,"fn":1600,"description":1601,"org":1602,"tags":1603,"stars":1614,"repoUrl":1615,"updatedAt":1616},"algorithmic-art","create algorithmic art with p5.js","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1604,1607,1608,1611],{"name":1605,"slug":1606,"type":16},"Creative","creative",{"name":1491,"slug":1492,"type":16},{"name":1609,"slug":1610,"type":16},"Generative Art","generative-art",{"name":1612,"slug":1613,"type":16},"JavaScript","javascript",161831,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills","2026-04-06T17:56:15.455818",{"slug":1618,"name":1618,"fn":1619,"description":1620,"org":1621,"tags":1622,"stars":1614,"repoUrl":1615,"updatedAt":1628},"brand-guidelines","apply Anthropic brand colors and typography","Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1623,1624,1625],{"name":1573,"slug":1574,"type":16},{"name":1491,"slug":1492,"type":16},{"name":1626,"slug":1627,"type":16},"Typography","typography","2026-04-06T17:56:05.042852",{"slug":1630,"name":1630,"fn":1631,"description":1632,"org":1633,"tags":1634,"stars":1614,"repoUrl":1615,"updatedAt":1640},"canvas-design","create posters and visual art as PNG or PDF","Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1635,1636,1637],{"name":1605,"slug":1606,"type":16},{"name":1491,"slug":1492,"type":16},{"name":1638,"slug":1639,"type":16},"PDF","pdf","2026-04-06T17:56:03.794732",{"slug":1642,"name":1642,"fn":1643,"description":1644,"org":1645,"tags":1646,"stars":1614,"repoUrl":1615,"updatedAt":1659},"claude-api","build apps with the Claude API","Reference for the Claude API \u002F Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration.\nTRIGGER — read BEFORE opening the target file; don't skip because it \"looks like a one-liner\" — whenever: the prompt names Claude\u002FAnthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing\u002Fmodel choice\u002Flimits\u002Fcaching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent\u002FMCP\u002Ftool-definition\u002Fmulti-agent\u002FRAG\u002FLLM-judge\u002Fcomputer-use; generate\u002Fsummarize\u002Fextract\u002Fclassify\u002Frewrite\u002Fconverse over NL; debugging refusals\u002Fcutoffs\u002Fstreaming\u002Ftool-calls\u002Ftokens).\nSKIP only when another provider is being worked on (overrides all triggers): OpenAI\u002FGPT\u002FGemini\u002FLlama\u002FMistral\u002FCohere\u002FOllama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1647,1650,1651,1654,1656],{"name":1648,"slug":1649,"type":16},"Agents","agents",{"name":9,"slug":8,"type":16},{"name":1652,"slug":1653,"type":16},"Anthropic SDK","anthropic-sdk",{"name":1655,"slug":1642,"type":16},"Claude API",{"name":1657,"slug":1658,"type":16},"LLM","llm","2026-07-28T05:36:08.213335",{"slug":1661,"name":1661,"fn":1662,"description":1663,"org":1664,"tags":1665,"stars":1614,"repoUrl":1615,"updatedAt":1670},"doc-coauthoring","co-author documentation and technical specs","Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1666,1667],{"name":1541,"slug":1542,"type":16},{"name":1668,"slug":1669,"type":16},"Technical Writing","technical-writing","2026-04-06T17:56:14.18897",{"slug":1672,"name":1672,"fn":1673,"description":1674,"org":1675,"tags":1676,"stars":1614,"repoUrl":1615,"updatedAt":1691},"docx","create and edit Word documents","Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1677,1680,1682,1685,1688],{"name":1678,"slug":1679,"type":16},"Documents","documents",{"name":1681,"slug":1672,"type":16},"DOCX",{"name":1683,"slug":1684,"type":16},"Office","office",{"name":1686,"slug":1687,"type":16},"Templates","templates",{"name":1689,"slug":1690,"type":16},"Word","word","2026-07-18T05:16:23.136271",{"slug":1693,"name":1693,"fn":1694,"description":1695,"org":1696,"tags":1697,"stars":1614,"repoUrl":1615,"updatedAt":1711},"frontend-design","design production-grade frontend interfaces","Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1698,1699,1702,1705,1708],{"name":1491,"slug":1492,"type":16},{"name":1700,"slug":1701,"type":16},"Frontend","frontend",{"name":1703,"slug":1704,"type":16},"React","react",{"name":1706,"slug":1707,"type":16},"Tailwind CSS","tailwind-css",{"name":1709,"slug":1710,"type":16},"UI Components","ui-components","2026-04-06T17:56:16.723469",{"slug":1713,"name":1713,"fn":1714,"description":1715,"org":1716,"tags":1717,"stars":1614,"repoUrl":1615,"updatedAt":1721},"internal-comms","write internal company communications","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1718,1719,1720],{"name":21,"slug":22,"type":16},{"name":1686,"slug":1687,"type":16},{"name":1579,"slug":1580,"type":16},"2026-04-06T17:56:20.695522",{"slug":1723,"name":1723,"fn":1724,"description":1725,"org":1726,"tags":1727,"stars":1614,"repoUrl":1615,"updatedAt":1736},"mcp-builder","build MCP servers","Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node\u002FTypeScript (MCP SDK).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1728,1729,1732,1733],{"name":1648,"slug":1649,"type":16},{"name":1730,"slug":1731,"type":16},"API Development","api-development",{"name":1657,"slug":1658,"type":16},{"name":1734,"slug":1735,"type":16},"MCP","mcp","2026-04-06T17:56:10.357665",{"slug":1639,"name":1639,"fn":1738,"description":1739,"org":1740,"tags":1741,"stars":1614,"repoUrl":1615,"updatedAt":1744},"read edit and manipulate PDF files","Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text\u002Ftables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting\u002Fdecrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1742,1743],{"name":1678,"slug":1679,"type":16},{"name":1638,"slug":1639,"type":16},"2026-04-06T17:56:02.483316",{"slug":1746,"name":1746,"fn":1747,"description":1748,"org":1749,"tags":1750,"stars":1614,"repoUrl":1615,"updatedAt":1757},"pptx","create and edit PowerPoint presentations","Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1751,1754],{"name":1752,"slug":1753,"type":16},"PowerPoint","powerpoint",{"name":1755,"slug":1756,"type":16},"Presentations","presentations","2026-07-18T05:16:24.1471",{"slug":1759,"name":1759,"fn":1760,"description":1761,"org":1762,"tags":1763,"stars":1614,"repoUrl":1615,"updatedAt":1773},"skill-creator","create and optimize agent skills","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1764,1765,1766,1769,1772],{"name":1648,"slug":1649,"type":16},{"name":1541,"slug":1542,"type":16},{"name":1767,"slug":1768,"type":16},"Evals","evals",{"name":1770,"slug":1771,"type":16},"Performance","performance",{"name":1668,"slug":1669,"type":16},"2026-04-19T06:45:40.804",490]