What do I need to use Incident Public Statement?

What happened; Who's affected and how; What you're doing; What affected people should do; Voice & constraints.

Is Incident Public Statement free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Incident Public Statement

Q: How do I know the Incident Public Statement output is good?

The skill verifies itself against its own quality checks: The first sentence acknowledges the issue directly — no warm-up, no burying; Only confirmed facts are stated; open items are named as "under investigation"; It takes responsibility without speculating on cause or shifting blame; Affected people get a clear, specific action (or an honest "no action needed").

🔵 Stable🕐 updated 2026-06-29 🔷 SkillSpec L3 pm-crisis

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.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸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.

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓The first sentence acknowledges the issue directly — no warm-up, no burying

✓Only confirmed facts are stated; open items are named as "under investigation"

✓It takes responsibility without speculating on cause or shifting blame

✓Affected people get a clear, specific action (or an honest "no action needed")

✓It commits to a next update by a stated time

✓Both a full and a short version are provided; sensitive claims flagged for review

⚠️ What it refuses to do

Do not open with self-congratulation or context-setting — lead with the acknowledgement

Do not use evasive legalese ("issues may have impacted some users") when you can be specific

Do not speculate on cause or promise outcomes you can't guarantee

Do not state numbers/scope you haven't confirmed — bracket them for confirmation

Do not omit what the reader should actually do next

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="incident-public-statement"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Incident Public Statement is one of 599 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog