Agent skill · operations · rmyndharis
on-call-handoff-patterns
Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call processes.
Why this skill is useful
Codifies best practices for on-call handoff procedures, reducing ambiguity in shift transitions.
What it needs
About 7k tokens when loaded. Last updated 2026-08-02. 1,255 stars on the source repository.
What this skill does
On-Call Handoff Patterns Effective patterns for on-call shift transitions, ensuring continuity, context transfer, and reliable incident response across shifts. Do not use this skill when The task is unrelated to on-call handoff patterns You need a different domain or tool outside this scope Instructions Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes. Provide actionable steps and verification. Use this skill when Transitioning on-call responsibilities Writing shift handoff summaries Documenting ongoing investigations Establishing on-call rotation procedures Improving handoff quality Onboarding new on-call engineers Core Concepts 1. Handoff Components Component Purpose ----------- --------- Active Incidents What's currently broken Ongoing Investigations Issues being debugged Recent Changes Deployments, configs Known Issues Workarounds in place Upcoming Events Maintenance, releases 2. Handoff Timing Templates Template 1: Shift Handoff Document bash Check service health kubectl get pods -A grep -v Running Recent deployments kubectl get events --sort-by='.lastTimestamp' tail -20 Database connections psql -c "SELECT count() FROM pgstatactivity;" Clear cache (emergency only) redis-cli FLUSHDB Template 2: Quick Handoff (Async) Template 3: Incident Handoff (Mid-Incident) Handoff Sync Meeting Agenda (15 minutes) On-Call Best Practices Before Your Shift During Your Shift After Your Shift Escalation Guidelines When to Escalate Best Practices Do's Document everything - Future you will thank you Escalate early - Better safe than sorry Take breaks - Alert fatigue is real Keep handoffs synchronous - Async loses context Test your setup - Before incidents, not during Don'ts Don't skip handoffs - Context loss causes incidents Don't hero - Escalate when needed Don't ignore alerts - Even if they seem minor Don't work sick - Swap shifts instead Don't disappear - Stay reachable during shift Resources Google SRE - Being On-Call PagerDut …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills rmyndharis/on-call-handoff-patterns