CtrlK
BlogDocsLog inGet started
Tessl Logo

shift-handover-summarizer

Generate structured shift handover summaries from EHR records, highlighting critical events, vital sign changes, and pending tasks for incoming clinical staff.

61

Quality

77%

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 ./scientific-skills/Other/shift-handover-summarizer/SKILL.md
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, actionable skill body with executable commands, explicit validation checkpoints, and an appropriately split bundle (overview in SKILL.md, logic in scripts/main.py). Main weaknesses are an undefined 'manual extraction path' referenced twice but never described, and some duplicated/overlapping scope-and-error-handling text that could be tightened.

Suggestions

Define the manual fallback path that Workflow step 4 and Error Handling both reference — either describe the manual extraction steps or point to a concrete section/script.

Deduplicate the repeated missing-inputs sentence ('state exactly which fields are missing and request only the minimum additional information') and consolidate the overlapping scope guidance across When to Use, Scope Boundaries, and Input Validation.

Add a brief example of the expected output structure (e.g., a sample summary.json snippet) so the deliverable format is as concrete as the input handling.

DimensionReasoningScore

Conciseness

The body is dense and operational with no explanations of concepts Claude already knows, but 'state exactly which fields are missing and request only the minimum additional information' appears verbatim in both Workflow and Error Handling, and Input Validation, Scope Boundaries, and When to Use overlap in content — minor trim candidates matching anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Provides executable, copy-paste-ready guidance (usage command with concrete arguments, Quick Check commands, parameter table, priority-level table, exact warning message and refusal template), but Workflow step 4's 'apply the manual extraction path' and Error Handling's 'provide a manual fallback' reference a fallback path that is never actually defined — a minor gap keeping it below anchor 5.

4 / 5

Workflow Clarity

The numbered 6-step workflow includes explicit validation checkpoints (records within the declared shift range, a timezone-offset check with the exact warning text) and error-recovery guidance with checklist-style Response Template blocks; however, the referenced manual fallback path is left undefined, leaving a minor checkpoint gap relative to anchor 5. The skill is read/summarize-only, so the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

The bundle is appropriately split: SKILL.md is a ~110-line overview and usage guide, while the implementation lives in scripts/main.py, which exists and is referenced by valid paths one level deep with no nested or broken references; sections are well-organized with clear headers and nothing that belongs in a separate reference file is inlined.

5 / 5

Total

17

/

20

Passed

Description

66%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 specific, third-person description with a clear niche and concrete actions, but it is missing any 'Use when...' trigger clause, capping completeness, and it lacks common synonyms (handoff, sign-out) that users would naturally say. It also omits the priority-ranking capability present in the skill body.

Suggestions

Add an explicit trigger clause, e.g. 'Use when generating end-of-shift handover summaries or nursing handoff reports from EHR records at shift change.'

Include natural synonyms users would say — 'handoff', 'sign-out', 'end-of-shift report', 'change-of-shift' — to improve trigger term coverage and distinctiveness.

Mention the patient priority ranking by event severity, a core documented capability currently absent from the description.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('Generate structured shift handover summaries', 'highlighting critical events, vital sign changes, and pending tasks') with a clear domain (EHR records), but omits the patient priority-ranking capability documented in the skill body — a minor coverage gap matching the anchor 'Lists several specific actions; minor gaps in coverage' rather than the comprehensive anchor 5.

4 / 5

Completeness

It clearly answers 'what' ('Generate structured shift handover summaries from EHR records, highlighting critical events, vital sign changes, and pending tasks') but contains no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric caps at 3 ('Has a clear what but when is missing or only weakly implied').

3 / 5

Trigger Term Quality

Good natural keyword coverage ('shift handover', 'EHR records', 'critical events', 'vital sign changes', 'pending tasks', 'clinical staff'), but common variations users would naturally say — 'handoff', 'sign-out', 'end-of-shift report', 'SBAR' — are missing, fitting anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The clinical shift-handover niche is specific and mostly distinct ('structured shift handover summaries from EHR records... for incoming clinical staff'), with only minor overlap risk against general clinical-summarization or EHR-analysis skills; anchor 5 would require distinct trigger phrases that fully separate it from adjacent skills, which it lacks.

4 / 5

Total

15

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
aipoch/medical-research-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.