CtrlK
BlogDocsLog inGet started
Tessl Logo

medical-soap-note-creation

Transform unstructured clinical encounters into comprehensive SOAP notes with ICD codes and care plans

59

Quality

67%

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 ./benchmarks/gdpval/skills/medical-soap-note-creation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is actionable and well-sequenced with a verification checklist, but it is somewhat verbose and keeps reference-grade material inline rather than splitting it into one-level-deep bundle files.

Suggestions

Trim the Overview's explanation of the four SOAP sections and the duplicated Example Structure, or move the example template into a separate reference file to reduce redundancy.

Split the ICD-10 code category list into a references file (e.g., references/icd-categories.md) and link to it from the body, improving progressive disclosure.

Tighten the 'Notes on Efficiency' section, which restates the single-write rationale already covered in Step 3 and Best Practices.

DimensionReasoningScore

Conciseness

Mostly efficient, but the Overview explains the four SOAP sections (concepts Claude already knows) and the lengthy 'Example Structure' duplicates much of the Step 2 outline, so it could be tightened.

2 / 3

Actionability

It provides a concrete 4-step process, a fill-in write_file code template, a detailed copy-paste-ready note template, and real ICD-10 code examples — specific and actionable guidance.

3 / 3

Workflow Clarity

Steps 1–4 are clearly sequenced with an explicit Step 4 quality checklist as a validation checkpoint; the task is non-destructive, so a hard validate→retry loop is not required.

3 / 3

Progressive Disclosure

Content is well-sectioned with headers, but at ~175 lines it keeps reference material (ICD-10 categories, the long example template) inline with no separate reference files, so content that should be split remains in the body.

2 / 3

Total

10

/

12

Passed

Description

57%

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 concrete and occupies a distinct clinical niche, but it omits any explicit 'when to use' trigger guidance and lacks common trigger-term variations, leaving the 'what' clear while the 'when' is only implied.

Suggestions

Add an explicit 'Use when...' clause naming when Claude should invoke this skill (e.g., when the user asks to write a SOAP note, progress note, or chart note from a clinical encounter).

Broaden trigger terms to include natural variations users say, such as 'progress note', 'chart note', 'clinical documentation', or 'EHR note'.

Consider framing the capability as multiple concrete actions (extract encounter info, assign ICD-10 codes, draft the care plan) to lift specificity toward the score-3 anchor.

DimensionReasoningScore

Specificity

Names the domain and a concrete transformation ('Transform unstructured clinical encounters into comprehensive SOAP notes'), but it is a single action with two output features (ICD codes, care plans) rather than the multiple distinct concrete actions exemplified by the score-3 anchor.

2 / 3

Completeness

It clearly answers 'what' the skill does, but 'when' is absent — there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Relevant natural terms appear ('SOAP notes', 'ICD codes', 'care plans'), but common variations a user might say (progress note, chart note, clinical documentation, EHR note) are missing.

2 / 3

Distinctiveness Conflict Risk

'SOAP notes with ICD codes and care plans' is a clearly distinct medical-documentation niche with domain-specific triggers, unlikely to conflict with non-clinical skills.

3 / 3

Total

9

/

12

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
HKUDS/OpenSpace
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.