CtrlK
BlogDocsLog inGet started
Tessl Logo

clinical-case-report

Structured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds", "case summary", or "patient presentation".

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

The body is a well-sequenced, actionable workflow with explicit self-check validation and clean progressive disclosure into two real reference files. It could be marginally tighter by not restating format structure that already lives in case-formats.md, and a full HTML template would push actionability higher.

Suggestions

Trim the duplicated format structure in 'What you will produce' since references/case-formats.md already covers SOAP/Conference/Brief Rounds in full, keeping the body to a pointer plus the workflow-specific deltas.

Add a minimal complete index.html scaffold (headings + data-od-id sections + a callout box + @media print block) so the HTML step is fully copy-paste ready rather than described as requirements.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (no basic explanations of SOAP or pharmacology), with minor redundancy: the format breakdown appears both in the body's "What you will produce" and again in references/case-formats.md.

4 / 5

Actionability

Provides concrete templates (the HPI fill-in narrative), a specific dosing example ("Piperacillin-Tazobactam 4.5g IV q8h for 5 days"), and an HTML section snippet with data-od-id tags, though no complete copy-paste HTML scaffold is given.

4 / 5

Workflow Clarity

Clear 8-step sequence (Step 0–7) with an explicit validation checkpoint at Step 7 ("run every P0 item... All P0 items must pass. Fix any failures before emitting") forming a validate-fix-retry feedback loop.

5 / 5

Progressive Disclosure

SKILL.md is an overview that signals two real one-level-deep references (references/case-formats.md, references/checklist.md) by path with clear purpose; detail is appropriately offloaded rather than nested.

5 / 5

Total

18

/

20

Passed

Description

95%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 is concise, uses correct third-person voice, and cleanly covers both capability and trigger conditions with natural clinical keywords. Minor room to enumerate a few more discrete output actions for maximal specificity.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans"), but the action list is slightly less granular than the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what (structured medical case presentation generating SOAP/narrative reports with vitals, labs, plans) and when ("Use when the brief mentions...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases ("case report", "case presentation", "SOAP note", "clinical case", "ward rounds", "case summary", "patient presentation") covering synonyms a clinician would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear clinical-case-report niche with distinct, domain-specific triggers; minimal risk of overlapping with unrelated skills.

5 / 5

Total

19

/

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
nexu-io/open-design
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.