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 description that clearly defines a specific domain (on-call shift handoffs), lists concrete actions, and provides extensive explicit trigger scenarios. It uses proper third-person voice and includes natural keywords that engineers would use when needing this skill. The five 'when' clauses are particularly effective at disambiguating this skill from related but different skills.
| 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' (on-call shift handoffs with context transfer, escalation procedures, documentation) and 'when' with 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', 'onboarding', 'handoff processes'. 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 an extensive collection of handoff templates but suffers from extreme verbosity—most of the content is filled-out example data that inflates token usage without adding proportional value. The structural organization is poor, with Template 1 consuming the majority of the file and troubleshooting content accidentally embedded inside Template 3. The skill would benefit greatly from condensing templates into separate files and adding clear instructions for Claude on how and when to apply each template.
Suggestions
Move the three full templates into separate referenced files (e.g., SHIFT_HANDOFF.md, QUICK_HANDOFF.md, INCIDENT_HANDOFF.md) and keep only a brief overview with links in SKILL.md.
Add explicit instructions for Claude at the top: what to do when a user asks for a handoff document (e.g., 'Ask the user for active incidents, recent changes, and ongoing investigations, then populate the appropriate template').
Fix the structural issue where troubleshooting content is embedded inside Template 3's code block—extract it to its own top-level section.
Condense the templates to show structure/skeleton only rather than fully filled-out examples with placeholder data, reducing token usage by 50%+.
| 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 doesn't clearly tell Claude what to *do* (e.g., 'when asked to write a handoff, use this template and fill in based on the user's context'). The bash commands in the quick reference are executable but context-specific placeholders. | 2 / 3 |
Workflow Clarity | The handoff timing section provides a basic sequence, and checklists exist for outgoing/incoming engineers. However, there are no explicit validation checkpoints (e.g., 'verify the document is complete before proceeding'). The troubleshooting section is oddly embedded inside Template 3's markdown block, creating confusion about document structure. The incomplete handoff gate is mentioned in troubleshooting but not in the actual workflow. | 2 / 3 |
Progressive Disclosure | The content 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. The troubleshooting section is incorrectly nested inside Template 3's code block. There are references to related skills at the end but no structured navigation for the bulk of the content. | 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
91fe43e
- 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.