comprehensive-soap-note

Generate complete medical SOAP notes with all four sections in a single comprehensive file write operation

Quality

56%

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/create-soap-note-merged/SKILL.md

Quality

Content

60%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 template, verification step, and feedback loop, but it is notably verbose due to four trailing sections that redundantly restate the same guidance plus an unnecessary file-size reference. Consolidating the redundant sections would materially improve token efficiency.

Suggestions

Merge Best Practices, Common Mistakes, Troubleshooting, and the Quality Checklist into a single concise section — they currently restate 'include all sections, single write, no placeholders, mark missing as N/A' four times over.

Remove the 'Example File Size Reference' section; character-count ranges are not actionable guidance for generating a note.

Tighten the Required Sections detail and the Template Example, which overlap heavily — either reference one from the other or consolidate the field lists.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: Best Practices, Common Mistakes, Troubleshooting, and the Quality Checklist all restate the same handful of points (completeness, single write, no placeholders, mark missing as N/A), and the 'Example File Size Reference' section is non-actionable padding — several padded sections rather than just minor tightening.	2 / 5
Actionability	As an instruction-only skill it provides a concrete copy-paste markdown template, specific per-section element lists (OLDCARTS, ICD codes, named vitals), and a file-naming convention — mostly executable guidance with only the minor gap of no fully filled worked example.	4 / 5
Workflow Clarity	The Execution Pattern gives a clear 4-step sequence with an explicit verification step, supported by a Quality Checklist and a rewrite-if-incomplete feedback loop; it sits at 4 rather than 5 because the steps themselves ('Gather all patient information', 'Structure content') are somewhat high-level rather than command-level.	4 / 5
Progressive Disclosure	No bundle files exist, so all content lives in SKILL.md, which is organized into clear headed sections; structure is good with only minor organization gaps from the redundant trailing sections, fitting the 'good structure, minor gaps' anchor.	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 conveys what the skill does but omits any 'when to use it' trigger guidance, which caps completeness and limits trigger-term coverage. It is distinct within the medical-documentation niche yet would benefit from explicit use-case phrasing.

Suggestions

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

Include natural trigger synonyms such as 'clinical notes', 'patient encounter', and 'visit documentation' to broaden keyword coverage.

Optionally name additional concrete actions (e.g. 'include all four SOAP sections and apply the OLDCARTS framework') to lift specificity toward a 4.

Dimension	Reasoning	Score
Specificity	Names the domain ('medical SOAP notes') and a couple of concrete actions ('generate complete SOAP notes', 'single comprehensive file write operation'), but does not enumerate multiple distinct actions, so it is not comprehensive — matching the 1-2 concrete actions anchor rather than the several-actions anchor at 4.	3 / 5
Completeness	The 'what' is clearly stated ('Generate complete medical SOAP notes with all four sections in a single comprehensive file write operation'), but there is no 'Use when...' clause or equivalent trigger guidance — per the rubric this caps completeness at 3 even though the what is clear.	3 / 5
Trigger Term Quality	'medical SOAP notes' is a natural keyword a user would say, but the description omits common synonyms and variations such as 'clinical notes', 'patient encounter', 'visit documentation', or file extensions, leaving keyword coverage partial.	3 / 5
Distinctiveness Conflict Risk	The SOAP-note niche is clearly distinct from most skills with only minor overlap risk against general medical-note or documentation skills; it stops short of 5 because the description lacks an explicit distinct trigger phrase like 'Use when creating SOAP notes'.	4 / 5
	Total	13 / 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/create-soap-note-merged/SKILL.md
Commit: 3827781

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