$ loading_
Create stakeholder updates tailored to audience, cadence, and communication goals.
This skill appears to be a prompt-only, open-source writing aid with no required secrets and no declared remote endpoints or local execution capability, so overall risk is low. The README mentions pulling context from connected tools, but based on the provided material alone, there are no concrete red flags of built-in network exfiltration, code execution, or excessive data access.
The material explicitly states that no keys or environment variables are required; as a prompt-only skill, it does not appear to request or handle credentials, so credential exposure or abuse risk is low.
No remote endpoints are declared, and the system marks it as prompt-only. Although the README mentions pulling context from 'connected tools,' that describes workflow when external connectors exist, not network egress behavior inherently declared by this skill itself.
The material does not indicate spawning local processes, running scripts, invoking a shell, or using system capabilities; from the current description, it mainly generates stakeholder update text for different audiences.
The skill itself does not declare read/write access to files, databases, or other resources. The README only suggests using project, chat, meeting, or knowledge-base context when external tools are already connected; viewed on its own, there is no sign of excessive access.
The source is an open-source GitHub repository, which is a clear positive for auditability and lowers risk; however, the license is unspecified, community adoption is 0 stars, and maintenance status is unknown, so supply-chain trust is decent but still warrants attention to repository activity and governance.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "stakeholder-update" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/product-management/skills/stakeholder-update/SKILL.md 2. Save it as ~/.claude/skills/stakeholder-update/SKILL.md 3. Reload skills and tell me it's ready
Write a weekly project update for leadership in a concise executive tone. Include completed work, current risks, next week's plan, and decisions needing support. The project is a mobile payment redesign, and the audience is the company leadership team.
A leadership-friendly weekly update highlighting outcomes, risks, and required decisions.
Generate a product launch announcement for internal cross-functional stakeholders. Explain what is launching, the user value, release timing, affected teams, and the post-launch monitoring plan. Use a professional and clear tone.
A clear launch announcement that helps teams understand the change and required coordination.
Turn the following project blocker into a risk escalation update for executives and engineering leaders. Include background, current impact, actions already taken, why it remains unresolved, recommended next steps, and support needed. Keep the tone objective and direct.
A formal escalation update clearly explaining impact, mitigation progress, and support requests.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate a stakeholder update tailored to the audience and cadence.
/stakeholder-update $ARGUMENTS
Ask the user what kind of update:
Ask who the update is for:
If ~~project tracker is connected:
If ~~chat is connected:
If ~~meeting transcription is connected:
If ~~knowledge base is connected:
If no tools are connected, ask the user to provide:
Structure the update for the target audience using the templates and frameworks below.
For executives: TL;DR, status color (G/Y/R), key progress tied to goals, decisions made, risks with mitigation, specific asks, and next milestones. Keep it under 300 words.
For engineering: What shipped (with links), what is in progress (with owners), blockers, decisions needed (with options and recommendation), and what is coming next.
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.
For customers: What is new (framed as benefits), what is coming soon, known issues with workarounds, and how to provide feedback. No internal jargon.
For launch announcements: What launched, why it matters, key details (scope, availability, limitations), success metrics, rollout plan, and feedback channels.
After generating the update:
Executives want: strategic context, progress against goals, risks that need their help, decisions that need their input.
Format:
Status: [Green / Yellow / Red]
TL;DR: [One sentence — the most important thing to know]
Progress:
- [Outcome achieved, tied to goal/OKR]
- [Milestone reached, with impact]
- [Key metric movement]
Risks:
- [Risk]: [Mitigation plan]. [Ask if needed].
Decisions needed:
- [Decision]: [Options with recommendation]. Need by [date].
Next milestones:
- [Milestone] — [Date]
Tips for executive updates:
…
Review an analysis for methodology, accuracy, bias, and evidence support.
Generate people analytics reports on headcount, attrition, diversity, and org health.
Identify, categorize, and prioritize technical debt for smarter refactoring decisions.
Choose the right Zoom surface for a product use case with clear tradeoffs.
Turn an approved brief into social assets, copy, and a staged campaign.
Research contacts with Common Room data to assess background and lead warmth.
Generate clear project status reports with KPIs, risks, and action items.
Format project updates into clear stakeholder-ready status reports.
Generate clear daily standup updates from recent commits, PRs, and ticket changes.
Publish stakeholder report entries for consistent reporting and collaboration.
Generate daily or weekly cross-source digests of mentions, action items, and updates.
Generate personalized outreach emails and messages using Common Room signals.