Runbook

by anthropicsae1513ea94dcNo license27K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.

FeaturedInstructions onlyDevOps & Cloud Productivity & Workflow

AI-generated overview

Creates or updates step-by-step operational runbooks for recurring tasks, including troubleshooting, rollback and escalation.

What it does: Produces a structured operational runbook document for a recurring task or procedure, following a fixed template with purpose, prerequisites, numbered procedure steps, verification, troubleshooting, rollback, escalation and history sections. Each step records the exact command or action, the expected result and what to do if it fails. It can also extend an existing procedure with troubleshooting and rollback steps, and optionally search a knowledge base or link to ITSM records when those connectors are available.
When to use it: Use it when on-call or operations staff need a repeatable procedure documented precisely, when tribal knowledge must be turned into exact commands, or when an existing procedure needs failure modes, rollback and escalation paths added.
Requirements: Instructions only; no scripts are shipped. Connector integrations (knowledge base, ITSM) are optional and only used if available.

/runbook

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Create a step-by-step operational runbook for a recurring task or procedure.

Usage

Output

markdown

## Runbook: [Task Name]**Owner:** [Team/Person] | **Frequency:** [Daily/Weekly/Monthly/As Needed]**Last Updated:** [Date] | **Last Run:** [Date]
### Purpose[What this runbook accomplishes and when to use it]
### Prerequisites- [ ] [Access or permission needed]- [ ] [Tool or system required]- [ ] [Data or input needed]
### Procedure
#### Step 1: [Name]

## Runbook: [Task Name]**Owner:** [Team/Person] | **Frequency:** [Daily/Weekly/Monthly/As Needed]**Last Updated:** [Date] | **Last Run:** [Date]
### Purpose[What this runbook accomplishes and when to use it]
### Prerequisites- [ ] [Access or permission needed]- [ ] [Tool or system required]- [ ] [Data or input needed]
### Procedure
#### Step 1: [Name]

[Exact command, action, or instruction]

**Expected result:** [What should happen]**If it fails:** [What to do]
### Verification- [ ] [How to confirm the task completed successfully]- [ ] [What to check]
### Troubleshooting| Symptom | Likely Cause | Fix ||---------|-------------|-----|| [What you see] | [Why] | [What to do] |
### Rollback[How to undo this if something goes wrong]
### Escalation| Situation | Contact | Method ||-----------|---------|--------|| [When to escalate] | [Who] | [How to reach them] |
### History| Date | Run By | Notes ||------|--------|-------|| [Date] | [Person] | [Any issues or observations] |

**Expected result:** [What should happen]**If it fails:** [What to do]
### Verification- [ ] [How to confirm the task completed successfully]- [ ] [What to check]
### Troubleshooting| Symptom | Likely Cause | Fix ||---------|-------------|-----|| [What you see] | [Why] | [What to do] |
### Rollback[How to undo this if something goes wrong]
### Escalation| Situation | Contact | Method ||-----------|---------|--------|| [When to escalate] | [Who] | [How to reach them] |
### History| Date | Run By | Notes ||------|--------|-------|| [Date] | [Person] | [Any issues or observations] |

If Connectors Available

If ~~knowledge base is connected:

Search for existing runbooks to update rather than create from scratch
Publish the completed runbook to your ops wiki

If ~~ITSM is connected:

Link the runbook to related incident types and change requests
Auto-populate escalation contacts from on-call schedules

Tips

Be painfully specific — "Run the script" is not a step. "Run python sync.py --prod --dry-run from the ops server" is.
Include failure modes — What can go wrong at each step and what to do about it.
Test the runbook — Have someone unfamiliar with the process follow it. Fix where they get stuck.

Source and attribution

Source:anthropics/knowledge-work-pluginsinoperations/skills/runbookat commitae1513e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from anthropics/knowledge-work-plugins

Ticket Deflector

anthropics

Featured

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

Awaiting classification27Kupdated today

Tax Season Organizer

anthropics

Featured

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

Awaiting classification27Kupdated today

Tax Prep

anthropics

Featured

Prepares tax materials from closed books: a quarterly estimated payment breakdown or a year-end 1099-NEC list and accountant packet.

Business & Finance27Kupdated today

Smb Onboard

anthropics

Featured

Guides a small-business owner through first-time setup: connecting tools, running a value-proof recipe, capturing business context, and setting a weekly…

Productivity & Workflow27Kupdated today

Smb Router

anthropics

Featured

Routes a small-business owner's request to the right plugin skill or command and explains what is available.

Productivity & Workflow27Kupdated today

Month End Prep

anthropics

Featured

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

Awaiting classification27Kupdated today

Runbook

/runbook

Usage

Output

If Connectors Available

Tips

Source and attribution

More from anthropics/knowledge-work-plugins

Ticket Deflector

Tax Season Organizer

Tax Prep

Smb Onboard

Smb Router

Month End Prep

More in DevOps & Cloud

M5 Onboard

Incident Response

Deploy Checklist

Spanner Basics

Secops Cases

Managed Airflow Migrations