on-call-handoff-patterns
Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use this skill when transitioning on-call responsibilities between engineers and ensuring the incoming responder has full situational awareness, when writing a shift summary that captures active incidents, ongoing investigations, and recent changes, when handing off mid-incident so a fresh engineer can take over the incident commander role without losing context, when onboarding a new engineer to the on-call rotation for the first time, or when auditing and improving the quality of existing handoff processes across teams.
71
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/incident-response/skills/on-call-handoff-patterns/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope around on-call shift handoffs, lists concrete actions and scenarios, and provides explicit trigger guidance with five well-differentiated use cases. The natural trigger terms are comprehensive and the niche is well-defined. The only minor note is that the description is somewhat long, but the detail is substantive rather than padded.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: context transfer, escalation procedures, documentation, shift summaries capturing active incidents/investigations/changes, mid-incident handoffs, onboarding new engineers, and auditing handoff processes. | 3 / 3 |
Completeness | Clearly answers both 'what' (master on-call shift handoffs with context transfer, escalation procedures, and documentation) and 'when' with an explicit 'Use this skill when...' clause listing five distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'on-call', 'shift handoff', 'incident commander', 'shift summary', 'active incidents', 'escalation', 'on-call rotation', 'handoff', 'onboarding', 'situational awareness'. These cover a wide range of natural phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a very clear niche around on-call shift handoffs specifically. The combination of on-call rotation, incident commander handoff, and shift summaries is highly distinctive and unlikely to conflict with general incident management or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a comprehensive but overly verbose handoff reference document that would benefit enormously from restructuring. The templates are detailed and realistic but should be extracted into separate files, with the main SKILL.md providing a concise overview and clear pointers. The content also explains many concepts Claude already understands (what handoff components are, why overlap matters) rather than focusing on the unique, non-obvious guidance.
Suggestions
Extract the three templates into separate files (e.g., SHIFT_HANDOFF.md, QUICK_HANDOFF.md, INCIDENT_HANDOFF.md) and reference them from a concise overview in SKILL.md
Remove explanatory content Claude already knows (e.g., the 'Core Concepts' table explaining what 'Active Incidents' and 'Recent Changes' mean) and focus on non-obvious patterns and constraints
Move the troubleshooting section out of Template 3's code block where it's incorrectly nested, and make it a top-level section
Add an explicit validation step in the workflow: 'Before marking handoff complete, verify every section has content or explicit "none" — do not skip sections'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines, mostly consisting of filled-out example templates with placeholder data. Much of this content (what a handoff is, what components matter, timing recommendations) is general knowledge Claude already possesses. The templates could be significantly condensed. | 1 / 3 |
Actionability | The templates are concrete and copy-paste ready, which is good. However, the skill is more of a reference document than actionable instructions for Claude—it describes what handoffs should contain rather than giving Claude specific steps to generate or evaluate handoffs. The bash commands in the quick reference section are a nice touch but are example-specific rather than universally applicable. | 2 / 3 |
Workflow Clarity | There is a handoff checklist and a timing diagram, and the troubleshooting section addresses failure modes. However, the workflow steps lack explicit validation checkpoints—there's no 'verify the document is complete before proceeding' gate built into the sequence, and the checklist is presented as a static template rather than an enforced workflow. The troubleshooting section is oddly embedded inside Template 3's markdown block. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of text with three full templates inlined. The templates (especially Template 1 at ~100+ lines) should be in separate referenced files. There are links to related skills at the bottom, but the core content desperately needs splitting into overview + referenced template files. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
27a7ed9
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.