eng-runbook

Generate structured HTML/Markdown engineering runbooks for on-call incidents.

Updated May 2, 2026
One-click install
npx skills add https://github.com/az9713/open-design-tutorial --skill eng-runbook-az9713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-runbook
Source: https://github.com/az9713/open-design-tutorial/tree/main/skills/eng-runbook
Command: npx skills add https://github.com/az9713/open-design-tutorial --skill eng-runbook-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runbooks provide a single, portable reference that guides on-call teams through incident handling, reducing MTTR and ensuring consistent responses across services.

Core Features & Use Cases

  • Service overview, alerts table, dashboards, and on-call rotation to coordinate responses.
  • Common procedures with copy-pasteable commands for deploys, rollbacks, and key rotation.
  • Incident-response checklist and post-incident learning artifacts to accelerate recovery and improvements.

Quick Start

Generate a one-page engineering runbook for the target service by providing its name and owner team.

Frequently Asked Questions about eng-runbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an engineering runbook for on-call incidents?

Create an engineering runbook for on-call incidents by providing the target service name and owner team to generate a structured HTML/Markdown artifact. This artifact includes sections for service overview, alerts, dashboards, procedures, on-call rotation, and an incident-response checklist.

What is an SRE runbook and why do I need one for my services?

An SRE runbook is a single, portable reference that guides on-call teams through incident handling to reduce Mean Time To Resolve (MTTR). You need one to ensure consistent responses across services during outages and performance degradations.

Can I generate a one-page runbook that includes common procedures like deploys and rollbacks?

Yes, you can generate a one-page runbook that includes common procedures with copy-pasteable commands for deploys, rollbacks, and key rotation. It also provides dashboards and an incident-response checklist to accelerate recovery.

Does the generated runbook support validation against safety constraints?

Yes, the generated runbook supports validation against safety constraints. The output is a structured HTML/Markdown artifact that includes frontmatter, optional resources, and validated safety checks for incident response.

What's the best way to document on-call rotation and incident response checklists?

Document on-call rotation and incident-response checklists by automating runbook generation to produce a single-page reference. This ensures teams have coordinated responses and post-incident learning artifacts to accelerate improvements.

What format does the automated runbook generator output for incident response?

The automated runbook generator outputs a structured HTML/Markdown artifact for incident response. This format includes a frontmatter section, optional resources, and sections for alerts, dashboards, and procedures.