Incident Public Statement Skill
A public statement is judged in seconds: does it acknowledge the problem, take responsibility, and tell people
what to do? This skill writes that statement — honest, human, and specific — avoiding both the legalese that
reads as evasion and the over-promising that creates the next problem. (Need the whole coordinated response,
not just the statement? Use pr-crisis-response.)
Working from a brief
Given a one-line incident description, produce the full statement anyway — infer the likely impact and next
steps, label assumptions, and clearly bracket only the genuinely incident-specific facts the user must confirm
before publishing (numbers, dates, scope). Never refuse for missing detail; flag legally sensitive claims for review.
Required Inputs
Ask for these only if they aren't already provided (else infer and label):
- What happened — the incident, when it started/was discovered, and current status.
- Who's affected and how — scope and the concrete impact on them.
- What you're doing — the response so far and what's next.
- What affected people should do — the specific action (reset password, watch for X, no action needed).
- Voice & constraints — tone, and anything legal/regulatory you can't yet say.
Output Format
Public Statement: [incident]
Statement (publish-ready) — in this order:
- Acknowledge — name the issue plainly in the first sentence; don't bury it.
- What happened — a brief, factual account (confirmed only); say what's still being investigated.
- Impact — who/what is affected, specifically and honestly.
- What we're doing — the actions taken and underway, with accountability (no blame-shifting).
- What you should do — the clear next step for affected people, or "no action needed" if true.
- Our commitment — that you'll share an update by a stated time, and how to get help/contact.
Then provide:
- Short version — 2–3 sentences for social / status page / SMS.
- Notes — bracketed facts to confirm before publishing, and any line flagged for legal review.
Quality Checks
Anti-Patterns
Based On
Incident communication practice — prompt acknowledgement, factual transparency, accountability, and clear guidance for affected people.
Example Trigger Phrases
- "Draft a public statement."
- "Write a press statement about the breach."
- "Write our official response to the outage."
- "Respond publicly to this controversy."
1---2name: incident-public-statement3description: "Write a single clear, honest public statement about an incident. Use when asked to draft a public statement, a press statement, or an official response to a security breach, outage, data incident, recall, or public controversy. Produces a ready-to-publish statement — acknowledgement, what happened, impact, what you're doing, what affected people should do, and a commitment to update — plus a short and a long version."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/incident-public-statement7---89# Incident Public Statement Skill1011A public statement is judged in seconds: does it acknowledge the problem, take responsibility, and tell people12what to do? This skill writes that statement — honest, human, and specific — avoiding both the legalese that13reads as evasion and the over-promising that creates the next problem. (Need the whole coordinated response,14not just the statement? Use [`pr-crisis-response`](../pr-crisis-response/SKILL.md).)1516## Working from a brief1718Given a one-line incident description, **produce the full statement anyway** — infer the likely impact and next19steps, label assumptions, and clearly bracket only the genuinely incident-specific facts the user must confirm20before publishing (numbers, dates, scope). Never refuse for missing detail; flag legally sensitive claims for review.2122## Required Inputs2324Ask for these only if they aren't already provided (else infer and label):2526- **What happened** — the incident, when it started/was discovered, and current status.27- **Who's affected and how** — scope and the concrete impact on them.28- **What you're doing** — the response so far and what's next.29- **What affected people should do** — the specific action (reset password, watch for X, no action needed).30- **Voice & constraints** — tone, and anything legal/regulatory you can't yet say.3132## Output Format3334### Public Statement: [incident]3536**Statement (publish-ready)** — in this order:371. **Acknowledge** — name the issue plainly in the first sentence; don't bury it.382. **What happened** — a brief, factual account (confirmed only); say what's still being investigated.393. **Impact** — who/what is affected, specifically and honestly.404. **What we're doing** — the actions taken and underway, with accountability (no blame-shifting).415. **What you should do** — the clear next step for affected people, or "no action needed" if true.426. **Our commitment** — that you'll share an update by a stated time, and how to get help/contact.4344Then provide:45- **Short version** — 2–3 sentences for social / status page / SMS.46- **Notes** — bracketed facts to confirm before publishing, and any line flagged for legal review.4748## Quality Checks4950- [ ] The first sentence acknowledges the issue directly — no warm-up, no burying51- [ ] Only confirmed facts are stated; open items are named as "under investigation"52- [ ] It takes responsibility without speculating on cause or shifting blame53- [ ] Affected people get a clear, specific action (or an honest "no action needed")54- [ ] It commits to a next update by a stated time55- [ ] Both a full and a short version are provided; sensitive claims flagged for review5657## Anti-Patterns5859- [ ] Do not open with self-congratulation or context-setting — lead with the acknowledgement60- [ ] Do not use evasive legalese ("issues may have impacted some users") when you can be specific61- [ ] Do not speculate on cause or promise outcomes you can't guarantee62- [ ] Do not state numbers/scope you haven't confirmed — bracket them for confirmation63- [ ] Do not omit what the reader should actually do next6465## Based On6667Incident communication practice — prompt acknowledgement, factual transparency, accountability, and clear guidance for affected people.6869## Example Trigger Phrases7071- "Draft a public statement."72- "Write a press statement about the breach."73- "Write our official response to the outage."74- "Respond publicly to this controversy."