CtrlK
BlogDocsLog inGet started
Tessl Logo

summarizing-clinical-notes

Produces structured, citation-anchored summaries of clinical notes — one-liner, hospital course, and problem-oriented views — where every claim cites a source span so nothing is hallucinated. Use after de-identifying notes when the user wants a discharge summary draft, handoff/SBAR, problem list, or chart-abstraction summary. De-identify FIRST with openmed.deidentify, then anchor summary claims to entity spans from openmed.analyze_text. Trigger keywords: summarize note, discharge summary, hospital course, problem-oriented, one-liner, SOAP, SBAR, handoff, chart abstraction.

75

Quality

92%

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

85%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 a clear validated workflow and good navigation. The main gaps are a slightly trimmable intro and a summary-composition example that stops at pseudocode.

Suggestions

Tighten the opening two paragraphs: keep one sentence on the faithfulness/hallucination rationale and fold the rest into the Workflow, since the Edge cases already restate the anti-hallucination gate.

Make the summary-composition example executable end-to-end — show a small runnable snippet that builds and emits one problem-oriented line with real cite() anchors, rather than leaving it as a comment.

In the Quick start, after the spans dict, add a 2–3 line runnable block producing an actual cited one-liner so a user can copy-paste and see the citation format immediately.

DimensionReasoningScore

Conciseness

Mostly lean with executable code and tight bullet sections, but the opening two motivational paragraphs about the hallucination failure mode could be trimmed without losing actionable guidance.

4 / 5

Actionability

Provides executable openmed.deidentify/analyze_text code and a cite() helper, but the actual summary-composition step is left as a comment/pseudocode example rather than runnable code, leaving a minor gap.

4 / 5

Workflow Clarity

Six-step sequence with explicit validation checkpoints — step 5 rejects/flags uncited sentences, step 6 requires human sign-off, and edge cases add a PHI leakage gate — so validation is present rather than absent.

5 / 5

Progressive Disclosure

Well-organized into clear sections with one-level-deep, clearly signaled references (See `resolving-clinical-context`, external standards URLs) and no nested references; content is appropriately self-contained with no bundle files needed.

5 / 5

Total

18

/

20

Passed

Description

100%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 high-quality description: third-person voice, concrete capabilities, explicit use-when guidance, and a comprehensive trigger-keyword list. It clearly distinguishes itself and names the upstream skills it depends on.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'one-liner, hospital course, and problem-oriented views', 'every claim cites a source span', de-identify, analyze_text — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' (structured, citation-anchored summaries of clinical notes) and 'when' ('Use after de-identifying notes when the user wants a discharge summary draft, handoff/SBAR…') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Explicit 'Trigger keywords' cover natural clinical synonyms a user would say: summarize note, discharge summary, SOAP, SBAR, handoff, chart abstraction, one-liner.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (clinical-note summarization with span citations) with distinct triggers and named companion skills, giving minimal overlap risk with other skills.

5 / 5

Total

20

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
maziyarpanahi/openmed
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.