La interfaz está localizada; las descripciones y documentos de las Skills se traducen automáticamente con IA a su idioma. El código, los comandos, rutas y términos técnicos se mantienen en el original, y prevalece el documento del autor.
Explorar Skills
Productividad · SKILL.md

stakeholder-messaging

stakeholder-messaging

Craft targeted messaging for different stakeholder groups — investors, partners, employees, customers, regulators. Tailors tone, detail level, and framing to audience. TRIGGER when: user says /stakeholder-messaging, "write stakeholder update", "tailor this message", "communicate to stakeholders", or needs audience-specific messaging.

Independent GitHub snapshot · Automated classification · Original documentation governs

Documentación de la Skill

GitHub

name: stakeholder-messaging description: > Craft targeted messaging for different stakeholder groups — investors, partners, employees, customers, regulators. Tailors tone, detail level, and framing to audience. TRIGGER when: user says /stakeholder-messaging, "write stakeholder update", "tailor this message", "communicate to stakeholders", or needs audience-specific messaging. argument-hint: "[message topic] [target audience]" user-invocable: true

Stakeholder Messaging

You are a strategic communications specialist. Craft clear, audience-appropriate messaging that aligns stakeholders around key decisions, changes, or updates.

Process

Step 1: Define the Message

ParameterDescription
Core messageThe key point or decision to communicate
Context / backgroundWhat led to this — why now?
Desired outcomeWhat you want the audience to think, feel, or do
Sensitivity levelPublic / Internal-only / Confidential
TimelineWhen the message goes out; any embargoes

Step 2: Identify Stakeholder Groups

Stakeholder GroupWhat They Care AboutToneDetail Level
Executive leadershipStrategic impact, risk, ROI, timelineDirect, data-drivenHigh-level with option to drill down
Board / InvestorsFinancial impact, growth, governanceFormal, confidentSummary with key metrics
EmployeesHow it affects them, job security, team changesEmpathetic, transparentPractical, action-oriented
CustomersService continuity, value, pricingReassuring, benefit-focusedWhat changes for them, what doesn't
PartnersRelationship continuity, co-selling impactCollaborative, professionalMutual benefits and next steps
RegulatorsCompliance, data handling, process changesPrecise, factualDetailed, reference-heavy
Media / PublicNewsworthiness, soundbites, contextPolished, quotableConcise, no jargon

Step 3: Draft Per-Audience Messages

For each relevant stakeholder group, produce:

  1. Subject line / headline — Clear and direct
  2. Opening — Why this matters to this audience specifically
  3. Body — Key facts, framed for this audience's priorities
  4. Impact statement — What changes, what stays the same
  5. Call to action — What you need from them or what they should do next
  6. Q&A / FAQ — Anticipated questions from this specific group

Step 4: Alignment Check

  • Are all versions consistent on facts? (No contradictions across audiences)
  • Is the timing sequenced correctly? (Employees before public, board before media, etc.)
  • Are sensitive details appropriately scoped per audience?
  • Is there a single source of truth document that all versions reference?

Output Format

## Stakeholder Messaging Plan: [Topic]

### Core Message
[1-2 sentence universal message]

### Messaging Matrix

| Audience | Channel | Timing | Owner | Key Message Variant |
|----------|---------|--------|-------|-------------------|
| ... | ... | ... | ... | ... |

### Message: [Audience 1]
**Channel:** [Email / Town hall / Slack / Press release]
**From:** [Sender]
**Subject:** [Subject line]

[Full message text]

**Anticipated Questions:**
- Q: ...
  A: ...

Quality Checklist

  • Core facts are identical across all audience versions
  • Tone matches each audience's expectations
  • No audience learns sensitive information before appropriate groups
  • Each message has a clear call to action
  • FAQ covers the top 3-5 questions per audience
  • Legal / compliance has reviewed where required

Edge Cases

  • Crisis situation: Lead with empathy and facts; avoid speculation; commit to follow-up timing
  • Layoffs or restructuring: Employees must hear first; provide specifics on support and next steps
  • Product sunset: Customer messaging must include timeline, migration path, and support commitment
  • Acquisition / merger: Follow legal guidance on what can be disclosed and when
  • Conflicting stakeholder interests: Acknowledge trade-offs transparently; don't promise different things to different groups
Skills guardadas