stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on stakeholder update, status report, executive summary, exec review, manage up, communicate bad news, project comms, status meeting, weekly update. Also triggers when a project is going off track and the team needs to communicate it.
Profile →npx skills add rampstackco/claude-skills --skill stakeholder-communication --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 Communication Get the right information to the right people at the right time, in a form they can act on. Stack-agnostic. Applies to any team operating with cross-functional stakeholders. --- ## When to use - Writing weekly or monthly status updates - Preparing for an executive review or board update - Sharing a technical decision with a non-technical audience - Communicating a delay, miss, or quality problem - Asking for help, resources, or decisions - Managing up to a manager or sponsor - Designing the communication cadence for a project - Drafting an internal announcement ## When NOT to use - Customer-facing communication (use marketing/support skills) - Public comms or press (different framework, different stakes) - Incident communication during an active incident (use `incident-response`) - Internal documentation that isn't time-sensitive (use `documentation-strategy`) - Specific delivery formats (slide deck design, email tone) - this skill is about content and structure --- ## Required inputs - The audience (who specifically, what's their context, what do they care about) - The purpose (inform, decide, escalate, ask, celebrate) - The substance (what's actually h
- When to use
- When NOT to use
- Required inputs
- The framework: 5 questions
- Question 1: Who is the audience?
- Question 2: What's the headline?
- Question 3: What's the so-what?
- Question 4: What do you want?
- Question 5: What format?
- The structure: the inverted pyramid
- Update templates
- Weekly project update
- Executive review
- Bad news
What does the stakeholder-communication skill do?
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on stakeholder update, status report, executive summary, exec review, manage up, communicate bad news, project comms, status meeting, weekly update. Also triggers when a project is going off track and the team needs to communicate it.
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill stakeholder-communication --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 rampstackco/claude-skills, a repository with 515 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.