← Back to Skills Marketplace
🔌
Status page & incident communication by openstatus
by
openstatus
· GitHub ↗
· v1.0.0
· MIT-0
72
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install incident-communication-playbook
Description
Write professional incident updates, blameless postmortems, maintenance announcements, and status reports for your status page. Includes real-world examples...
README (SKILL.md)
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
Usage Guidance
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.
Capability Tags
Capability Assessment
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.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install incident-communication-playbook - After installation, invoke the skill by name or use
/incident-communication-playbook - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of incident-communication skill.
- Enables writing professional incident updates for any incident phase: investigating, identified, monitoring, resolved.
- Integrates real-world communication examples from Vercel, Stripe, GitHub, and Cloudflare.
- Automatically uses your status page’s tone, components, and SLAs by referencing status-page-context.
- Bundled with templates, principles, anti-patterns, and quality checklists to ensure effective updates.
- Designed for on-call engineers, SREs, DevOps, engineering managers, and anyone responsible for status page communication.
Metadata
Frequently Asked Questions
What is 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... It is an AI Agent Skill for Claude Code / OpenClaw, with 72 downloads so far.
How do I install Status page & incident communication by openstatus?
Run "/install incident-communication-playbook" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Status page & incident communication by openstatus free?
Yes, Status page & incident communication by openstatus is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Status page & incident communication by openstatus support?
Status page & incident communication by openstatus is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Status page & incident communication by openstatus?
It is built and maintained by openstatus (@openstatus); the current version is v1.0.0.
More Skills