runbook-generator

Name: runbook-generator
Availability: InStock
Author: luminairprime

Generate structured Markdown runbook skeletons for microservices and platform services.

1|Updated Mar 9, 2026

Search Tags:#automation #devops #deployment #runbook #sre #incident-response #ops-documentation

Ready to run

npx skills add https://github.com/LuminairPrime/openwrt-docs4ai-pipeline --skill runbook-generator-luminairprime

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: runbook-generator
Source: https://github.com/LuminairPrime/openwrt-docs4ai-pipeline/tree/main/.kilocode/skills/runbook-generator
Command: npx skills add https://github.com/LuminairPrime/openwrt-docs4ai-pipeline --skill runbook-generator-luminairprime

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Quickly provides a consistent, editable runbook scaffold for services that lack standard operational documentation, reducing on-call confusion and untested recovery procedures.

Core Features & Use Cases

Runbook skeleton generation: Creates structured Markdown with overview, preconditions, start/stop, health checks, deployment checklist, rollback, incident response, escalation, and post-incident sections.
CLI-driven output: Supports printing to stdout or writing a curated runbook file with owner and environment metadata.
Use Cases: Useful for service onboarding, standardizing runbooks across teams, preparing deployment and rollback playbooks, and generating incident response scaffolding for SRE workflows.

Quick Start

Generate a runbook skeleton for the service payments-api and save it to docs/runbooks/payments-api.md with owner platform and environment production.

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 skeleton for a microservice?▼

Generate a structured Markdown runbook skeleton for microservices by providing the service name, outputting sections for start/stop, health checks, deployment, and rollback to a specified file path.

What sections should an SRE incident response runbook include for on-call workflows?▼

An SRE incident response runbook should include overview, preconditions, health checks, rollback, incident response, escalation, and post-incident sections to reduce on-call confusion during service recovery.

Can I specify the owner and environment metadata when creating ops documentation?▼

Yes, you can pass command-line parameters to specify owner and environment metadata, generating a curated runbook file with the correct environment context for platform services.

What is the best way to standardize deployment and rollback playbooks across teams?▼

Standardize deployment and rollback playbooks by generating consistent Markdown scaffolds with preconditions and checklists, ensuring all teams follow tested recovery procedures for service onboarding.

Does this runbook generator support writing output directly to a documentation path?▼

Yes, the runbook generator supports writing output directly to a specified path like docs/runbooks, or printing the structured Markdown to stdout for pipeline integration.