AI AGENTS
On-call agent: Scheduled runbook drill with safe shell rehearsal
On a weekly schedule, an agent rehearses a chosen runbook by running its read-only steps against staging and reports drift, broken commands, and stale instructions to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule selects next runbook
- ActionParse runbook, mark rehearsal-safe steps
- ActionRun safe shell steps against stagingShell
- LogicCompare results to expected, detect drift
- OutputPost freshness report to SlackSlack
What it does
Keeps runbooks honest. On a schedule, the agent picks a runbook, executes only its read-only and dry-run-safe steps against staging, and flags anything that errored, drifted, or no longer matches reality.
When to use it
Use it to catch rotten runbooks before an incident does. Great for teams whose docs silently go stale between pages.
How it works
- 1A weekly cron schedule triggers the workflow with the next runbook in rotation.
- 2The agent parses the runbook into discrete steps and marks which are safe to rehearse.
- 3It runs the safe shell steps against the staging target and captures results.
- 4It compares observed behavior against the runbook's documented expectations and detects drift.
- 5It compiles a freshness report listing broken commands, changed outputs, and stale notes.
- 6The report is posted to the platform Slack channel with a per-step pass or fail.
Set it up
What you configure once, before turning it on.
- 1Connect ShellRun sandboxed commands inside the workspace.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.