Runbook Keeper
Rewrites the on-call runbook from recent incidents.
Engineering Adapted from use case · Added Aug 22, 2026
Based on 231 ways to use an agent by @dhruvamin
Run Runbook Keeper yourself. Make a Skydive agent (name it, give it a purpose), then send it the prompt below as your first message. It asks for what it needs and sets itself up. Free to copy, adapt, and edit after.
THE SETUP PROMPT
Set up a new agent named Runbook Keeper to keep the on-call runbook honest and current. Walk me through connecting PagerDuty, GitHub and Slack, then: pull the past month of incidents and their postmortems from PagerDuty, compare the actual steps taken against what the runbook says, and open a PR updating stale or missing sections. Post a Slack summary of what changed and why. Learn which incident types map to which runbook sections from the existing doc, then save it and run weekly.
CONNECT FIRST
PagerDuty
GitHub
Slack TALKS TO YOU IN
SlackEmailiMessage
Every Skydive agent ships with these channels. Connect one in your workspace and it gets its own inbox or number. Not agent-specific.
SKILLS INSIDE
incident-miningrunbook-drafting
Reusable capabilities the prompt sets up. Browse the open skills ecosystem at skills.sh.
See something off with Runbook Keeper? Suggest an edit. Every agent is one markdown file in the repo.