Status page & incident communication by openstatus

Write professional incident updates, blameless postmortems, maintenance announcements, and status reports for your status page. Includes real-world examples...

Security Scan

This is an instruction-only skill that drafts incident updates, postmortems, maintenance announcements, and status reports; its files, prompts, and requirements are consistent with that purpose and request no unusual permissions or installs.

Purpose & Capability

Name, description, and included SKILL.md files all describe producing status-page content and postmortems. The skill declares no binaries, no env vars, and no installs — appropriate for a text-generation / template skill.

Instruction Scope

Runtime instructions are limited to asking the user for incident details, using templates, and (optionally) reading a local context file at .agents/status-page-context.md. The skill explicitly avoids inventing details and instructs placeholders for unknowns. It does not direct the agent to read unrelated system files, exfiltrate data, or call external endpoints.

Install Mechanism

No install spec or code files are present — instruction-only. This minimizes disk writes and arbitrary code execution risk.

Credentials

The skill requests no environment variables, credentials, or config paths beyond an optional local context file (.agents/status-page-context.md). That matches the described function (tone, component names, SLAs).

Persistence & Privilege

Flags: always=false and default autonomous invocation are present (normal). The skill does not request persistent privileges, modify other skills, or claim system-level access.

Assessment

This skill appears coherent and low-risk because it's just text templates and instructions. Before using it, avoid pasting secrets or full internal logs into prompts (the skill will use any text you provide). Review any draft updates before publishing externally. If you wire an automated publisher (a separate skill or script) to post updates to your actual status page, restrict that publisher's credentials and review automation carefully — this skill itself does not include publishing code. Finally, if you want a higher assurance review, provide the .agents/status-page-context.md content and any automation hooks so you can confirm nothing else will read or transmit sensitive data.

OpenStatus Skills

Status page & incident communication skills for AI agents — by OpenStatus.

Skills

Skill	What it does
status-page-context	Configure your product, components, SLAs, severity levels, and communication tone. All other skills read this automatically.
incident-communication	Write status page updates for any incident phase: investigating, identified, monitoring, resolved.
postmortem	Write blameless postmortems with timeline, root cause analysis (5 Whys), and prioritized action items.
maintenance	Write maintenance announcements: scheduled, in-progress, completed, extended, or cancelled.
status-report	Write periodic health reports (weekly, monthly, quarterly) with uptime metrics, SLA tracking, and trends.

How They Work Together

status-page-context     ← run this first (defines tone, components, SLAs)
  │
  ├── incident-communication   ← during an outage
  │     investigating → identified → monitoring → resolved
  │                                                  │
  │                                                  └── postmortem   ← after resolution
  │
  ├── maintenance              ← for planned work
  │     scheduled → in-progress → completed
  │
  └── status-report            ← periodic health updates
        weekly / monthly / quarterly

Each skill checks for .agents/status-page-context.md and uses your defined tone, component names, and severity levels. Without it, skills still work — they'll just prompt you for the details.

What's Inside Each Skill

Every skill includes:

• SKILL.md — full instructions, principles, templates, and anti-patterns
• references/examples.md — real-world good and bad examples from Vercel, Stripe, GitHub, and Cloudflare
• references/framework.md — checklists and quality tests to verify output
• evals/evals.json — evaluation scenarios for testing skill behavior

Who This Is For

• On-call engineers — write clear incident updates under pressure without starting from a blank page
• SREs / DevOps — produce consistent postmortems and reliability reports
• Engineering managers — publish regular status reports to stakeholders
• Anyone with a status page — communicate maintenance, outages, and health to users