runbook

Generate operational runbooks with steps, prerequisites, troubleshooting, and rollback paths.

23.4k|2.8k|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill runbook-anthropics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runbook
Source: https://github.com/anthropics/knowledge-work-plugins/tree/main/operations/skills/runbook
Command: npx skills add https://github.com/anthropics/knowledge-work-plugins --skill runbook-anthropics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms complex or tribal knowledge into clear, step-by-step operational runbooks, ensuring consistency and reducing errors in recurring tasks.

Core Features & Use Cases

  • Procedure Documentation: Creates detailed guides for recurring tasks, including commands, expected results, and failure handling.
  • Troubleshooting & Rollback: Includes sections for diagnosing issues and reverting changes if necessary.
  • Use Case: Document the exact steps for deploying a new microservice, including pre-deployment checks, the deployment command, verification steps, and rollback procedures.

Quick Start

Create a runbook for the daily database backup process.

Frequently Asked Questions about runbook

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

FAQPage Schema
How do I document operational procedures for on-call engineers?

Documenting operational procedures for on-call engineers involves generating detailed runbooks with step-by-step instructions, prerequisites, verification, troubleshooting, and rollback paths. This ensures repeatable tasks are executed with clarity and safety.

What is the best way to create a runbook for recurring tasks?

Creating a runbook for recurring tasks requires detailing exact commands, expected results, and failure handling procedures. This standardizes operations and reduces errors by capturing tribal knowledge in a clear format.

How do I write step-by-step instructions for deploying a new microservice?

Writing deployment instructions involves documenting pre-deployment checks, the exact deployment command, verification steps, and rollback procedures. This creates a reliable operational runbook for the microservice deployment process.

Can I include escalation paths in my operational documentation?

Yes, generating operational runbooks includes defining escalation paths within the documentation. This supports on-call engineers by providing clear procedures for executing tasks and knowing when and how to escalate critical failures.