on-call-handoff

Structures on-call rotation handoffs with a fixed template covering incidents, risks, and access checks.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Nandansai08/skillz --skill on-call-handoff-nandansai08
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: on-call-handoff
Source: https://github.com/Nandansai08/skillz/tree/main/skills/sre-incident-response/on-call-handoff
Command: npx skills add https://github.com/Nandansai08/skillz --skill on-call-handoff-nandansai08

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? On-call shift changes lose critical context: untracked follow-ups, silences with no expiry, and rotted access credentials surface as surprises during the next incident. This Skill turns handoff from an informal chat into a verifiable transfer of operational state. ## Core Features & Use Cases - Fixed handoff template: Captures open incidents, smoldering risks, recent changes, alert weather, and owed follow-ups in the same five sections every rotation. - Explicit ownership transfer: Every open item is marked transferred, retained, or parked so nothing falls between shifts. - Access verification ritual: Test pages, VPN, kubeconfig, dashboard, and escalation contact checks catch access rot on handoff day instead of incident day. - Use Case: An engineer ending a week-long rotation writes the templated note, walks the incoming on-call through it synchronously, sends a test page, and escalates a three-week recurring vendor issue into a ticket. ## Quick Start Use the on-call-handoff skill to write my end-of-rotation handoff note covering open incidents, risks, and follow-ups.

Frequently Asked Questions about on-call-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an on-call handoff note?▼

Use a fixed template with five sections: open incidents, smoldering risks, recent changes, alert weather, and follow-ups owed. Rank items by likelihood of paging, include what has been tried and ruled out for each open item, and mark empty sections as none.

What should an on-call handoff include?▼

Include open incidents with state and next action, risks not yet incidents, recent deploys still soaking, noisy alerts and active silences with expiry, and owed follow-ups. Each open item needs an explicit transferred, retained, or parked state.

Is on-call handoff the same as mid-incident IC transfer?▼

No. Mid-incident incident commander transfer is a live role handoff inside incident-triage: announce, brief on the timeline, confirm acceptance. On-call handoff is the scheduled rotation change covering the full operational picture.

Why do on-call handoffs fail between shifts?▼

Handoffs fail when they are verbal-only, skipped on quiet weeks, or omit active silences and access verification. Facts transfer without hypothesis state, so the incoming person repeats eliminated troubleshooting steps during the next incident.

How do I verify access before taking over on-call?▼

Send a test page on rotation change, then confirm VPN, kubeconfig, dashboard logins, and escalation contacts during the synchronous walkthrough. Tokens and SSO lapse between rotations, so check on handoff day rather than during an outage.