ops-runbook

Create structured operational runbooks with commands, verification, troubleshooting, and rollback steps.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/EvolutionAPI/evo-nexus --skill ops-runbook-evolutionapi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops-runbook
Source: https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/ops-runbook
Command: npx skills add https://github.com/EvolutionAPI/evo-nexus --skill ops-runbook-evolutionapi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates clear, testable operational runbooks that convert tribal knowledge into reproducible, step-by-step procedures to reduce human error during routine operations, maintenance, and incident handling.

Core Features & Use Cases

  • Step-by-step Procedures: Produce ordered steps with exact commands, expected outcomes, and verification checks to ensure repeatability.
  • Troubleshooting & Rollback: Include a troubleshooting table, probable causes, solutions, and safe rollback instructions for failed steps.
  • Escalation & History: Define escalation contacts and methods alongside a change/history log to track updates and ownership.
  • Integrations: When connectors are available, find and update existing runbooks in Notion or link to related Linear issues for incident/change tracking.
  • Use Case: On-call engineers or operations teams can transform a recurring maintenance task or incident playbook into an audited runbook that anyone can follow.

Quick Start

Use the ops-runbook skill to create or update a step-by-step operational runbook for [process name], including prerequisites, exact commands, verification steps, troubleshooting, rollback, and escalation contacts.

Frequently Asked Questions about ops-runbook

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

FAQPage Schema
How do I create an operational runbook for on-call incident procedures?

Create an operational runbook by defining prerequisites, step-by-step commands, expected outcomes, verification checks, troubleshooting tables, rollback instructions, and escalation contacts. This structured approach ensures on-call incident procedures are reproducible and reduce human error during routine operations and maintenance.

What is the best way to document rollback steps for failed maintenance tasks?

The best way to document rollback steps is to include a troubleshooting table mapping probable causes to solutions, followed by safe rollback instructions for failed steps. This converts tribal knowledge into testable procedures so anyone can safely revert failed maintenance tasks.

Can I link operational runbooks to existing Notion pages or Linear issues?

Yes, you can link operational runbooks to existing Notion pages or Linear issues when connectors are available. This integration allows you to find and update runbooks in Notion or link related Linear issues for incident and change tracking.

Does generating an operations playbook require prior documentation of scheduled jobs?

Generating an operations playbook does not require prior documentation. It transforms undocumented tribal knowledge of scheduled jobs and maintenance scripts into structured, audited runbooks with ordered steps, verification checks, and change history logs.

What should an on-call handoff runbook include to ensure repeatable change tasks?

An on-call handoff runbook should include prerequisites, exact commands, expected outcomes, verification steps, troubleshooting tables, rollback instructions, escalation contacts, and change history. These elements ensure repeatable change tasks are clear and testable for any operations engineer.