SkillVaultskills Browse all 500 skills

Reliability · Version 1.3.0 · Reviewed 2026-08-02

SRE Runbook Writer

Reduce production risk in runbook authoring and mitigation steps with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Writes runbooks with clear symptoms, verification steps, mitigations, and escalation criteria.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Runbook authoring
  • Mitigation steps
  • Escalation criteria

How SRE Runbook Writer works

You provide

Impact window, telemetry, and dependency state

It inspects

Saturation and blast radius behind runbook authoring

It decides

A mitigation steps plan that stabilizes before diagnosing

You verify

Detect, mitigate, and resolve times recorded separately

What it checks first

SRE Runbook Writer writes runbooks with clear symptoms, verification steps, mitigations, and escalation criteria. Use it when the work involves Runbook authoring, Mitigation steps, Escalation criteria.

  1. User-visible impact and error-budget consumption rather than component health.
  2. Saturation signals — queue depth, pool utilization, connection counts — near the onset.
  3. Whether the system recovered on its own, which indicates saturation rather than corruption.
  4. The blast radius and what boundary should have contained it.

Failure modes it recognizes

  • Retry amplification turning a partial failure into a total outage.
  • A shared dependency creating correlated failure across supposedly independent services.
  • Slow resource exhaustion invisible until a hard limit is crossed.
  • A rollback blocked by an incompatible migration.

Answers it will reject

  • Treating the trigger as the root cause, which stops the analysis before the fragility is identified.
  • Adding a runbook step where a boundary would remove the failure mode.
  • Measuring availability as a mean, which hides regional and tenant-level outages.

Decision rules it applies

  • Stabilize user impact before completing diagnosis.
  • Bound every retry with a budget, jitter, and a circuit breaker.
  • Prefer removing a failure mode over detecting it faster.

Evidence it asks for

  • Record time-to-detect, time-to-mitigate, and time-to-resolve separately.
  • Quantify impact in customer terms: failed requests, affected accounts, duration.
  • Verify recovery with the same signal that detected the failure.

The method inside

  1. Extract decisions, facts, and unresolved questions needed for runbook authoring.
  2. Organize mitigation steps around the reader's next decision or action rather than the source order.
  3. Draft escalation criteria with source traceability and no invented behavior.
  4. Run a completeness, consistency, audience, and actionability review before returning the artifact.

Deliverables

  • Runbook authoring assessment
  • Mitigation steps decision and action plan
  • Escalation criteria verification checklist

Evidence requirements

  • User-visible symptoms and SLO impact
  • Timeline, telemetry, deploys, and dependency state
  • Current mitigations and operational constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Write a runbook for our queue backlog alert so a new on-call engineer can act on it at 3am without escalating immediately.

Expected output

Structured it around what the responder sees first: how to confirm the backlog is real rather than a metrics lag, three mitigations ordered by blast radius, and the explicit point where continuing past your confidence should become an escalation instead...

Boundaries and compatibility

Ideal for

  • Runbook authoring: produce a decision or artifact grounded in supplied evidence.
  • Mitigation steps: produce a decision or artifact grounded in supplied evidence.
  • Escalation criteria: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Replacing incident command authority
  • Calling a trigger the root cause without a causal chain

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.