New to Claude Skills? Learn how to install them →

anthropics on GitHub

Runbook Creator

OfficialFree

Streamline operational procedures with detailed runbooks.

Get this skill

Free · Opens the source repo

What Runbook Creator does

The Runbook Creator skill is designed to assist teams in documenting operational procedures for recurring tasks. By generating comprehensive runbooks, this skill helps transform informal knowledge into structured, step-by-step guides that can be easily followed by on-call or operations teams. This is particularly useful in environments where consistency and clarity are crucial for maintaining operational efficiency.

When using the Runbook Creator, users can specify various details about the task, including its purpose, prerequisites, and the exact steps required to complete it. Each step includes expected outcomes and troubleshooting advice, ensuring that users are prepared for potential issues that may arise during execution. In addition, the skill provides sections for verification, rollback procedures, and escalation paths, making it a robust tool for operational documentation.

This skill is particularly beneficial for teams that frequently handle similar tasks and need to ensure that all members can execute these tasks without ambiguity. It is ideal for IT operations, DevOps teams, and any organization that relies on repeatable processes to maintain service quality and reliability. By utilizing this skill, teams can reduce the risk of errors and improve response times during incidents.

The Runbook Creator also offers integration capabilities with other tools, allowing users to search for existing runbooks and link them to related incident types, enhancing overall operational efficiency. By documenting procedures in a clear and organized manner, this skill not only aids in immediate task execution but also serves as a valuable resource for training new team members.

When to use it

Use this skill when you need to document a procedure that will be executed repeatedly by your team, ensuring clarity and consistency.

When not to use it

This skill may not be suitable for one-off tasks or highly variable processes that do not require standardized documentation.

What you can build with it

Documenting Routine Server Maintenance

Use the Runbook Creator to outline the steps for routine server maintenance tasks, ensuring all team members follow the same procedure.

Creating Incident Response Procedures

Develop a runbook for responding to common incidents, detailing escalation paths and troubleshooting steps for quick resolution.

Standardizing Deployment Processes

Document the deployment process for applications, including rollback procedures and verification steps to ensure successful updates.

How to install Runbook Creator

View source

1. Install with the skills CLI

npx skills add anthropics/knowledge-work-plugins/runbook --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by anthropics

/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

/runbook $ARGUMENTS

Output

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

Frequently asked questions about Runbook Creator

Similar skills