customer-outage-notice
Write clear customer-facing outage and service-disruption notifications. Use when asked to write an outage notice, a status-page update, a service-disruption email, a maintenance notice, or an incident update sequence. Produces status-page updates for each phase (investigating → identified → monitoring → resolved), a customer email, and a resolved/post-incident summary, in plain, reassuring language.
npx skills add mohitagw15856/pm-claude-skills --skill customer-outage-notice --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.
# Customer Outage Notice Skill During an outage, customers don't need engineering detail — they need to know you're aware, that you're on it, and when you'll update them next. This skill writes the notifications across the whole incident lifecycle, in calm, plain language that reduces support tickets instead of generating them. (For a security/data incident or a PR crisis, use [`incident-public-statement`](../incident-public-statement/SKILL.md) or [`pr-crisis-response`](../pr-crisis-response/SKILL.md).) ## Working from a brief Given "checkout is down for some users", **produce the full set of phased notices anyway** — infer the affected scope and a plausible update cadence, label assumptions, and bracket the specific facts (start time, services, ETA) to fill in. Never wait for full detail; teams paste these live and edit the brackets. ## Required Inputs Ask for these only if they aren't already provided (else infer and label): - **What's affected** — which service/feature, and for whom (all users, a region, a plan). - **Severity** — full outage, partial/degraded, or intermittent. - **Status** — investigating, root cause known, fix deploying, or resolved. - **Timing** — when it star
- Working from a brief
- Required Inputs
- Output Format
- Outage Communications: [service]
- Quality Checks
- Anti-Patterns
- Based On
What does the customer-outage-notice skill do?
Write clear customer-facing outage and service-disruption notifications. Use when asked to write an outage notice, a status-page update, a service-disruption email, a maintenance notice, or an incident update sequence. Produces status-page updates for each phase (investigating → identified → monitoring → resolved), a customer email, and a resolved/post-incident summary, in plain, reassuring language.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill customer-outage-notice --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.