CtrlK
BlogDocsLog inGet started
Tessl Logo

create-soap-note

Generate structured medical SOAP notes with all required sections in a single comprehensive file write.

52

Quality

57%

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/create-soap-note/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 a clean, well-structured single-purpose skill with a useful template, but it lacks an explicit validation checkpoint for the file write and its guidance is structural rather than executable, capping workflow clarity and actionability.

Suggestions

Add an explicit validation checkpoint after the file write — e.g., 'Verify all four headers (## Subjective, ## Objective, ## Assessment, ## Plan) are present and non-empty; if any is empty, fill with the agreed "not applicable/deferred" marker before finalizing.'

Include one fully filled example section (e.g., a sample Subjective block with CC/HPI) so Claude has a copy-paste-ready pattern rather than only a placeholder template.

Tighten the Objective and Prerequisites prose to bullet-only form to remove the remaining minor verbosity.

DimensionReasoningScore

Conciseness

The body is well-organized and largely free of padding, defining each SOAP section concisely without explaining concepts Claude already knows; only minor boilerplate (Objective/Prerequisites prose) could be trimmed.

4 / 5

Actionability

It provides a concrete template and per-section item lists, but the guidance stays at the structural level — there is no executable command, no sample filled section, and the steps are instructions rather than copy-paste-ready artifacts.

3 / 5

Workflow Clarity

Four numbered steps are sequenced and a completeness review is mentioned, but the file-write operation is a batch/destructive-ish action with no validation checkpoint (e.g., verify headers present before finalizing), which the rubric caps at 3.

3 / 5

Progressive Disclosure

The ~90-line single-purpose skill is organized into clear sections (Objective, Prerequisites, Workflow, Template, Best Practices, Troubleshooting) with no nested references and no bundle files needed, fitting the simple-skill exception well.

4 / 5

Total

14

/

20

Passed

Description

53%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 clearly states what the skill does and targets a distinct niche, but it omits any 'Use when...' trigger guidance and lacks keyword synonyms, leaving it at the midpoint across most dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to write a SOAP note, medical visit note, or clinical documentation with Subjective/Objective/Assessment/Plan sections.'

Broaden trigger keywords with natural synonyms and file extensions such as 'SOAP note', 'medical documentation', 'clinical note', '.md', and '.txt'.

Mention a second concrete action (e.g., populating each section from provided vitals, history, and exam data) to lift specificity above a single action.

DimensionReasoningScore

Specificity

It names the domain (medical SOAP notes) and a concrete action (generate structured notes with all required sections in a single file write), but stops at one action and is not comprehensive across multiple concrete capabilities.

3 / 5

Completeness

The 'what' is clearly stated (generate structured SOAP notes), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

It surfaces the relevant keyword 'SOAP notes' that users would naturally say, but offers no synonyms, file extensions, or common variations like 'medical documentation' or 'visit note'.

3 / 5

Distinctiveness Conflict Risk

The SOAP-note niche is fairly distinct with minimal overlap risk against generic document skills, though the single-action phrasing leaves slight ambiguity versus a broader medical-documentation skill.

4 / 5

Total

13

/

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