Individual skill

on-call-handoff

Run clean on-call handoffs — shift transitions, knowledge transfer, runbook currency, and sustainable rotations.

skills/on-call-handoff/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
54
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

On-call handoffs are where context transfers between humans: what happened, what's fragile, what's pending. Done well, they prevent dropped incidents and repeated pages; done poorly, they cause both. This skill covers handoff rituals, documentation, runbook maintenance, and designing sustainable on-call rotations.


On-call handoffs transfer operational responsibility between engineers: what is happening, what to watch, what is fragile, and who to call.
Good handoffs prevent the 3am "I have no context" disaster; bad handoffs (or none) turn every incident into an archaeological expedition.
This skill covers handoff rituals, documentation, and shadowing for sustainable on-call.
## When to use

- Designing on-call rotations
- Creating handoff checklists
- Reducing repeat pages
- Improving runbook quality