Find stale runbooks before they fail during an incident
Runbooks go stale quietly. Deploy paths change, services move, dependencies get renamed, and the doc only gets noticed at 3 a.m. when it points to infrastructure that no longer exists. This recipe finds runbooks that have not kept up with the services they describe and proposes updates based on recent service changes.
Audit service runbooks for freshness and operational drift. Goal: Help me find runbooks that are likely out of date so I can fix them before they fail during a real incident. Ask me for: - The Google Drive folder where runbooks live - Stale thresholds: days since last edit and minimum service activity - Which services to scope the audit to, if any - Whether to create Linear tickets for top stale runbooks Use available integrations this way: - Google Drive: list runbook docs, last edit date, and last editor - GitHub: pull commit and deploy activity for each service referenced in a runbook - PagerDuty: identify which services page most often (those runbooks need to be right) - Linear: create tickets for the highest-risk stale runbooks with proposed owners - Slack: post a summary to the team channel - Google Docs: write the audit report Output: 1. A ranked list of stale runbooks with last-edit date, last editor, and activity gap 2. For each stale runbook: a summary of what has changed in the service since the last edit 3. Suggested updates with diffs against the current runbook text where possible 4. Linear tickets for the top stale runbooks 5. A Slack summary for the team 6. The full audit report in Google Docs Rules: - Do not edit any runbook directly; produce proposed diffs only - Do not delete a runbook even if it appears unused - Cross-reference paging frequency before ranking; high-paging runbooks are higher priority - If a runbook references a deleted service, flag it for archive review, not deletion - Respect Drive permissions; do not surface runbooks I do not have access to
This recipe audits your runbook set for operational drift. It scans
Google Drive for runbook docs, compares them with recent GitHub
activity on the services they describe, and flags the docs most
likely to be wrong. The core signal is simple: the service changed,
but the runbook did not.
Hand off the pager without making the next engineer reconstruct the shift
On-call handoffs usually happen fast, right when context is easiest to lose. The next engineer starts their shift digging through incidents, deploys, noisy alerts, and half-finished Slack threads just to understand the current state. This recipe pulls the shift's PagerDuty incidents, deploy activity, Datadog alerts, and open Slack threads into a clean handoff brief the next on-call can use immediately.
Turn rough incident notes into a blameless postmortem with shippable follow-ups
Postmortems often start as rushed incident notes and stay messy until review time. This recipe takes a rough draft, removes blameful language, fills timeline gaps from PagerDuty and Slack, turns vague follow-ups into concrete Linear tickets, and schedules the review.
Stop audio drift by quarantining variable-frame-rate clips at ingest
Audio slowly drifts out of sync or randomly desyncs in your timeline when footage is variable frame rate — common with iPhone footage, screen recordings, and some OBS workflows. This recipe catches VFR clips at ingest, transcodes them to constant frame rate, and quarantines the originals so drift never reaches your edit.
Fix credit report errors without guesswork
Generate dispute letters, evidence checklists, and follow-up timelines to correct credit report mistakes. Covers bureaus, furnishers, and identity theft.