on-call-handoff-patterns
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.
72
58%
Does it follow best practices?
Impact
95%
1.53xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/incident-response/skills/on-call-handoff-patterns/SKILL.mdQuality
Discovery
89%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 solid skill description that clearly defines its niche around on-call shift handoffs and provides explicit 'Use when' triggers. The main weakness is that the capability descriptions lean slightly abstract ('context transfer', 'escalation procedures') rather than listing highly concrete actions. Overall it performs well for skill selection purposes.
Suggestions
Make capabilities more concrete by listing specific actions, e.g., 'generate shift summary reports, create escalation runbooks, compile incident timelines' instead of abstract nouns like 'context transfer'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (on-call shift handoffs) and mentions some actions (context transfer, escalation procedures, documentation), but these are somewhat abstract rather than concrete specific actions like 'generate shift summary reports' or 'create escalation checklists'. | 2 / 3 |
Completeness | Clearly answers both what ('context transfer, escalation procedures, and documentation') and when ('Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call processes') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'on-call', 'shift handoffs', 'context transfer', 'escalation procedures', 'shift summaries', 'on-call processes'. These cover the key vocabulary someone dealing with on-call transitions would use. | 3 / 3 |
Distinctiveness Conflict Risk | On-call shift handoffs is a very specific niche that is unlikely to conflict with other skills. The combination of 'on-call', 'shift handoffs', and 'escalation procedures' creates a distinct trigger profile. | 3 / 3 |
Total | 11 / 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 excessively verbose collection of on-call handoff templates and checklists. While the templates themselves are well-structured and realistic, the skill suffers from being a monolithic document that explains many concepts Claude already understands. It would benefit significantly from splitting templates into separate files and trimming generic advice.
Suggestions
Split the three handoff templates into separate referenced files (e.g., SHIFT_HANDOFF.md, QUICK_HANDOFF.md, INCIDENT_HANDOFF.md) and keep SKILL.md as a concise overview with navigation links.
Remove generic on-call advice sections (Do's/Don'ts, 'Document everything', 'Take breaks') that Claude already knows - focus only on the structural patterns and templates.
Add validation steps to the workflow: e.g., 'Verify incoming engineer has confirmed receipt and understanding before considering handoff complete' as an explicit checkpoint.
Trim the Core Concepts table and explanatory text - the templates themselves demonstrate the components; the table explaining 'Active Incidents = What's currently broken' is redundant.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Much of the content is generic on-call advice that Claude already knows (e.g., 'Document everything', 'Escalate early', 'Take breaks'). The templates are exhaustive but filled with placeholder data that inflates token count without adding instructional value. The 'Core Concepts' table explains obvious things like 'Active Incidents = What's currently broken'. | 1 / 3 |
Actionability | The templates are concrete and copy-paste ready, which is good. However, the skill is primarily a collection of markdown templates rather than executable code or commands. The bash commands in the quick reference section are useful but most of the content is descriptive documentation patterns rather than specific instructions Claude can act on programmatically. | 2 / 3 |
Workflow Clarity | The handoff timing diagram and checklists provide a clear sequence, and the sync meeting agenda has time allocations. However, there are no validation checkpoints or feedback loops - no guidance on what to do if the handoff document is incomplete, if access verification fails, or how to verify the handoff was successful. For a process involving responsibility transfer (a risky operation), this is a gap. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with everything inline. Three full templates, multiple checklists, best practices, escalation guidelines, and external resources are all crammed into a single file. The templates alone could each be separate referenced files, with the main skill providing a concise overview and navigation to each template. | 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
- Dicklesworthstone/pi_agent_rust
- Commit
6e3d68c
- 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.