CtrlK
BlogDocsLog inGet started
Tessl Logo

soap-note-creation

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

54

Quality

60%

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

Quality

Content

62%

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

The skill is well-structured with a clear workflow and verification step, but it is somewhat verbose and relies on placeholder templates rather than fully concrete examples. Consolidating the duplicate Required Sections / Example Structure and tightening restated domain knowledge would improve it.

Suggestions

Merge 'Required Sections' and the 'Example Structure' template into one authoritative section to remove duplication and reduce tokens.

Trim restated domain knowledge (e.g. the enumeration of HEENT/Cardiovascular/Respiratory exam systems, the OLDCARTS note) that Claude already knows.

Provide at least one fully worked SOAP note example with realistic values instead of only placeholder brackets to lift actionability.

DimensionReasoningScore

Conciseness

The body restates some domain knowledge Claude already knows (e.g. listing HEENT/Cardiovascular exam systems, defining OLDCARTS) and duplicates structure between 'Required Sections' and the full 'Example Structure' template, so it could be tightened despite being mostly efficient.

2 / 3

Actionability

A concrete execution pattern and a full markdown template are provided, but the template is placeholder-heavy ([Patient Name/ID], [value], [findings]) rather than copy-paste ready with worked specifics, matching the score-2 'some concrete guidance but incomplete' anchor.

2 / 3

Workflow Clarity

The 'Execution Pattern' gives a clear four-step sequence culminating in an explicit verification checkpoint ('Verify all four sections are present and complete'); for this simple single-write skill that checkpoint satisfies the workflow-clarity bar.

3 / 3

Progressive Disclosure

Sections are well-organized within a single file and no external references are needed, but the full Example Structure template is inline monolithic content that could be split out; the skill also exceeds the ~50-line simple-skill threshold that would otherwise justify a 3.

2 / 3

Total

9

/

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 states a clear, distinctive purpose but stops short of listing multiple concrete actions and provides no explicit 'Use when...' trigger guidance. Adding a trigger clause and a second concrete action would raise the weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating medical meeting notes, patient visit documentation, or clinical encounter records in SOAP format.'

List a second concrete action beyond 'create' (e.g. '...and verify all four sections are complete') to lift specificity toward the score-3 anchor.

Include common natural term variations like 'patient visit notes' or 'clinical encounter documentation' alongside 'SOAP notes'.

DimensionReasoningScore

Specificity

The phrase 'Create structured medical SOAP notes with all four components in a single comprehensive file write' names the domain and a single core action with modifiers, but does not list multiple distinct concrete actions like the score-3 anchor ('Extract text and tables... fill forms, merge documents').

2 / 3

Completeness

It clearly answers what the skill does, but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

'medical SOAP notes' is a natural term a clinician would say, but the description omits common variations such as 'patient visit', 'clinical encounter', or 'clinical notes' that appear only in the body.

2 / 3

Distinctiveness Conflict Risk

'structured medical SOAP notes with all four components' carves out a clear, narrow niche that is unlikely to trigger for or conflict with unrelated 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.