eng-runbook

Generate a compact HTML engineering runbook with service overview, alerts, dashboards, procedures, on-call rotation, and incident response.

84.7k|9.9k|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/nexu-io/open-design --skill eng-runbook-nexu-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-runbook
Source: https://github.com/nexu-io/open-design/tree/main/skills/eng-runbook
Command: npx skills add https://github.com/nexu-io/open-design --skill eng-runbook-nexu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables engineering teams to generate a compact, standardized runbook that documents service overview, dependencies, alerts, dashboards, on-call rotations, and incident-response steps in a single HTML artifact.

Core Features & Use Cases

  • Generates a self-contained, single-page HTML runbook suitable for on-call pages, handoffs, and runbook sharing.
  • Includes sections for service summary, dependencies, alerts table, dashboards/links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist.
  • Designed for SRE/governance workflows, enabling rapid incident response and knowledge transfer across teams.

Quick Start

Provide the service name and incident context to generate a ready-to-use HTML runbook.

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 SRE runbook for incident response?

Generate a self-contained HTML runbook by providing your service name and incident context. The output consolidates service summaries, alerts, dashboards, procedures, on-call rotations, and incident-response checklists into a single shareable page.

What should be included in an on-call runbook for service handoffs?

An on-call runbook should include a service summary, dependencies, alerts table, dashboard links, common procedures with copy-pasteable commands, on-call rotation details, and an incident-response checklist within a single HTML page.

Can I generate a single-page HTML runbook for multiple API and web services?

Yes, this Skill applies to web, mobile, and API services by generating a standardized, self-contained HTML runbook that consolidates operational guidance and incident-response procedures for each specific service context.

What is the best way to document deploy procedures for on-call incidents?

Document deploy procedures by generating a compact HTML runbook that features a dedicated section for common procedures, including copy-pasteable commands and an incident-response checklist to guide rapid on-call action during deployments.

Does this runbook generation approach support extensible scripts and references?

Yes, the runbook generation supports optional scripts, references, and assets directories for extensibility. It uses a frontmatter-driven entry point that provides operational guidance alongside the generated HTML artifact.

Why use a single HTML artifact for ops docs instead of a wiki?

A single HTML artifact ensures runbook information is self-contained and instantly shareable during on-call incidents. Unlike fragmented wikis, it consolidates alerts, dashboards, and procedures into one actionable page without navigation friction.