Automated summary
This skill provides templates and procedures for effective on-call shift handoffs, ensuring continuity and context transfer between engineers.
Strengths
- Ensures information continuity between on-call teams
- Provides structured templates for various scenarios (end-of-shift, mid-incident)
- Includes checklists for both outgoing and incoming engineers
Limitations
- Requires team discipline to be applied consistently
- Can become cumbersome if too much documentation is expected
- Does not replace direct communication during urgent situations
Use this skill when preparing or performing an on-call shift transition, especially to document ongoing incidents and items to watch.
Do not use it if your team does not have an on-call rotation or if the handoff process is already informal and effective.
Security analysis
SafeThe skill purely provides documentation and workflow guidance for on-call handoffs. It does not instruct any code execution, system access, or data handling that could pose a security risk.
No concerns found
How this analysis is madeExamples
Create a shift handoff document for the outgoing on-call engineer. Include sections for ongoing incidents, recent changes, and items to watch. Use the template for a standard shift end.Generate a quick async handoff summary for the incoming on-call engineer. Include current alerts, any active investigations, and key links.We have a critical incident in progress (payment service outage). Create a mid-incident handoff document so a new engineer can take over. Include current status, actions taken, and next steps.version: 4.1.0-fractal name: on-call-handoff-patterns description: 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.
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.
- If detailed examples are required, open
resources/implementation-playbook.md.
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
🧠 Knowledge Modules (Fractal Skills)
1. 1. Handoff Components
2. 2. Handoff Timing
3. Template 1: Shift Handoff Document
4. None currently active
5. 1. Intermittent API Timeouts (ENG-1234)
6. 2. Memory Growth in Auth Service (ENG-1235)
7. Payment Service Outage (2024-01-19)
8. Deployments
9. Configuration Changes
10. Infrastructure
11. 1. Slow Dashboard Loading
12. 2. Flaky Integration Test
13. Common Commands
14. Important Links
15. Outgoing Engineer
16. Incoming Engineer
17. Template 2: Quick Handoff (Async)
18. Template 3: Incident Handoff (Mid-Incident)
19. Agenda (15 minutes)
20. Before Your Shift
21. Access Verification
22. Alerting Setup
23. Knowledge Refresh
24. Environment Ready
25. During Your Shift
26. Morning (start of day)
27. Throughout Day
28. End of Day
29. After Your Shift
30. When to Escalate
31. Immediate Escalation
32. Consider Escalation
33. How to Escalate
34. Do's
35. Don'ts
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/on-call-handoff-patterns-mmbizkx1/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/on-call-handoff-patterns-mmbizkx1' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/on-call-handoff-patterns-mmbizkx1/download' --output '.skill-downloads/on-call-handoff-patterns-mmbizkx1/SKILL.md.part' && mv '.skill-downloads/on-call-handoff-patterns-mmbizkx1/SKILL.md.part' '.skill-downloads/on-call-handoff-patterns-mmbizkx1/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/on-call-handoff-patterns-mmbizkx1/SKILL.md' && test -s '.skill-downloads/on-call-handoff-patterns-mmbizkx1/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/on-call-handoff-patterns' && cp -R '.skill-downloads/on-call-handoff-patterns-mmbizkx1' '.claude/skills/on-call-handoff-patterns'Cursor
test -f '.skill-downloads/on-call-handoff-patterns-mmbizkx1/SKILL.md' && test -s '.skill-downloads/on-call-handoff-patterns-mmbizkx1/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/on-call-handoff-patterns' && cp -R '.skill-downloads/on-call-handoff-patterns-mmbizkx1' '.cursor/skills/on-call-handoff-patterns'Codex
test -f '.skill-downloads/on-call-handoff-patterns-mmbizkx1/SKILL.md' && test -s '.skill-downloads/on-call-handoff-patterns-mmbizkx1/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/on-call-handoff-patterns' && cp -R '.skill-downloads/on-call-handoff-patterns-mmbizkx1' '.agents/skills/on-call-handoff-patterns'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/on-call-handoff-patterns-mmbizkx1'openskills read 'on-call-handoff-patterns-mmbizkx1'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/on-call-handoff-patterns-mmbizkx1/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.