Incident Response & On-Call Readiness Audit
Asks whether your team could handle a bad night: who answers, how they get in, and what they do next.
What it examines
- One person holding the pager and no one behind them
- Alerts with no runbook
- No agreed way to run an incident
- Reviews that blame a person and set no actions
- Emergency access that fails with the system
- How long outages really take to find and fix
What you get back
A findings file. Each item has the evidence, how serious it is, and a fix.
Dependencies
- An AI coding agent that reads SKILL.md files, such as Claude Code, Codex or Gemini CLI
- Read access to the repository: runbooks, on-call and escalation notes, incident and postmortem documents, alert rule files, code owner files and any service catalogue
- Optional but the strongest evidence: an export of incidents from your paging, ticket or chat tool, with start, detection and resolution times
- Optional: page counts per person and per hour, to show the on-call load
- Python 3 with the jsonschema package, to check findings.json before fixing anything
How it works
The audit only reads. It never pages anyone, posts to a channel or opens or closes an incident.
It finds the incident and paging tools in use afresh and runs every readiness check against your runbooks, alerts and records.
Most of this evidence lives outside the repository. It asks for what is missing and records what it cannot get as insufficient evidence. Without an incident export, time-based checks rely on what your postmortems state.
You get findings.json and findings.md. The remediate skill reads findings.json, writes the documents it can, and plans the rest.
Setup
- Unzip the download, then copy the audit and remediate folders into your agent's skills folder (for Claude Code, .claude/skills/) in the repository you want to check.
- Export recent incidents and on-call page counts from your paging or ticket tool if you can.
- Open the repository in your agent and ask it to run the i5-incident-response-readiness-audit skill.
- Check the result with the validator: pip install jsonschema, then python3 schema/validate.py findings.json.
- Ask your agent to run the i5-incident-response-readiness-remediate skill using findings.json.
Run it with your agent
Copy the prompt, fill in the parts in square brackets, and paste it into your agent.
Run the i5-incident-response-readiness-audit skill on this repository. Incident export: [path, or none]. On-call page counts: [path, or none]. Never page anyone or post to a channel. Mode: audit only. Do not change any code. Write findings.json and findings.md in the repository root.
Run the i5-incident-response-readiness-remediate skill using findings.json. Work through the findings I choose, and leave the rest open.