runbook

Document repeatable tasks as step-by-step runbooks with owners, prerequisites, and escalation sections.

704|58|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/openyak/desktop --skill runbook-openyak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runbook
Source: https://github.com/openyak/desktop/tree/main/backend/app/data/plugins/operations/skills/runbook
Command: npx skills add https://github.com/openyak/desktop --skill runbook-openyak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and maintain step-by-step runbooks for recurring tasks or procedures, turning tacit knowledge into explicit, auditable instructions that guide on-call and operations teams and reduce error-prone handoffs.

Core Features & Use Cases

  • Create new runbooks for common tasks and update existing ones with troubleshooting, rollback, and escalation steps.
  • Standardize on-call procedures, incident response playbooks, and routine maintenance to reduce miscommunication and delays.
  • Use cases include documenting backup procedures, change implementations, and post-incident reviews to capture lessons learned.

Quick Start

Provide the task name to generate a complete runbook draft.

Frequently Asked Questions about runbook

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

FAQPage Schema
How do I create step-by-step runbooks for on-call procedures?

To create runbooks, provide a task name to generate a structured draft including owners, prerequisites, verification, troubleshooting, rollback, and escalation sections. This standardizes on-call procedures and incident response.

What is the best way to document tribal knowledge for routine maintenance tasks?

Documenting tribal knowledge for routine maintenance requires turning tacit instructions into explicit, auditable runbooks. Provide the task name to generate step-by-step procedures that reduce error-prone handoffs and ensure consistency.

How do incident response playbooks help reduce miscommunication during operations?

Incident response playbooks reduce miscommunication by standardizing on-call procedures into step-by-step runbooks. They include rollback and escalation steps to guide operations teams, ensuring quick recovery and minimizing delays.

Can I update existing runbooks with new troubleshooting and rollback steps?

Yes, you can update existing runbooks with troubleshooting, rollback, and escalation steps. This maintains auditable instructions for recurring tasks and captures lessons learned during post-incident reviews.

What sections should be included when documenting standard operating procedures?

Standard operating procedures should include owners, frequency, prerequisites, steps, verification, troubleshooting, rollback, and escalation sections. Structuring runbooks with these sections ensures consistency and quick recovery for operations teams.