eng-runbook

Generate a single-page HTML engineering runbook from an input brief.

1|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/PiercingXX/xx-stack --skill eng-runbook-piercingxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-runbook
Source: https://github.com/PiercingXX/xx-stack/tree/main/packs/design/runtime/skills/design/eng-runbook
Command: npx skills add https://github.com/PiercingXX/xx-stack --skill eng-runbook-piercingxx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It turns vague operational knowledge into a consistent, one-page runbook that engineers can follow quickly during incidents and day-to-day operations.

Core Features & Use Cases

  • Runbook generation for a specific service: Produces a single-page HTML runbook covering service overview, dependencies, alerts, dashboards, procedures, on-call rotation, and an incident-response checklist.
  • Operational readiness formatting: Enforces a clear structure (alerts table, procedure cards, rotation table, and a step-by-step incident flow) designed for fast scanning under pressure.
  • Use case: When a team needs an up-to-date ops document for an authentication or payment service, generate a runbook that includes the most important alerts, what they mean, how to respond first, and the exact rollback/key-rotation/mitigation commands to use.

Quick Start

Ask the AI to generate an engineering runbook for the auth service including alerts, dashboards, common procedures with copy-pasteable commands, on-call rotation, and a first-30-min incident response checklist.

Frequently Asked Questions about eng-runbook

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

FAQPage Schema
How do I generate an engineering runbook for on-call incident response?

To generate an engineering runbook, provide a service brief to convert into a single-page HTML document covering service overview, alert triage, dashboards, procedures, on-call rotation, and an incident-response checklist.

What should be included in an SRE ops doc for production operations?

An SRE ops doc should include a service overview, dependencies, an alerts dashboard, common operational procedures with commands, on-call rotation tables, and a first-30-min incident response checklist for fast scanning.

Can I create an HTML incident-response checklist with copy-pasteable mitigation commands?

Yes, you can generate an HTML incident-response checklist that structures common procedures into copy-pasteable rollback and key-rotation commands formatted for quick operational access during incidents.

Does this runbook generator format operational readiness documentation for fast scanning?

This runbook generator formats operational readiness documentation into a single-page HTML layout with an alerts table, procedure cards, rotation table, and step-by-step incident flow designed for scanning under pressure.

What is the best way to document alert triage guidance for an authentication service?

The best way to document alert triage guidance is to generate a structured runbook that lists important alerts, explains what they mean, and provides the exact first-response and mitigation commands to use.