runbook-generator

Generate standardized Markdown runbook skeletons for software services.

Updated Nov 3, 2016
One-click install
npx skills add https://github.com/xleliberty/mydotfiles --skill runbook-generator-xleliberty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runbook-generator
Source: https://github.com/xleliberty/mydotfiles/tree/main/.config/.claude/plugins/cache/claude-code-skills/engineering-advanced-skills/2.1.2/runbook-generator
Command: npx skills add https://github.com/xleliberty/mydotfiles --skill runbook-generator-xleliberty

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill eliminates the inconsistency and lack of documentation for services by providing a standardized, repeatable framework for creating operational runbooks.

Core Features & Use Cases

  • Runbook Scaffolding: Automatically generates a structured Markdown skeleton including start, stop, health check, and rollback procedures.
  • Standardization: Ensures all team services follow the same operational documentation format, improving incident response and on-call efficiency.
  • Use Case: When onboarding a new microservice, use this tool to generate a baseline runbook that includes placeholders for escalation contacts, deployment steps, and incident response protocols.

Quick Start

Use the runbook-generator skill to create a new runbook for the payments-api service owned by the platform team.

Frequently Asked Questions about runbook-generator

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

FAQPage Schema
How do I create a standardized runbook for incident response?

To create a standardized runbook, use a generation script to output a structured Markdown skeleton covering health checks, rollback procedures, and escalation contacts. This ensures consistency across engineering teams for incident response and maintenance workflows.

What should be included in a service runbook for DevOps automation?

A service runbook should include deployment steps, health monitoring procedures, rollback workflows, and incident response protocols. Using a generation script creates a standardized Markdown skeleton with these sections to improve on-call efficiency and operational consistency.

Do I need Python 3 to generate operational runbook documentation?

Yes, you need Python 3 installed to execute the runbook generation script. The script uses Python 3 to process service inputs and produce structured Markdown output files for your operational documentation needs.

How do I scaffold a Markdown runbook for a new microservice?

You scaffold a Markdown runbook by running a generation script that creates a baseline document with placeholders for start, stop, health check, and rollback procedures. This provides a repeatable framework for onboarding new microservices with standardized operational documentation.

Can I use this runbook generator for SRE maintenance workflows?

Yes, this runbook generator supports SRE maintenance workflows by producing standardized operational skeletons. It creates Markdown files that document deployment, health monitoring, and rollback procedures to maintain consistency across engineering teams during maintenance.

What is the best way to automate operational documentation for software services?

The best way to automate operational documentation is using a script that generates standardized runbook skeletons in Markdown format. This approach ensures all services follow the same documentation format for deployment, health checks, and rollback procedures, reducing manual effort and inconsistency.