CtrlK
BlogDocsLog inGet started
Tessl Logo

resolving-clinical-context

Assign negation, temporality, and uncertainty (the ConText axes) to clinical entities extracted by OpenMed, so "denies chest pain" is not counted as chest pain and "history of MI" is not counted as an active MI. Use after NER when the user needs assertion status, negation detection, family-history / hypothetical / historical flags, or ConText/NegEx-style classification before grounding entities to FHIR or a problem list. Covers openmed.clinical.resolve_negation / resolve_temporality / resolve_uncertainty / resolve_span_context / assert_context_axes, ClinicalAssertion, and the AFFIRMED/NEGATED, RECENT/HISTORICAL/HYPOTHETICAL, CERTAIN/UNCERTAIN constants. Pairs after extracting-clinical-entities.

72

Quality

88%

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

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.

A well-structured, actionable skill body with executable examples and a clear workflow. Token efficiency is good with only minor trim opportunities, and references are cleanly organized one level deep.

Suggestions

Trim the opening conceptual explanation of what NER finds (lines 14-16), since Claude already knows NER surfaces mentions without assertion status.

Consider moving the four-edge-case block into a tighter checklist to reduce prose while preserving the window-scoping and experiencer-scope warnings.

DimensionReasoningScore

Conciseness

Mostly efficient with executable code and tight prose; a few explanatory sentences about what NER finds and pseudo-negation could be trimmed but generally assume Claude's competence.

4 / 5

Actionability

Fully executable copy-paste Quick start code plus a concrete numbered Workflow with exact function names, return values, and cue lexicons covering common cases.

5 / 5

Workflow Clarity

Clear sequenced five-step workflow with explicit downstream-application guidance; missing an explicit validate/retry checkpoint, but the operation is advisory/annotation rather than destructive so the destructive-cap does not apply.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers and a concise reference list with one-level-deep external links; no bundle files present and content is appropriately self-contained for its size.

5 / 5

Total

18

/

20

Passed

Description

91%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 description that clearly conveys both capability and triggering context with natural user phrasing. It names concrete API surface and pairs cleanly with its upstream skill.

DimensionReasoningScore

Specificity

Lists several concrete actions (assign negation, temporality, uncertainty axes) plus named API symbols and constants, with only minor coverage gaps keeping it below a 5.

4 / 5

Completeness

Explicitly states what it does ('Assign negation, temporality, and uncertainty...') and when to use it ('Use after NER when the user needs assertion status...'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms users would say — 'assertion status', 'negation detection', 'family-history', 'hypothetical', 'historical flags', 'ConText/NegEx' — plus synonyms and concrete tool names.

5 / 5

Distinctiveness Conflict Risk

Clear niche tied to OpenMed's clinical ConText layer and explicit pairing with extracting-clinical-entities; minor overlap risk with adjacent clinical skills keeps it just below 5.

4 / 5

Total

18

/

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.