CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

icd10-cpt-coding-assistant

Parse clinical notes and recommend ICD-10-CM diagnosis codes and CPT procedure codes with confidence scoring. Cross-references diagnoses with procedure codes, generates alternatives for medium-confidence matches, and produces structured coding reports with human-review flags.

Quality

74%

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 ./scientific-skills/Other/icd10-cpt-coding-assistant/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 highly actionable with an exemplary checkpointed workflow, but it is bloated with generic template sections that dilute token efficiency, and its progressive disclosure is weak: over half the reference bundle is unreachable from SKILL.md and a cited dependency file (requirements.txt) is missing. Trimming the boilerplate and wiring up the remaining reference files would lift both low dimensions.

Suggestions

Remove or relocate the generic template blocks (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Response Template) — they contribute padding, not skill-specific instruction.

Reference the four orphaned bundle files (code_examples.md, common_mappings.json, cpt_guidelines.md, icd10_guidelines.md) from the References section, or remove them from the bundle if unused.

Fix the broken requirements.txt reference (ship the file or drop the Dependencies/Prerequisites mentions), and consolidate the duplicated Quick Check / Audit-Ready Commands and Dependencies / Prerequisites sections.

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded sections: it expands "ICD-10-CM: International Classification of Diseases, 10th Revision, Clinical Modification" and "CPT: Current Procedural Terminology" — knowledge Claude already has — and carries large generic template blocks (Risk Assessment table, unchecked Security Checklist, Evaluation Criteria with placeholders like "Standard input → Expected output", Lifecycle Status, Output Requirements, Response Template) that add tokens without skill-specific instruction. Quick Check and Audit-Ready Commands duplicate the same py_compile line, and Dependencies and Prerequisites both cover requirements.txt. This fits anchor 2 (several unnecessary explanations/padded sections); it avoids anchor 1 only because the core sections (Workflow, Parameters, Output Format) are dense and useful.

2 / 5

Actionability

Mostly executable guidance: runnable commands ("python -m py_compile scripts/main.py", "python scripts/main.py --help", a real sample invocation), a full parameter table with defaults, concrete JSON output examples with realistic codes (J20.9, 99213), and a programmatic usage example. Minor gaps keep it below 5: the body twice points to a requirements.txt that does not exist in the bundle (so "pip install -r requirements.txt" fails), and the Usage example passes the literal string "clinical_note.txt" where a path is documented.

4 / 5

Workflow Clarity

The five-step Workflow is clearly sequenced, each step states Input → operations → Output, and step 4 contains an explicit validation checkpoint ("⛔ Checkpoint: Present low-confidence codes (<0.7) to user for manual review; confirm all codes before output") appropriate to this high-stakes domain. The Quick Check provides an up-front parseability gate, and the Error Handling section defines failure recovery (report failure point, summarize what remains, manual fallback). This matches anchor 5: clear sequence, explicit validation steps, and error-recovery guidance.

5 / 5

Progressive Disclosure

Structure exists (a dedicated References section with correctly named files, and all three cited paths — icd10_common_codes.json, cpt_common_codes.json, coding_guidelines.md — exist in references/), but the signaling covers only 3 of the 7 bundled reference files: code_examples.md, common_mappings.json, cpt_guidelines.md, and icd10_guidelines.md are never mentioned anywhere in SKILL.md, leaving most of the bundle undiscoverable. Meanwhile generic filler (security checklist, risk assessment) is inlined in the overview file. This sits between anchor 3 (references not clearly signaled / misplaced inline content) and anchor 4; it lands at 3 because more than half the bundle is invisible from the entry point.

3 / 5

Total

14

/

20

Passed

Description

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

A strong, specific third-person description that concretely covers the full capability pipeline with excellent distinctiveness. Its one structural gap is the complete absence of a 'Use when...' trigger clause, which caps completeness and leaves invocation guidance to be inferred.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user mentions ICD-10, CPT, medical coding, billing codes, or asks to code clinical notes, SOAP notes, or discharge summaries.'

Add one or two natural synonyms users actually say ("medical coding", "billing codes") to strengthen trigger-term coverage.

Keep the existing specificity; no changes needed to the action list.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage: "Parse clinical notes", "recommend ICD-10-CM diagnosis codes and CPT procedure codes with confidence scoring", "Cross-references diagnoses with procedure codes", "generates alternatives for medium-confidence matches", "produces structured coding reports with human-review flags". Every verb names a distinct capability and the pipeline is covered end-to-end; nothing is generic filler.

5 / 5

Completeness

The 'what' is clear and detailed (parse, map to both code sets, cross-reference, score confidence, report), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description. Per the judging guidelines, a missing 'when' caps completeness at 3; it is not a 2 because the 'what' half is fully explicit, and not a 4 because 'when' is entirely absent rather than merely weak.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms a clinician or coder would say: "clinical notes", "diagnosis codes", "procedure codes", "coding reports", plus the standard vocab "ICD-10-CM" and "CPT". A few common phrasings are missing — users plausibly say "medical coding", "billing codes", or "charge capture", and no note-format synonyms (SOAP note, discharge summary) appear.

4 / 5

Distinctiveness Conflict Risk

This is a clear niche with distinct triggers: ICD-10-CM/CPT medical coding of clinical documentation is unlikely to collide with any other skill category, and the domain vocabulary is unambiguous. Minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/icd10-cpt-coding-assistant/SKILL.md

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.