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 an exhaustive reference document for on-call handoffs but suffers from extreme verbosity and poor organization for Claude's context window. The templates are well-structured individually but should be split into separate files with a concise overview in the main skill. Much of the content (best practices, do's/don'ts, external links) is generic knowledge that wastes tokens without adding actionable value.
Suggestions
Reduce the main SKILL.md to a concise overview (~50 lines) with the core handoff workflow and link to separate template files (e.g., HANDOFF_TEMPLATE.md, INCIDENT_HANDOFF.md, QUICK_HANDOFF.md)
Remove generic advice sections (Do's/Don'ts, 'When to Use This Skill', external resource links) that Claude already knows or that don't provide actionable guidance
Add validation steps to the workflow: e.g., 'Incoming engineer confirms understanding by summarizing top 3 risks back to outgoing engineer' as a feedback loop
Trim template examples to show structure with minimal placeholder data rather than fully populated examples - Claude can fill in realistic details from context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~350+ lines. Much of the content is generic on-call advice that Claude already knows (e.g., 'Document everything', 'Escalate early', 'Alert fatigue is real'). The templates are heavily padded with example data that could be condensed significantly. The 'When to Use This Skill' section, best practices do's/don'ts, and external resource links add little value for Claude. | 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 content is descriptive templates with placeholder data rather than actionable instructions Claude can directly execute. | 2 / 3 |
Workflow Clarity | The handoff process has a clear sequence (write document → sync call → verify alerting) and checklists are provided. However, there are no validation checkpoints or feedback loops - no guidance on what to do if handoff quality is insufficient, if the incoming engineer identifies gaps, or how to verify the handoff was successful. The timing diagram is helpful but lacks error recovery. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with everything inline. Three full templates, multiple checklists, best practices, escalation guidelines, and meeting agendas are all in 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
47823e3
- 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.