skill

Runbook

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.

Anthropic4.80+ installsVetted

About

# /runbook

> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).

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

## Usage

``` /runbook $ARGUMENTS ```

## 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] ``` [Exact command, action, or instruction] ``` **Expected result:** [What should happen] **If it fails:** [What to do]

#### Step 2: [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] | ```

## 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

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

Install

Run this command

git clone https://github.com/anthropics/knowledge-work-plugins && cp -r knowledge-work-plugins/operations/skills/runbook ~/.claude/skills/

Works with

claude appclaude codeclaude apicursorcodexwindsurfclinezed

Manual steps

Clone the repository and copy the `operations/skills/runbook` folder into your Claude skills directory. Compatible with Claude Code, Cursor, Codex, and any Agent Skills-compatible agent.

View source
License: Apache-2.0By Anthropic

Frequently asked questions

What is the Runbook skill?

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.

How do I install Runbook?

Run this in your terminal:

git clone https://github.com/anthropics/knowledge-work-plugins && cp -r knowledge-work-plugins/operations/skills/runbook ~/.claude/skills/
Which AI tools does Runbook work with?

It works with claude_app, claude_code, claude_api, cursor, codex, windsurf, cline, zed.

Who made Runbook?

Anthropic, released under the Apache-2.0 license.

Is Runbook free?

Yes, it is free to use under the Apache-2.0 license.

Related assets

More curated picks in Productivity & Office.

All Runbook alternatives →

Audit before you install

Run any source through our checks - AI visibility, security, performance, and stack detection.

More in Productivity & Office