免费在 GitHub 公开

incident-slo-runbook

Create or audit SLOs, SLIs, alert rules, incident response steps, escalation paths, postmortems, operational runbooks, and customer-impact communication. Use when defining production reliability, preparing launch readiness, responding to an outage, writing a runbook, tuning alerts, or closing the loop after an incident.

中文简介正在准备中。当前显示原文说明。

majiayu000/spellbook

实测评分未实测

查看安装方法

包含的文件（2）

SKILL.md1.8 KB
agents/openai.yaml230 B

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Incident SLO Runbook

Purpose

Use this skill to connect observability to action. Metrics and logs are not enough; each critical user journey needs an SLO, alert, owner, response path, and post-incident learning loop.

SLO Design

Define:

User journey or system capability.
SLI: request success, latency, freshness, durability, or job completion.
SLO target and measurement window.
Error budget and burn-rate alerts.
Exclusions with rationale.
Dashboard and data source.
Owner and escalation path.

Avoid vanity metrics. Prefer user-visible success and latency over internal counters unless internal counters are the only reliable proxy.

Runbook Requirements

Each runbook should include:

Symptom and alert name.
Impacted users or systems.
First 5-minute checks.
Triage decision tree.
Mitigation steps with commands.
Rollback or failover path.
Escalation owner.
Customer/support communication note.
Postmortem trigger.

Commands must be safe to run or explicitly labeled destructive.

Incident Flow

Declare severity and incident commander.
Confirm impact from live evidence.
Stabilize with the lowest-risk mitigation.
Communicate status on a fixed cadence.
Preserve evidence before cleanup.
Write a blameless postmortem with action items and owners.

Output Shape

service_or_journey:
slo:
alerts:
dashboard_or_queries:
runbook:
escalation:
postmortem_template:
verification:

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

agentsmd-optimize

免费

Audit and organize AI coding-agent instructions, including AGENTS.md, CLAUDE.md, skills, and agent definitions. Use when the user asks to diagnose conflicting instructions, excessive approval pauses, broad skill triggers, duplicate guidance, or broken instruction references, or to clean up that instruction set. Ordinary code review, Markdown editing, or application debugging alone does not trigger this workflow. Inspection stays read-only; apply changes when authorized.

中文简介正在准备中。当前显示原文说明。