stakeholder-comms
Deep workflow for stakeholder communication—audience mapping, narrative structure, status with honesty, trade-off framing, asks, and follow-ups. Use when writing exec updates, cross-team notes, project summaries, or managing expectations under uncertainty.
Why use this skill?
Master stakeholder communication with OpenClaw. Streamline executive updates, project reports, and dependency negotiations with a structured, professional workflow.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/codekungfu/stakeholder-commsWhat This Skill Does
The stakeholder-comms skill provides a structured, high-leverage framework for crafting professional correspondence and documentation. It is designed to move communication away from vague updates toward clarity, accountability, and actionable outcomes. The skill guides you through five essential stages: audience analysis, narrative construction, risk and trade-off assessment, explicit ask formulation, and follow-up cadence. By following this workflow, you ensure that your messages reduce ambiguity, build trust, and streamline decision-making processes, particularly in high-stakes environments like executive steering committees or crisis management.
Installation
To integrate this skill into your OpenClaw environment, execute the following command in your terminal:
clawhub install openclaw/skills/skills/codekungfu/stakeholder-comms
Use Cases
This skill is ideal for:
- Writing weekly project status reports for executives.
- Negotiating complex cross-team dependencies where alignment is slipping.
- Communicating project delays or incidents with honesty and mitigation plans.
- Pitching technical initiatives where you need to frame trade-offs against business goals (e.g., tech debt vs. feature velocity).
- Requesting budget, headcount, or architectural decisions.
Example Prompts
- "I need to tell our VP of Product that we are missing our launch date for the API update by two weeks due to a database migration issue. Please use the stakeholder-comms workflow to draft a message that focuses on the delay, the new recovery plan, and what I need from them."
- "Help me structure an email for a steering committee meeting. I have two competing options for our cloud migration strategy. Frame these as a trade-off analysis so the committee can easily choose between speed and long-term cost efficiency."
- "Refine this project update. I feel like it's too defensive. Use the stakeholder-comms methodology to make it more objective, clear about the risks, and explicit about the action items for the stakeholders."
Tips & Limitations
- Be specific: The skill thrives on evidence. Avoid generalities like 'we are working hard' and replace them with 'we are deploying X fix by Tuesday.'
- Don't over-document: Match your output detail to the stakeholder's role. Executives generally require high-level, bottom-line-up-front (BLUF) summaries.
- Date the unknown: If a risk is high, don't ignore it. Use the 'date the unknown' technique to tell stakeholders exactly when you will have a resolution.
- Limitations: This skill focuses on the structure and strategy of communication. It does not replace subject matter expertise; you must provide the raw facts for the agent to synthesize effectively.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-codekungfu-stakeholder-comms": {
"enabled": true,
"auto_update": true
}
}
}