360 Secure SkillHub
360 安全技能中心

Status page & incident communication by openstatus

面向状态页与事故沟通的技能集合：在事件各阶段（调查、定位、监控、恢复）撰写更新，事后产出无责复盘（含时间线与5 Whys根因分析），并支持计划维护公告与周期性健康报告；可读取项目内的状态页上下文文件，统一组件名称、SLA、严重级别与语气。每个技能附带实例与质量检查清单。

分类：协作
openstatus
热度 38.99
最近更新 2026-05-11 17:43:38

安装

发给 Agent
帮我安装这个技能：npx secure-skills-cli add openstatus/incident-communication-playbook
兼容性
通用兼容
联网要求
联网要求未确认
数据出网
数据不出本机
Metadata
name
incident-communication
description
Write professional incident updates, blameless postmortems, maintenance announcements, and status reports for your status page. Includes real-world examples from Vercel, Stripe, GitHub, and Cloudflare. Start with status-page-context to configure your tone, components, and SLAs — all other skills reference it automatically.
version
1.0.0
homepage
https://openstatus.dev
skills
["skills/status-page-context","skills/incident-communication","skills/postmortem","skills/maintenance","skills/status-report"]

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