Does the generated runbook include actual CLI commands?

Yes, based on the system analysis, the skill attempts to provide actionable, tested commands, environment variable placeholders, and expected output examples.

What types of runbooks can this skill generate?

The skill supports four specific categories: Incident (for active alerts), Operational (for standard procedures), Troubleshooting (for diagnostic fixes), and Emergency (for critical recovery actions).

How does the skill handle runbook versioning and storage?

It follows a predefined directory priority (e.g., docs/runbooks/) and uses an incrementing ID system (e.g., RB-001) or date-based sequencing to ensure organized documentation.

Can I target specific services when creating a runbook?

Yes, you can use the --service flag to specify the system name, which ensures the generated metadata and context are correctly mapped to that specific component.

Operational Runbook Architect

Name: Operational Runbook Architect
Author: melodic-software

bymelodic-software

•

Learning & Documentation

Generates comprehensive, standardized operational runbooks and incident response protocols through automated system analysis.

The Operational Runbook Architect skill streamlines the creation of mission-critical documentation for DevOps and SRE teams. By analyzing your system context, it generates structured Markdown runbooks for incident response, routine operations, troubleshooting, and emergency protocols. Each runbook is automatically versioned and includes essential components like metadata tracking, step-by-step procedures with actual commands, verification checklists, and escalation paths. This skill is ideal for teams looking to standardize their documentation, reduce Mean Time to Resolution (MTTR), and ensure operational consistency across complex services.

Key Features

01Interactive analysis of prerequisites, alert triggers, and system metrics to ensure actionable content.

0238 GitHub stars

03Automated file organization and versioning using standardized naming conventions and sequential ID numbering.

04Context-aware generation for four distinct runbook types: incident, operational, troubleshooting, and emergency.

05Standardized metadata tables for tracking service ownership, severity levels, and last-updated timestamps.

06Integrated communication templates and escalation paths for streamlined incident management.

Use Cases

01Standardizing incident response procedures for new microservices to reduce operational downtime.

02Generating diagnostic troubleshooting guides based on recurring error patterns or service crash loops.

03Documenting complex database failover or production deployment procedures for team onboarding.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add melodic-software/claude-code-plugins create-runbook

For use in Claude.ai and ChatGPT

Download Skill