Generate an on-call handoff document from incidents, alerts, and notable events during a shift, ready for the next on-call to read in five minutes.
Generates a tight on-call handoff document covering the past shift: open incidents, recently-fired alerts (with current state), workarounds in place, deploys that landed, and unresolved questions. Designed to be readable in 5 minutes.
shift_start, shift_end: ISO timestamps.incident_source: pagerduty, opsgenie, or incident-io. Provide an API key in env.alert_source: prometheus, datadog, or cloudwatch.deploy_log: path to a deploys CSV with service, version, started_at, status.incidents?since=<start>&until=<end>. Capture id, status, title, urgency, last note./api/v2/alerts. Identify alerts that fired and resolved within the window vs alerts still firing.deploy_log. Filter to the window.oncall-handoff-<shift-end>.md.oncall-handoff-<shift-end>.md with the prioritized sections. Stdout prints incident count, active alert count, deploy count.
Cross-check the open-incident list against the source's UI directly to confirm counts. For each "active alert", re-query at the moment of doc generation; if it just resolved, move it to Recently Resolved. Time-to-read estimate: word count / 250 wpm; if over 5 minutes, condense by collapsing low-severity alerts into a "Quiet" section.
Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/oncall-handoff-doc-generator.
Read-only AWS surface — list/describe EC2, S3 buckets, IAM users, and Lambda functions. Auth via STS-assumed role; no mutating tools.
Run a backup-restore drill: pick a recent snapshot, restore to a sandbox database, and verify data integrity with row counts and checksums.
Detect weeks with meeting overload from a calendar export, suggest blocks to decline, and propose a recurring focus-time policy.
Read-only Cloudflare surface — list zones, DNS records, deployed Workers, and page rules. Auth via scoped API token; no mutating tools.
Identify imports and module-init code that contribute to Cloudflare Worker cold starts and propose lazy-load rewrites.
Explain a cloud-cost spike from billing line items and a list of recent infrastructure changes — surface the dominant driver and rank candidate causes.