Runbook Assistant | Runbook 助手

SkillCloud & infra

Guide runbook creation, maintenance, and drill exercises. Use when: writing runbooks, planning drills, auditing runbook coverage, post-incident runbook updates. Not for: responding to an incident already in progress — use /incident; the deployment procedure itself — use /deploy. Keywords: runbook, operations, drill, on-call, procedure.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Runbook Assistant | Runbook 助手 skill

What this skill tells your AI

The instructions your AI receives, as published by asiaostrich/universal-dev-standards in skills/runbook-assistant/SKILL.md and read by ahel’s review.

Language: English | 繁體中文

Guide runbook writing, maintenance, drill exercises, and coverage reporting.

引導 Runbook 撰寫、維護、演練和覆蓋率報告。

Capabilities | 功能

CapabilityDescription說明
Create RunbookGenerate runbook from standard template (7 sections)從標準範本產生 Runbook
Drill PlanningSchedule and record drill exercises規劃和記錄演練
Coverage ReportCheck runbook coverage for P1-P4 alerts檢查告警的 Runbook 覆蓋率
Quality ReviewVerify runbook quality (6 principles)驗證 Runbook 品質
Staleness CheckIdentify overdue runbook reviews識別過期需審查的 Runbook

Usage | 使用方式

/runbook                              # Show runbook guide
/runbook create "api-latency-high"    # Create runbook for alert
/runbook drill                        # Plan drill exercises
/runbook coverage                     # Generate coverage report

Next Steps Guidance | 下一步引導

Runbook 引導完成。建議下一步:

  • 執行 /observability --alerting 連結告警到 Runbook ⭐ 推薦
  • 執行 /incident --postmortem 從事故更新 Runbook
  • 執行 /checkin 提交變更

Deploy Runbook — Mandatory Rule

Any deploy runbook that includes a destructive-update pattern (stop → swap → start) MUST follow the Defensive Deployment Ordering sequence: extract to staging → verify → only then touch the live install. Skipping the verify step has caused real production outages.

任何包含 destructive-update(stop → swap → start)的部署 runbook 必須遵循 Defensive Deployment Ordering 順序:解壓到 staging → verify → 通過後才動 live install。跳過 verify 步驟已造成真實生產事故。

Reference | 參考

Signals

GitHub stars
73
Forks
13
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
runbook
Source
github.com/asiaostrich/universal-dev-standards