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.

1.53x

Quality

—

Does it follow best practices?

Impact

95%

1.53x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

42%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill offers genuinely useful, actionable handoff templates and commands but is far too verbose, padding the context window with generic on-call guidance Claude already knows and lacking any progressive-disclosure split across files.

Suggestions

Trim generic best-practice and checklist prose ('Take breaks', 'Don't hero', 'Document everything') that Claude already knows; keep only the specific handoff templates and commands.

Split the large templates into separate reference files under references/ (e.g. shift-handoff-template.md, incident-handoff-template.md) and link to them one level deep to satisfy progressive disclosure.

Add explicit validation/confirmation checkpoints to the handoff workflow (e.g. 'Incoming engineer confirms receipt and PagerDuty routing before outgoing logs off') to close the feedback loop on a context-transfer-critical operation.

Dimension	Reasoning	Score
Conciseness	The ~480-line body is heavily padded with verbose templates, checklists, and generic best-practice lists ('Document everything - Future you will thank you', 'Take breaks - Alert fatigue is real') that assume little of Claude's competence and explain routine on-call concepts Claude already knows.	1 / 3
Actionability	Provides concrete, copy-paste-ready templates and executable bash snippets ('kubectl get pods -A \| grep -v Running', 'psql -c "SELECT count(*) FROM pg_stat_activity;"'), but much guidance is generic checklist prose rather than specific executable instruction.	2.5 / 3
Workflow Clarity	Sequencing is present (handoff timing diagram, sync-meeting agenda, before/during/after-shift checklists), but there are no validation checkpoints or feedback loops verifying that a handoff was actually received and understood before proceeding.	2 / 3
Progressive Disclosure	Content is organized into sections but it is a monolithic single-file wall of templates and checklists with no bundle files (references/, scripts/, assets/ absent) and no offloading of the large reference material into separate files.	2 / 3
	Total	7.5 / 12 Passed

Description

95%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that clearly states both capability and trigger conditions in natural third-person voice, with good trigger-term coverage and a distinctive niche.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete facets ('context transfer, escalation procedures, and documentation') with action verbs ('Master', 'transitioning', 'documenting', 'improving'), though some are noun-like rather than fully concrete operations, falling between anchor 2 and 3.	2.5 / 3
Completeness	Explicitly answers both what ('Master on-call shift handoffs with context transfer, escalation procedures, and documentation') and when ('Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call processes'), matching the score-3 anchor exactly.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered: 'on-call shift handoffs', 'transitioning on-call responsibilities', 'shift summaries', 'on-call processes' — the kinds of phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The on-call handoff niche is narrow with distinct triggers unlikely to overlap with unrelated skills.	3 / 3
	Total	11.5 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Dicklesworthstone/pi_agent_rust
Commit: e9f9b67

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.