runbook-generator

Generate standardized runbook skeletons from a service name via CLI.

Updated Nov 28, 2025
One-click install
npx skills add https://github.com/moshesham/Economic-Dashboard-API --skill runbook-generator-moshesham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runbook-generator
Source: https://github.com/moshesham/Economic-Dashboard-API/tree/main/.github/skills/runbook-generator
Command: npx skills add https://github.com/moshesham/Economic-Dashboard-API --skill runbook-generator-moshesham

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Runbook Generator helps teams quickly create standardized operational runbooks for services, reducing onboarding time and inconsistencies across teams.

Core Features & Use Cases

  • Runbook skeleton generation from a CLI
  • Standard sections for start/stop/health/rollback
  • Structured escalation and incident handling placeholders
  • Reference templates for deployment and incident playbooks

Quick Start

Run the generator to create a skeleton runbook for a service, then customize the resulting document.

Frequently Asked Questions about runbook-generator

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

FAQPage Schema
How do I generate a standardized runbook for a new service?

To generate a standardized runbook, run the CLI-based skeleton generator using a service name. It outputs a document with standard sections for start/stop, health checks, and rollback procedures to ensure operational consistency.

What sections should an incident response runbook include for SRE operations?

An incident response runbook should include structured escalation placeholders, incident handling steps, and standard health and rollback sections. This generator creates these predefined sections automatically to standardize SRE workflows.

Does this runbook generator work with existing DevOps automation workflows?

Yes, the runbook generator fits DevOps automation workflows by providing CLI-based skeleton generation. It outputs reference templates for deployment and incident playbooks that can be integrated into existing automation pipelines.

Can I use this to create onboarding documentation for new services?

Yes, you can create onboarding documentation by generating a skeleton runbook from a service name. It standardizes operational knowledge, reducing onboarding time and inconsistencies across teams.

What is the best way to standardize maintenance and rollback workflows across services?

The best way to standardize maintenance and rollback workflows is using a skeleton runbook generator. It applies consistent templates across services, ensuring all maintenance procedures and rollback steps follow the same structured format.