CtrlK
BlogDocsLog inGet started
Tessl Logo

exporting-to-fhir

Convert OpenMed NER output (entities from openmed.analyze_text) into FHIR R4 resources — Condition, MedicationStatement, Observation — using OpenMed's built-in FHIR R4 export helpers in openmed.clinical.exporters. Covers the verified CodeableConcept builder (coding, codeable_concept, system_uri), deterministic fullUrl references, and OperationOutcome reporting. Use after running OpenMed NER when the user wants standards-conformant FHIR JSON, mentions FHIR, Condition/Observation/MedicationStatement, CodeableConcept, RxNorm/LOINC/ICD-10/SNOMED coding, or interoperability with an EHR. Pairs after extracting-clinical-entities; feeds assembling-fhir-bundles and validating-us-core.

74

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A dense, actionable, well-structured body with executable examples covering the main resource types and a clear workflow. It could be tightened slightly and would benefit from an inline validation feedback loop and splitting large examples into reference files.

Suggestions

Conciseness: trim the introductory paragraph and rationale prose around the API (e.g., 'That is by design...') to reduce token overhead while keeping the OpenMed-specific API detail.

Workflow clarity: add an explicit validate -> fix -> retry feedback loop in the Workflow section rather than delegating validation entirely to validating-us-core, since building a resource list is a batch operation.

Progressive disclosure: consider moving the full MedicationStatement/Observation resource examples and the resource cheat-sheet into a reference file so SKILL.md stays a lean overview pointing to detail.

DimensionReasoningScore

Conciseness

Mostly efficient OpenMed-specific API detail that Claude does not already know, but includes some trimmable explanatory prose (intro paragraph, 'That is by design...' sentences); not 5 because not every token earns its place, not 3 because it is not noticeably verbose.

4 / 5

Actionability

Fully executable copy-paste Python covering Condition, MedicationStatement, and Observation plus a worked JSON output; the one stand-in (hardcoded codes) is explicitly justified as out-of-process grounding.

5 / 5

Workflow Clarity

Clear 7-step sequenced workflow with validation present (step 7 validate, OperationOutcome for unmapped spans, to_bundle rejecting duplicate ids); the batch cap does not bind because validation is not missing, but no inline validate->fix->retry feedback loop or gating, so not 5.

4 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level hand-offs to sibling skills, but the skill is a ~230-line monolithic file with multiple full inlined code examples and no bundle files to split into; over 50 lines so the simple-skill auto-5 does not apply.

4 / 5

Total

17

/

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 highly specific, well-triggered, and clearly bounded description that answers both what and when with concrete domain phrases. It distinguishes itself from sibling skills via explicit pairing/feeding language.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (convert NER output to FHIR R4 Condition/MedicationStatement/Observation, CodeableConcept builder, deterministic fullUrl, OperationOutcome) with comprehensive coverage; not 4 because coverage is broad rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both what (convert OpenMed NER output into FHIR R4 resources via openmed.clinical.exporters) and when (use after NER when the user wants FHIR JSON / mentions FHIR, CodeableConcept, coding systems, or EHR interoperability) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural domain triggers (FHIR, Condition/Observation/MedicationStatement, CodeableConcept, RxNorm/LOINC/ICD-10/SNOMED, EHR interoperability) with synonym coverage across coding systems; no file-extension equivalent applies to this domain.

5 / 5

Distinctiveness Conflict Risk

Clear OpenMed-specific niche with distinct FHIR/coding triggers and explicit boundary delineation against sibling skills (pairs after extracting-clinical-entities; feeds assembling-fhir-bundles and validating-us-core); minimal conflict risk. Third-person voice, no pronoun penalty.

5 / 5

Total

20

/

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
maziyarpanahi/openmed
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.