create-runbooks

Generate operational and troubleshooting runbooks from repository evidence and commands.

Updated Feb 10, 2026

Search Tags:#automation #devops #documentation #troubleshooting #operations #runbooks

Ready to run

npx skills add https://github.com/jrodrigopuca/skills --skill create-runbooks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-runbooks
Source: https://github.com/jrodrigopuca/skills/tree/main/create-software-docs/sub-skills/create-runbooks
Command: npx skills add https://github.com/jrodrigopuca/skills --skill create-runbooks

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of operational and troubleshooting runbooks, ensuring clear, evidence-based procedures for managing software systems.

Core Features & Use Cases

Automated Runbook Generation: Creates detailed runbooks for operational and troubleshooting scenarios.
Evidence-Based Procedures: Grounds instructions in repository artifacts and verifiable commands.
Use Case: When a new service is deployed, this Skill can automatically generate a runbook detailing its deployment, common operational tasks, and troubleshooting steps based on its configuration and scripts.

Quick Start

Generate an operational runbook for the 'user-authentication-service' scope.

Frequently Asked Questions about create-runbooks

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

FAQPage Schema

How do I generate operational runbooks for a newly deployed service?▼

To generate operational runbooks, you define a specified scope and provide deployment evidence, commands, and validation findings. The Skill then produces documentation with exact procedures, verification steps, rollback instructions, and escalation notes in the scope's docs/runbooks directory.

What is an evidence-based troubleshooting runbook?▼

An evidence-based troubleshooting runbook grounds its operational instructions in repository artifacts and verifiable commands. This ensures that procedures, verification steps, and rollback instructions are directly traceable to actual system configurations and scripts.

How do I document rollback instructions and escalation procedures for DevOps operations?▼

You document rollback instructions and escalation procedures by providing deployment evidence and validation findings to the runbook generator. It automatically structures these operational details within the generated docs/runbooks directory for the specified scope.

Does this runbook generator warn before destructive operations?▼

Yes, the runbook generator explicitly warns before destructive operations. It structures operational and troubleshooting procedures to include these warnings alongside verification steps and rollback instructions to ensure safe system management.

What do I need to provide to automate runbook creation for a specific scope?▼

To automate runbook creation, you must provide the specified scope, deployment evidence, exact commands, and validation findings. These inputs allow the Skill to generate accurate operational procedures and documentation.

Where are the generated operational runbooks stored in the repository?▼

Generated operational runbooks are stored under the specified scope's docs/runbooks directory. This ensures the documentation is organized and accessible within the repository structure.