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 identifies its niche (on-call shift handoffs) and provides explicit 'Use when' guidance with natural trigger terms. 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, build handoff checklists, and document incident context for incoming on-call engineers.'
| 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 keywords users would say: 'on-call', 'shift handoffs', 'escalation', 'shift summaries', 'on-call processes', 'transitioning on-call responsibilities'. These cover the natural language a user would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The on-call shift handoff domain is a clear niche with distinct triggers like 'on-call', 'shift handoffs', 'escalation procedures' that are unlikely to conflict with other skills. | 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 essentially a comprehensive on-call handbook dumped into a single file, resulting in extreme verbosity and poor progressive disclosure. While the templates themselves are well-structured and concrete, much of the content is generic operational advice that Claude already knows, and the sheer volume undermines usability. The skill would benefit enormously from splitting templates into separate files and trimming the body to essential, non-obvious guidance.
Suggestions
Extract 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 links.
Remove generic best practices Claude already knows (e.g., 'Take breaks', 'Don't work sick', 'Document everything') and focus only on non-obvious, organization-specific patterns.
Add explicit validation gates in the workflow, such as 'Verify incoming engineer confirms PagerDuty routing BEFORE outgoing engineer signs off' as a hard checkpoint.
Cut the external resource links (Google SRE book, PagerDuty guide) which are general references Claude already knows about, and replace with guidance on how to customize templates for a specific team's needs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Much of the content is general on-call best practices that Claude already knows (e.g., 'Don't work sick', 'Take breaks', 'Alert fatigue is real'). The templates are exhaustive with placeholder data that inflates token count significantly. The do's/don'ts and best practices sections are generic advice, not skill-specific instruction. | 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 few bash commands provided are useful but most content is descriptive checklists and tables rather than specific instructions for Claude to follow when performing a task. | 2 / 3 |
Workflow Clarity | The handoff timing section provides a clear sequence, and checklists are well-structured. However, there are no validation checkpoints or feedback loops - for example, no step to verify the handoff document is complete before the sync call, no mechanism to confirm the incoming engineer actually has access before the outgoing engineer goes off-call. The mid-incident handoff template has a confirmation checklist but it's not integrated into a workflow with explicit gates. | 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 resource links are all crammed into a single file. The templates alone could each be separate referenced files, with the SKILL.md serving as a concise overview pointing to them. | 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
b09ec7f
- 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.