CtrlK
BlogDocsLog inGet started
Tessl Logo

on-call-handoff-patterns

Effective patterns for on-call shift transitions, ensuring continuity, context transfer, and reliable incident response across shifts.

49

Quality

54%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/on-call-handoff-patterns/SKILL.md

The canonical home for this skill is on-call-handoff-patterns in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

60%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.

The body is highly actionable with concrete templates, commands, and checklists, but it is verbose and monolithic, inlining large blocks that belong in separate reference files. The single reference target does not exist.

Suggestions

Move the full templates (shift handoff, quick handoff, incident handoff) and command reference into separate files under references/, keeping SKILL.md as a concise overview with one-level-deep links.

Fix or remove the broken reference to 'resources/implementation-playbook.md' since no such file exists.

Trim the generic 'Instructions' filler ('Clarify goals', 'Apply relevant best practices') that adds no on-call-specific value.

DimensionReasoningScore

Conciseness

Mostly concrete templates and commands, but the 450+ line body inlines large template/checklist blocks and includes generic filler ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') that could be trimmed; not a 2 because it avoids explaining concepts Claude already knows.

3 / 5

Actionability

Provides concrete, copy-paste-ready commands (kubectl, psql, redis-cli) and detailed fill-in templates with specific examples; not a 5 because much of the guidance is template scaffolding the user must complete rather than fully executable end-to-end procedures.

4 / 5

Workflow Clarity

Clear sequences (handoff timing diagram, pre/during/post-shift checklists) with verification checkpoints ('Test alert received and acknowledged', 'Verify PagerDuty routing changed'); not a 5 because some escalation and handoff flows lack explicit error-recovery feedback loops.

4 / 5

Progressive Disclosure

Content that clearly belongs in separate reference files (full templates, command lists, checklists) is inlined monolithically, and the one body reference points to a nonexistent 'resources/implementation-playbook.md' with no bundle directory present; not a 3 because the sole reference is broken rather than merely unclear.

2 / 5

Total

13

/

20

Passed

Description

48%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.

The description identifies a clear domain and niche but stays at an abstract outcome level without concrete actions or an explicit 'Use when' trigger clause. It is distinguishable yet generic in phrasing.

Suggestions

Add concrete actions (e.g., 'write shift handoff documents, document ongoing investigations, establish rotation procedures') instead of abstract outcomes.

Append an explicit 'Use when...' clause with natural trigger phrases like 'on-call handoff', 'shift change', or 'rotation handoff'.

Include common synonyms (handoff, rotation, pager) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('on-call shift transitions') but the rest are abstract outcomes ('ensuring continuity, context transfer, and reliable incident response') rather than concrete actions; not a level 3 because it lists no concrete actions like writing handoff documents.

2 / 5

Completeness

Has a clear 'what' (patterns for on-call shift transitions) but no explicit 'Use when...' trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains the natural phrase 'on-call shift transitions' a user might say, but misses common synonyms and variations such as 'handoff', 'rotation', 'pager', or 'shift change'.

3 / 5

Distinctiveness Conflict Risk

'On-call shift transitions' is a fairly distinct niche with low overlap risk against unrelated skills; not a 5 because the description lacks concrete distinguishing triggers.

4 / 5

Total

12

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.