CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

93%

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 strong, dense body: fully executable quick start, a concrete 5-step workflow with real cue lists, thoughtful hand-off contracts to sibling skills and FHIR, and honest scope/edge-case treatment. Minor gains available in trimming the motivational intro and citations, adding an explicit re-validation pass for spans left unclassified, and potentially splitting cue-lexicon detail into a reference file.

Suggestions

Trim the six-line introductory paragraph to a single sentence ('NER finds mentions; it does not tell you whether the patient has them — the ConText layer assigns negation, temporality, and uncertainty before grounding'), and consider condensing the Standards & references section to bare citation names with DOIs on one line each.

Add an explicit validation step to the workflow (e.g., 'Step 6 — Verify: any span that resolves to AFFIRMED/RECENT/CERTAIN with no cue analysis, or that came back with an unexpected axis, re-inspect the window and cue list before recording'), creating a feedback loop rather than relying on the edge-case note to 'double-check anyway'.

Consider moving the per-axis cue lexicons and the full function/constants reference into a one-level-deep references/ file (e.g. CUES.md), keeping SKILL.md to the workflow and quick start — the body currently inlines API-reference material that would scale poorly as the cue lists grow.

DimensionReasoningScore

Conciseness

The body is efficient and teaches only non-obvious domain specifics (cue lexicons, pseudo-negation masking, even/odd parity, FHIR status mapping) rather than concepts Claude already knows. However, the six-line motivational intro ('NER finds *that* a condition was mentioned...') could be one line, and the 'Standards & references' citation block is padding-adjacent, so it fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

The quick start is copy-paste runnable — real imports (openmed.clinical), a concrete note string, and annotated expected output per span ('chest pain -> negated recent certain (do NOT record as present)') — and the workflow steps give exact function signatures with the actual cue lists ('denies', 'no evidence of', 'history of', 's/p', 'rule out', 'probable', 'vs'). This matches 'fully executable; copy-paste ready code; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced with per-step function calls, return values, and downstream application rules, and the quick-start comments act as expected-output checkpoints. It sits at 'clear sequence with most checkpoints present; minor validation gaps' rather than 5 because there is no explicit verify/re-check loop (e.g., re-inspect spans the cue lists leave unclassified) beyond the edge-case advice to 'double-check anyway'.

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files, and the sections (When to use, Quick start, Workflow, Hand-off, Edge cases, Standards) are well-organized and flat — no nested or buried references. It scores 4 rather than 5 because, at ~118 lines, the per-axis cue lexicons and function reference could plausibly live in a one-level-deep reference file per the anchor-5 pattern, though inlining at this length is defensible.

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.

An exemplary description: concrete actions, a full enumerated API surface, an explicit 'Use after NER when...' trigger clause with natural clinical NLP keywords, and clear positional scoping against sibling skills. Third-person voice throughout; dense but with no fluff or over-claims.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Assign negation, temporality, and uncertainty (the ConText axes) to clinical entities extracted by OpenMed' — and comprehensively enumerates the API surface (resolve_negation / resolve_temporality / resolve_uncertainty / resolve_span_context / assert_context_axes, ClinicalAssertion, the AFFIRMED/NEGATED, RECENT/HISTORICAL/HYPOTHETICAL, CERTAIN/UNCERTAIN constants). This matches the 'multiple specific concrete actions; comprehensive coverage' anchor and exceeds the score-4 anchor, which only requires 'several specific actions' with gaps.

5 / 5

Completeness

Both 'what' and 'when' are explicit: the what is 'Assign negation, temporality, and uncertainty (the ConText axes) to clinical entities', and the when is the explicit clause '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.' This is a textbook match for the score-5 anchor; score 4 would require the 'when' to be merely adequate rather than concrete.

5 / 5

Trigger Term Quality

It covers the natural phrases a user would say — 'assertion status', 'negation detection', 'family-history / hypothetical / historical flags', 'ConText/NegEx', 'FHIR', 'problem list' — plus concrete clinical examples ('denies chest pain', 'history of MI'). Coverage is comprehensive with synonyms; no file extensions apply to this domain, so the anchor-5 criterion is satisfied in spirit and there is no adjacent anchor that fits better.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — a ConText/assertion layer over OpenMed NER output — and it explicitly scopes itself relative to siblings ('Use after NER... Pairs after extracting-clinical-entities'), which minimizes overlap risk with the NER and problem-list skills. It is clearly distinguishable from any generic skill and from adjacent clinical skills, matching the score-5 anchor.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

maziyarpanahi/openmed

Path

skills/resolving-clinical-context/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.