mapping-to-snomed

Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL query, translate via a ConceptMap, or resolve a span to a concept id with FHIR $lookup/$translate/$validate-code. Trigger keywords: SNOMED CT, SNOMED concept id, ECL, ConceptMap, $translate, $lookup, Ontoserver, Snowstorm, SCTID, post-coordination, terminology server. Pairs after OpenMed NER: consume Disease/Anatomy/Pharmaceutical entities from openmed.analyze_text and map each span out-of-process. SNOMED CT is license-restricted — it is NEVER bundled; the user calls their own affiliate-licensed server.

Quality

93%

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

Quality

Content

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

Executable, well-structured content with strong code examples and a clear validated workflow. The main improvement opportunity is consolidating the repeated licensing-boundary messaging and adding an explicit validation retry loop for the batch mapping step.

Suggestions

Consolidate the 'never bundle SNOMED CT' guidance into one authoritative callout so it is not restated across the intro, the blockquote, and the edge-cases section.

Add an explicit validate→fix→retry feedback loop in the Workflow (e.g., if $validate-code fails, re-rank candidates and retry) to lift workflow clarity.

Show per-entity validation in the Hand-off code loop so the batch example mirrors the workflow's Validate step.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence, with brief justified glossing of domain terms (SCTID, ECL); the 'never bundle SNOMED CT' licensing boundary is restated across the intro, the callout block, and an edge-case bullet, which could be consolidated.	4 / 5
Actionability	Two complete, copy-paste-ready Python blocks perform real FHIR operations ($lookup, $expand/$translate) with env-var configuration, timeouts, error handling, and real SCTID/ECL examples covering the common cases.	5 / 5
Workflow Clarity	A clear 7-step sequence includes an explicit Validate step ($validate-code, $lookup), satisfying validation for this batch operation, but there is no explicit validate→fix→retry feedback loop for error recovery.	4 / 5
Progressive Disclosure	No bundle files exist, so the single well-organized SKILL.md with clearly headed sections (When to use, Quick start, Workflow, Hand-off, Edge cases) and one-level-deep external links in a dedicated Standards & references section navigates easily.	5 / 5
	Total	18 / 20 Passed

Description

100%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 dense, information-rich description that explicitly covers what it does, when to use it, natural trigger keywords, and a distinct niche with low conflict risk. The only minor blemish is slight redundancy in the licensing restatement, but no dimension is materially weakened by it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — mapping spans to SNOMED CT concepts, running ECL queries, translating via ConceptMap, resolving spans with FHIR $lookup/$translate/$validate-code, and consuming OpenMed entities — covering the domain comprehensively.	5 / 5
Completeness	Clearly states both what it does ('Maps clinical concept spans…to SNOMED CT concepts…') and when to use it ('Use when the user wants to code findings, disorders, procedures…run an ECL query, translate via a ConceptMap, or resolve a span'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	An explicit trigger-keyword list covers natural terms and synonyms users would say (SNOMED CT, SNOMED concept id, SCTID, ECL, ConceptMap, $translate, $lookup, Ontoserver, Snowstorm, post-coordination, terminology server).	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (SNOMED CT coding via a user-supplied terminology server paired with OpenMed NER) with distinct triggers and explicit disambiguation against sibling skills, minimizing conflict risk.	5 / 5
	Total	20 / 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: maziyarpanahi/openmed
Path: skills/mapping-to-snomed/SKILL.md
Commit: 80da98c

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