PlaygroundCatalog › Customer Incident Update
CI

Customer Incident Update

🔵 Stable 🔷 SkillSpec L3 pm-crisis

Write the customer-facing incident update during an outage — status-page post or email — that's honest about impact without over-promising. Use when asked to write a status page update, draft customer comms for an outage, post an incident notice, or tell customers about downtime. Produces the update in the right tense for the incident stage (investigating / identified / monitoring / resolved), with impact scope, any workaround, and a concrete next-update time. Distinct from incident-postmortem (the internal retro).

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

🗣 Say this to your agent

“Write a status page update — we're investigating an outage.”“Draft customer comms for the API downtime, identified stage.”“Post an incident notice for enterprise accounts.”“We've deployed a fix and are monitoring — write the update.”

What to give it

Stage — investigating, identified, monitoring, or resolved
Impact — which product/region/customers, and what they can't do right now
What's known — only what you're confident of; unknowns stay unknown in the post
Workaround — any, or none
Audience — all customers, affected only, or enterprise accounts (tone shifts)

✅ 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 tense matches the actual stage — no claiming a fix that isn't confirmed
Impact is stated in customer terms, up top
A specific next-update time is given
No cause is speculated when it isn't known
No fix-by time is promised that depends on an unknown
Tone is human and brief — one apology, no jargon

⚠️ What it refuses to do

**"Some users may be experiencing issues"** when it's a full outage — minimising erodes trust faster than the outage.
**Promising a resolution time** you can't control.
**Publishing a guessed cause** that turns out wrong.
**No next-update time** — leaves customers refreshing in the dark.
**Skipping stages** — jumping to "resolved" before monitoring confirms it.

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="customer-incident-update"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

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