Menu

Individual skill

status-page

Build and maintain status pages — incident communication, uptime transparency, and subscriber notifications.

skills/status-page/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 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)
53
Repository last updated
Oct 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

## Overview

A status page is the single source of truth during incidents and the proof of reliability the rest of the time: system status, incident history, uptime metrics, and maintenance schedules. This skill covers status page strategy, incident communication, transparency practices, and subscriber management.


A status page is your trust infrastructure during incidents: the single source of truth customers check instead of flooding support. Companies with excellent status pages turn outages from trust-destroying events into trust-building ones through fast, honest, human communication. It is also proactive transparency — historical uptime data that sells reliability before sales calls happen.
## When to use

- Setting up a status page
- Writing incident updates
- Deciding what to show publicly
- Building uptime transparency
- Managing maintenance communications
- Reducing "is it down?" support tickets