eng-runbook

Solid

服务概述 + alerts 表 + dashboards + 操作命令 + on-call + 事故清单

Web & Frontend 5,466 stars 543 forks Updated 2 days ago Apache-2.0

Install

View on GitHub

Quality Score: 95/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
13
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

【模板: Engineering Runbook】 【意图】工程 oncall 用的可拷贝命令的 runbook 单页。 【布局】 - Service overview (拓扑 + 依赖) - Alerts table (severity / threshold / runbook link) - Dashboards links 卡片 - Common procedures (mono 代码块, 一键复制) - On-call rotation (本周 + 下周) - Incident response checklist

Details

Author
nexu-io
Repository
nexu-io/html-anything
Created
2 weeks ago
Last Updated
2 days ago
Language
HTML
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

runbook-generator

Runbook Generator

16,642 Updated yesterday
alirezarezvani
API & Backend Listed

runbook-author

Given an alert definition (or a postmortem), produce a runbook entry — symptom, first 5 actions, escalation

1 Updated 4 days ago
bakw00ds
DevOps & Infrastructure Listed

devops-runbooks

Operational runbook and procedure documentation specialist. Use when creating incident response procedures, operational playbooks, or system maintenance guides.

335 Updated today
aiskillstore
AI & Automation Listed

runbook-generator

Guidance for generating OpenStack runbooks with dual task/symptom indexing following NASA procedure standards. Use when creating incident response procedures, operational runbooks, or troubleshooting guides that must be verified against running infrastructure.

62 Updated today
Tibsfox
Code & Development Solid

runbook

Create or update a runbook for an operational scenario — an incident an alert fires for, a recurring scheduled task, or a known failure mode on a live service — using a consistent template. Use when writing, drafting, authoring, or updating a runbook for an alert, incident, on-call procedure, scheduled maintenance, or operational SOP. Each invocation produces one runbook at a time. Applies a YAGNI preflight that requires the scenario to be real (an alert that has fired, a recurring task that exists, or a live failure mode on a service that receives traffic) before producing the runbook. Does not produce feature or system documentation — use project-documentation. Does not record architectural decisions — use architectural-decision-record. Does not create coding standards — use coding-standard.

66 Updated today
testdouble