soap-note-creation

Create structured medical SOAP notes with all four components in a single comprehensive file write

Quality

64%

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/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 content is well-structured and actionable, with a clear sequenced workflow and a concrete template, but it carries noticeable redundancy between its section-enumeration blocks and lacks an explicit error-recovery loop. Splitting the large example template into a reference file would improve progressive disclosure.

Suggestions

Reduce redundancy: 'Required Sections' and 'Example Structure' both enumerate the four SOAP sections — collapse them or move the full template into a separate reference file.

Trim restated guidance: 'Best Practices' #1 and several 'Common Mistakes' restate the single-write 'Core Technique'; consolidate to earn tokens back.

Add one fully-worked example with real values to satisfy the 'Best Practices' guidance against using placeholders.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but 'Required Sections' and 'Example Structure' both fully enumerate the four SOAP sections, and 'Best Practices' #1 plus several 'Common Mistakes' restate the 'Core Technique', creating noticeable redundancy that could be tightened.	3 / 5
Actionability	A concrete fill-in markdown template plus specific required elements (vitals list, HEENT/system exam, OLDCARTS, ICD-coded diagnosis) give mostly executable guidance; the minor gap is the absence of a fully-worked example with real values, with only placeholders shown.	4 / 5
Workflow Clarity	The 'Execution Pattern' gives a clear 4-step sequence with an explicit verification step ('Verify all four sections are present and complete'); it stops short of a 5 because there is no feedback loop describing what to do if verification fails.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no external references are needed, but at roughly 120 lines (above the 50-line simple-skill threshold) the large inlined 'Example Structure' template could be split into a one-level-deep reference file.	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 states a clear, specific purpose but omits any 'Use when...' trigger guidance, which caps completeness and limits trigger-term coverage. It is distinct within a clear niche yet would benefit from explicit invocation triggers and synonym coverage.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when creating patient visit notes, clinical encounter documentation, or SOAP-format medical records') to answer when Claude should invoke the skill and lift completeness.

Include natural synonyms users might say (e.g., 'clinical notes', 'chart notes', 'encounter documentation') to broaden trigger-term coverage toward comprehensive.

Name a couple more concrete actions (e.g., 'structure, draft, and write') to raise specificity beyond a single stated action.

Dimension	Reasoning	Score
Specificity	Names the domain ('medical SOAP notes') and one main concrete action ('Create ... in a single comprehensive file write'), but does not list multiple distinct actions, matching the anchor that names domain plus 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It clearly states what the skill does ('Create structured medical SOAP notes with all four components in a single comprehensive file write') but provides no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	'medical SOAP notes' is a strong natural phrase a clinician would actually say, but the description lacks synonyms (e.g., 'clinical notes', 'chart notes', 'encounter documentation'), so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	The 'medical SOAP notes' niche is specific and mostly distinct from other skills, with only minor overlap risk against general note-taking or documentation skills; absence of explicit trigger phrasing keeps it just below a 5.	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/soap-note-creation/SKILL.md
Commit: 3827781

Reviewed: 7 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.