medical-soap-note-creation

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

67%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 skill delivers a clear, actionable, well-sequenced workflow for SOAP note generation with concrete examples and a useful ICD-10 reference. Its main weakness is padding (the SOAP acronym definition and the efficiency rationale) that assumes too little of Claude's knowledge.

Suggestions

Remove the "Notes on Efficiency" section and the SOAP acronym expansion in the Overview; Claude already knows these, and the single-write guidance is already stated in Step 3 and Best Practices.

Tighten the Step 3 code template by replacing placeholder strings with a brief note that fields should be filled from extracted data, reducing template clutter.

Consider moving the "Common ICD-10 Code Categories" list into a separate references file if the list grows, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but includes unnecessary explanation Claude already knows, such as the Overview defining the SOAP acronym and the "Notes on Efficiency" section justifying the single write_file call, which pads the token budget.	3 / 5
Actionability	Concrete step-by-step extraction lists, an executable write_file code template, and a detailed worked example structure with ICD-10 codes provide mostly executable guidance, with only minor gaps from placeholder tokens like [Encounter Date].	4 / 5
Workflow Clarity	A clear four-step sequence (Extract, Structure, Write, Quality Checklist) with an explicit verification checklist gives a solid workflow, though there is no validate-and-retry feedback loop; this is acceptable since document generation is neither destructive nor batch.	4 / 5
Progressive Disclosure	Content is organized into well-labeled sections (Overview, Steps, Best Practices, Example Structure, ICD categories) with no external references needed; the inlined ICD-10 category list is compact enough to remain inline, leaving only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

61%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 specific and distinct within the clinical-documentation niche but omits any explicit usage trigger, capping completeness. Adding a "Use when..." clause referencing clinical encounters, charting, or SOAP note requests would raise completeness and distinctiveness.

Suggestions

Add an explicit trigger clause such as "Use when transcribing clinical encounters, writing SOAP notes, or preparing EHR documentation with ICD-10 coding."

Include a couple of natural user synonyms (e.g., "charting", "clinical documentation", "EHR notes") to broaden trigger coverage.

Separate the single "Transform...into" action into distinct capabilities (e.g., "Structure encounters into SOAP sections, assign ICD-10 codes, draft care plans") to improve specificity.

Dimension	Reasoning	Score
Specificity	"Transform unstructured clinical encounters into comprehensive SOAP notes with ICD codes and care plans" names the domain plus a few concrete outputs (SOAP notes, ICD codes, care plans) but bundles them into a single transformation action rather than listing multiple distinct actions.	3 / 5
Completeness	The description clearly states what the skill does but lacks any "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	"SOAP notes", "ICD codes", and "care plans" are natural terms a clinical user would say, giving good keyword coverage, though a few common variations (e.g., charting, documentation, EHR) are absent.	4 / 5
Distinctiveness Conflict Risk	The medical SOAP-note niche with ICD coding is mostly distinct with minimal conflict risk, though the absence of explicit trigger phrases leaves minor overlap with general clinical-documentation skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: HKUDS/OpenSpace
Path: benchmarks/gdpval/skills/medical-soap-note-creation/SKILL.md
Commit: 3827781

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.