CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

A well-structured overview that pushes detail into a real, clearly signaled reference file and keeps troubleshooting concrete and scenario-driven. Main improvements are removing the description-duplicating 'When to Use' section and surfacing the key validation checkpoints inline.

Suggestions

Trim or merge the 'When to Use This Skill' bullet list, which restates the frontmatter description almost verbatim, into a single line.

Surface the incoming-engineer verification steps (confirm PagerDuty routing, receive the test alert) as an explicit checklist in the handoff workflow rather than leaving them only in references/details.md and a troubleshooting entry.

Name what each referenced template is for where cited in the body (e.g., link 'Template 2' and 'Template 3' to their headings) so readers can navigate to the right one without loading the whole file.

DimensionReasoningScore

Conciseness

Largely lean with no filler explaining concepts Claude already knows, but the 'When to Use This Skill' bullet list substantially duplicates the frontmatter description and could be trimmed or merged.

4 / 5

Actionability

Concrete, executable guidance throughout ('do not mark handoff complete until every section has at least one entry', 'outgoing engineer fires a test alert and confirms incoming engineer receives it in PagerDuty and Slack'), though some steps depend on pulling the referenced templates rather than being self-contained.

4 / 5

Workflow Clarity

The timing tree sequences the handoff steps and troubleshooting adds checkpoints (the checklist-as-gate, the test-alert verification), but several verification steps live only in references/details.md rather than being surfaced as explicit checkpoints in the workflow itself.

4 / 5

Progressive Disclosure

A clear overview body with a single, well-signaled, one-level-deep reference ('Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates.') — verified to exist and to contain the Templates 1–3 the body cites.

5 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 description: concrete capabilities, an explicit multi-scenario trigger clause, and a well-defined niche. Keyword coverage is good but could add synonyms like 'handover' and common tool names to maximize natural-term matching.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'context transfer, escalation procedures, and documentation' and 'writing a shift summary that captures active incidents, ongoing investigations, and recent changes' — but the opening 'Master on-call shift handoffs' is broader than the anchor-5 level of fully enumerated, comprehensive actions.

4 / 5

Completeness

Explicitly answers both what ('Master on-call shift handoffs with context transfer, escalation procedures, and documentation') and when, via a detailed 'Use this skill when…' clause covering transitioning, shift summaries, mid-incident handoffs, onboarding, and process auditing.

5 / 5

Trigger Term Quality

Strong natural phrases users would say ('on-call shift handoffs', 'shift summary', 'onboarding a new engineer to the on-call rotation', 'handing off mid-incident'), but misses common synonyms such as 'handover', 'shift change', or tool names like 'PagerDuty'.

4 / 5

Distinctiveness Conflict Risk

A clear on-call handoff niche with distinct triggers; even the incident-related trigger ('take over the incident commander role without losing context') is framed around handoff, so overlap with incident-runbook or postmortem skills is minimal.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

wshobson/agents

Path

plugins/incident-response/skills/on-call-handoff-patterns/SKILL.md

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.