stakeholder-update
Stakeholder communication assistant for status updates, progress reports, and executive summaries. Use when the user needs to write a stakeholder update, status report, progress summary, or any upward communication. Triggers include "stakeholder update", "status update", "progress report", "update leadership", "weekly update", or "executive summary".
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill stakeholder-update --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Stakeholder Update Skill ## Instructions Help create clear, concise stakeholder updates that communicate progress, risks, and asks effectively. ### Behavior 1. **Lead with the headline** — Don't bury the lead 2. **Use consistent structure** — Same format builds trust 3. **Be honest about risks** — Surface problems early 4. **Include clear asks** — What do you need from them? 5. **Keep it scannable** — Executives skim ### Tone - Confident but not arrogant - Transparent about challenges - Action-oriented - Respectful of reader's time ### Advanced Patterns 1. **The bad news sandwich is dead** — Don't bury risks between good news. Executives see through it and lose trust. Instead, lead with the headline (good or bad), then immediately follow with what you're doing about it. "Android delivery dropped to 88%. Root cause identified, fix deploying Monday, ETA to recover: 2 weeks." Confidence comes from having a plan, not from hiding problems 2. **Metric trend > metric snapshot** — A single number is noise. Three data points are a trend. Always show the direction: "Delivery rate: 94% (up from 89% last month, target 95%)." The reader can instantly assess: are we improving, stable, or decli
- Instructions
- Behavior
- Tone
- Advanced Patterns
- Update Structure
- Principles
- Headline First
- Specific Over Vague
- Honest About Problems
- Clear Asks
- Examples
- Example 1: Weekly Update
- Push Notifications Update — Week of Feb 10, 2026
- TL;DR
What does the stakeholder-update skill do?
Stakeholder communication assistant for status updates, progress reports, and executive summaries. Use when the user needs to write a stakeholder update, status report, progress summary, or any upward communication. Triggers include "stakeholder update", "status update", "progress report", "update leadership", "weekly update", or "executive summary".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill stakeholder-update --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.