runbook

Generate dated Obsidian runbooks from codebase and infrastructure analysis.

5|2|Updated Dec 11, 2025

Search Tags:#automation #obsidian #infrastructure #operations #runbook #incident-response

Ready to run

npx skills add https://github.com/thoreinstein/opencode-config --skill runbook

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: runbook
Source: https://github.com/thoreinstein/opencode-config/tree/main/skill/runbook
Command: npx skills add https://github.com/thoreinstein/opencode-config --skill runbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of operational runbooks by analyzing codebases and infrastructure to produce precise, actionable procedures for deployment, maintenance, troubleshooting, and incident response.

Core Features & Use Cases

Parallel investigation tracks: codebase exploration, infrastructure analysis, and external research.
Output to Obsidian: dated runbook files stored in the vault for consistent documentation.
Document templates and structure ensure repeatable, high-quality procedures.

Quick Start

Provide Topic and Scope to initiate runbook generation. The tool analyzes the repository and infrastructure and writes a dated Markdown document to Obsidian at Runbooks/YYYY-MM-DD-service-operation.md. Open the Obsidian vault to review the generated runbook.

Frequently Asked Questions about runbook

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

FAQPage Schema

How do I generate an incident response runbook from my infrastructure and codebase?▼

To generate an incident response runbook, provide a topic and scope to trigger parallel investigation tracks across your codebase and infrastructure. This analyzes configurations and dependencies to output a structured, actionable procedure document.

Can I automatically create deployment and failover procedures in Obsidian?▼

Yes, you can create deployment and failover procedures that output directly to Obsidian. The tool writes dated Markdown files into your vault, storing them at Runbooks/YYYY-MM-DD-service-operation.md for consistent operational documentation.

What is an operational runbook and when do I need one for maintenance?▼

An operational runbook is a structured document containing actionable procedures for maintenance, scaling, and troubleshooting. You need one when you want to standardize infrastructure operations and infer context from your codebase to resolve incidents consistently.

Does this runbook generator work without external dependencies?▼

Yes, the runbook generator operates without external dependencies. It runs parallel investigation tracks for codebase exploration, infrastructure analysis, and external research to infer context and extract configurations entirely within its internal processing logic.

What's the best way to document troubleshooting procedures for complex services?▼

The best way to document troubleshooting procedures is to use document templates that ensure repeatable, high-quality output. By analyzing your repository and infrastructure, the tool produces precise, dated procedures tailored to your specific service architecture.

What are the limitations of automating runbook generation from code?▼

Automating runbook generation relies on analyzing codebases and infrastructure to infer context, meaning output quality depends on repository structure and configuration visibility. Generated markdown files are stored in a fixed Obsidian vault path without alternative export formats.