# Create Reliable On-Call Handoffs

Incomplete handoffs cause lost context and slower incident response. This skill provides structured templates, checklists, and escalation guidance for smooth shift transitions.

## Install

```bash
npx skillstore add sickn33/on-call-handoff-patterns
```

## Metadata

- Status: approved
- Slug: sickn33-on-call-handoff-patterns
- Skillstore revision: r2
- Version status: missing
- Tree hash: 1669d47beb3c939e5ae41f021a36ff8d6868fcf63c79f6387c29561c7f800caf
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/on-call-handoff-patterns
- Ref: 81e05e636292629114b76cbb3922fbe57672fc02
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/sickn33-on-call-handoff-patterns
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-on-call-handoff-patterns/manifest

## Capabilities

- Creates detailed shift handoffs covering incidents, investigations, changes, known issues, and upcoming events.
- Produces concise asynchronous handoffs for routine shift changes.
- Structures mid-incident transfers with status, impact, mitigation, ownership, and next steps.
- Provides outgoing, incoming, pre-shift, daily, and post-shift checklists.
- Defines handoff meeting agendas and escalation triggers.
- Suggests a timed overlap process for outgoing and incoming engineers.

## Use Cases

- Prepare a Weekly Shift Handoff: Turn current incidents, recent changes, and scheduled events into a complete transition document.
- Transfer an Active Incident: Summarize current impact, mitigation progress, technical findings, ownership, and immediate next actions.
- Standardize Team Handoffs: Create shared checklists, meeting agendas, escalation criteria, and documentation expectations for an on-call rotation.

## Prompt Templates

### Create a Basic Handoff

```
Create an on-call handoff from these notes: [notes]. Separate active incidents, investigations, recent changes, known issues, and upcoming events.
```

### Write a Quick Async Handoff

```
Create a concise asynchronous handoff from [notes]. Include a summary, watch list, recent changes, upcoming events, and clear owners.
```

### Transfer an Active Incident

```
Prepare a mid-incident handoff using [incident details]. Include impact, current state, evidence, completed actions, next steps, owners, and escalation conditions.
```

### Design a Team Handoff Process

```
Design an on-call handoff process for [team context]. Define timing, required sections, verification checks, escalation criteria, ownership, and quality controls.
```

## Limitations

- It does not connect to monitoring, paging, chat, ticketing, or deployment systems.
- Example links, names, dates, services, and incident identifiers are placeholders.
- Teams must adapt severity rules, escalation paths, access checks, and response targets.
- Operational commands require independent validation, authorization, and environment-specific safeguards.

## Best Practices

- Use precise timestamps, owners, impact statements, and next actions.
- Confirm access, alert routing, and understanding before the outgoing engineer leaves.
- Link each investigation to current evidence, decisions, dashboards, runbooks, and tickets.

## Anti Patterns

- Do not report status without naming an owner and next action.
- Do not copy stale links, contacts, thresholds, or incident details into a new handoff.
- Do not run example operational commands without authorization and environment validation.

## Security Audit

- Audited at: 2026-08-04T16:46:28.11\+00:00
- Summary: All 37 static alerts are false positives caused by Markdown formatting, example links, or ordinary prose. A separate semantic review found one destructive Redis command presented without sufficient execution safeguards.

## Stats

- Views: 107
- Downloads: 10
- Favorites: 0
- Popularity score: 0