---
name: create-runbook
description: Author a reusable runbook, or extract one from a completed investigation, following this repo's runbook standard. Use whenever a multi-step procedure, diagnosis, or recipe should be captured so future agents can reuse it.
disable-model-invocation: true
metadata:
  internal: true
---

# Create Runbook

Capture procedural knowledge as a runbook in `runbooks/`, following the authoring
standard in `runbooks/AGENTS.md`. Read that file first — it defines the retrieval
mechanics, frontmatter contract, split/merge rules, fact-ownership model, contract
style, and validation. This skill is the procedure for producing one runbook.

## When to use

- After a multi-step investigation whose pattern others could reuse.
- To add a new stage to the investigation pipeline.
- To turn an ad-hoc recipe (a query pattern, an optimization) into a durable how-to.

## Steps

1. **Check it should be a new file.** Search the existing registry
   (`panda search runbooks "…"` with a few phrasings). Content that would always be
   retrieved together with an existing runbook belongs IN that runbook — the split
   axis is co-retrieval, not topic count. Only mutually-exclusive-in-use content gets
   its own file.

2. **Extract the pattern, not the incident.** Generalize: what is the reusable
   diagnostic shape? Drop run-specific ids, timestamps, and host names.

3. **Engineer the retrieval surface first.** Write the `description` (what + when,
   third person, ≤1024 chars) and 3-6 `triggers` as the literal queries a caller would
   type, packed with exact identifiers (table names, error strings, API names). Body
   sections are embedded too (per-section child vectors), so mid-document facts are
   findable — but the metadata surface dominates ranking, so it decides whether the
   runbook wins the queries it should.

4. **Make it self-contained for its task.** Restate load-bearing facts briefly with a
   pointer to their canonical owner (`runbooks://<owner>`); reserve links for adjacent
   tasks. A required fact that lives only behind a link is a bug.

5. **Write to the standard's structure**: owns-line, Inputs (liberal), Output,
   Procedure; tables for decision matrices, numbered lists for procedures, positive
   directives, decisive rule up front. If the output feeds another stage: one filled
   example, ≤10 top-level fields, summary/reasoning before verdicts, confidence as
   `low|medium|high` per `runbooks://evidence_discipline`.

## Verify

- `go test ./runbooks/...` — frontmatter, refs, uniqueness.
- `panda search runbooks "<one of your triggers>"` returns the new runbook.
- `scripts/runbook-retrieval-check.sh` still passes (add a golden query for the
  new runbook while you're there).
- The server logs `Runbook registry loaded` with the new count.

$ARGUMENTS


---
Source attribution: ethpandaops
Original project: https://github.com/ethpandaops/mcp/blob/3346e64d6cdbab49fbce4904f94fb6398cf0297c/.claude/skills/create-runbook/SKILL.md
License: MIT
License information: https://opensource.org/license/mit
Original upstream instructions; downloaded from Dave AI.

## Upstream license notice

MIT License

Copyright (c) 2024 ethpandaops

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.



# Dave AI resource metadata

Creator / publisher: ethpandaops
Original project: https://github.com/ethpandaops/mcp/blob/3346e64d6cdbab49fbce4904f94fb6398cf0297c/.claude/skills/create-runbook/SKILL.md
Attribution basis: Recovered original package and original project license at a pinned revision

Fields of work: Content & Media, Operations, Project & Program Management, Sales, Customer Support
Roles: Customer Success Manager, Operations Manager, Project Manager, Support Agent, Technical Writer
Specialties: Specialty not specified
Tools: Xatu
Country applicability: Country not specified
Classification basis: Source catalog labels
Instruction SHA-256: ff3df54f21e3855d3ea77a3bf37f4b8e6cb1fb4a44c723cd267bf587fa3705a5
Metadata reviewed: 2026-10-27
This metadata supersedes earlier Dave AI catalog attribution. Original instruction and supporting files are preserved.
