incident-public-statement
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.
npx skills add mohitagw15856/pm-claude-skills --skill incident-public-statement --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.
# 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`](../pr-crisis-response/SKILL.md).) ## 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 passwo
- Working from a brief
- Required Inputs
- Output Format
- Public Statement: [incident]
- Quality Checks
- Anti-Patterns
- Based On
What does the incident-public-statement skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill incident-public-statement --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 mohitagw15856/pm-claude-skills, a repository with 1,255 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.