What it does
Given the current known facts about an incident, what's affected, when it started, current status, writes a short, calm, factual status update in the right format for the incident's stage, investigating, identified, monitoring, or resolved. Keeps each update consistent with prior updates on the same incident so the timeline reads coherently to someone checking back later.
Install
This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:
Use it in your AI assistant
Claude Code
.claude/skills/status-page-updater/ (or ~/.claude/skills/status-page-updater/ for all projects)
GitHub Copilot (VS Code)
.github/skills/status-page-updater/
OpenAI Codex
.codex/skills/status-page-updater/
Cursor
.cursor/skills/status-page-updater/ (or ~/.cursor/skills/status-page-updater/ globally)
Compatibility
Any WordPress site with a status page, whether a dedicated plugin, hosted status page tool, or a simple page used for updates; no analytics integration needed.
The complete SKILL.md for this skill:
---
name: status-page-updater
description: Use when a user needs an incident update drafted for a public status page during an outage, or asks to "post a status update" or "write an incident update".
---
# Status Page Updater
## When to use
An incident is in progress or just resolved and the user needs a short, factual public status page update that matches the incident's current stage.
## Procedure
1. Confirm the incident stage, investigating, identified, monitoring, or resolved, and only draft an update matching that stage.
2. State plainly what is affected and since when, using only confirmed facts, not speculation about cause.
3. Match tone and format to the site's prior incident updates so the timeline reads as one consistent thread.
4. For a resolved update, state what was fixed and, if known, a brief root cause in plain terms.
5. Keep each update short, a few sentences, since status pages are read quickly and during stress.
## Guardrails
- Never state a cause or fix is confirmed unless the human has actually confirmed it, write that investigation is ongoing instead.
- Don't promise a specific resolution time unless engineering has actually given one.