Menu

Individual skill

customer-outage-notice

0upvotes

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.

skills/customer-outage-notice/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top