CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

medication-reconciliation

Compare patient pre-admission medication lists with inpatient orders to automatically identify omitted or duplicated medications and improve medication safety.

Quality

78%

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/medication-reconciliation/SKILL.md
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 well-structured CLI skill body: commands are executable and verified against the script, the workflow is sequenced with explicit PHI and validation gates, and scope/error handling are unusually rigorous. The main improvements are removing duplicated instructions, merging or clarifying the two competing response templates, and actually documenting the referenced manual comparison path.

Suggestions

Remove the verbatim duplicate of "If inputs are incomplete, state exactly which fields are missing and request only the minimum additional information" (Workflow step 8 vs Error Handling) and state the dose-change warning text once, referencing it elsewhere.

Document the manual comparison fallback path — the Workflow and Error Handling sections both defer to it, but no steps for it exist anywhere in the skill.

Merge the overlapping Stress-Case Rules (5 blocks) and Response Template (7 items) into a single response structure, or state clearly when each applies.

DimensionReasoningScore

Conciseness

The body is efficient with no filler explanations of concepts Claude already knows, but "If inputs are incomplete, state exactly which fields are missing..." appears verbatim in both Workflow step 8 and Error Handling, and the dose-change warning text is repeated three times (Workflow, Output Format, and the JSON example). These are minor redundancies that could be trimmed, matching anchor 4 rather than 3 (mostly efficient, only minor trimming needed) or 5 (every token earns its place).

4 / 5

Actionability

Fully executable, copy-paste-ready guidance: concrete CLI invocations ("python scripts/main.py --pre-admission pre_meds.json --inpatient orders.json --output report.json"), a --example flag for immediate trial, a complete Parameters table verified against the actual argparse definitions in scripts/main.py, a concrete JSON output example, and a scripted out-of-scope response. Not 4 because the common cases are covered with specific, verified examples rather than having minor gaps.

5 / 5

Workflow Clarity

The 8-step Workflow is clearly sequenced with explicit checkpoints: a PHI confirmation gate first, input well-formedness and patient-ID validation (step 3), dose-change flagging (step 6), and a Quick Check section for verifying the script runs. Not 5 because the error-recovery path is weaker than a full feedback loop — "Run the reconciliation script or apply the manual comparison path" and "provide a manual fallback" reference a manual path that is never actually described, and there is no explicit fix-and-retry loop. Not 3 because validation checkpoints are explicit and prominent, not merely implicit.

4 / 5

Progressive Disclosure

Scored against the actual bundle: the 20KB of reconciliation logic is correctly externalized to scripts/main.py, which is clearly signaled in the Quick Check and Usage sections, and everything inline (parameters, output format, scope) belongs at overview level. Not 5 because of a minor organization gap: the "Stress-Case Rules" 5-block structure and the "Response Template" 7-item structure are two overlapping response layouts presented as separate sections, which slightly muddies navigation; not 3 because there is no content inlined that clearly belongs in a separate file.

4 / 5

Total

17

/

20

Passed

Description

65%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 specific, third-person description of a real niche with low conflict risk, but it is missing an explicit "Use when..." trigger clause, which caps completeness, and its action coverage undersells what the skill actually does (reports, dose-change flags, critical-class warnings). Adding a when-to-use sentence with reconciliation synonyms would lift two dimensions at once.

Suggestions

Append an explicit trigger clause, e.g.: "Use when comparing a patient's pre-admission medication list against inpatient orders during admission, handover, or discharge, or when asked to reconcile medications or find medication discrepancies."

Include the natural synonyms "medication reconciliation", "med rec", and "discrepancies" — the most common phrasings for this task are currently absent.

Mention the structured reconciliation report output (continued / dose_changed / discontinued / new / duplicates) so the description's action coverage matches the skill's actual capabilities.

DimensionReasoningScore

Specificity

The description names the domain ("pre-admission medication lists", "inpatient orders") and the concrete actions of comparing them to "identify omitted or duplicated medications" — i.e., 1-2 concrete actions, but not comprehensive coverage. It omits other capabilities the body documents (structured report generation, dose-change detection, critical drug-class warnings), and "improve medication safety" is purpose padding rather than a specific action, so it does not reach anchor 4's "several specific actions".

3 / 5

Completeness

The "what" is clearly stated ("Compare patient pre-admission medication lists with inpatient orders to automatically identify omitted or duplicated medications"), but there is no "Use when..." clause or any equivalent explicit trigger guidance — nothing about when Claude should invoke the skill, what input files to look for, or the clinical contexts (admission, handover, discharge). Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3, and it is not 2 because the "what" is fully clear rather than vague.

3 / 5

Trigger Term Quality

Good keyword coverage with clinically natural phrases users would actually say: "medication lists", "pre-admission", "inpatient orders", "omitted or duplicated medications". A few natural terms are missing — most notably "medication reconciliation" / "med rec" / "reconcile", which is the single most common way this task is requested, plus "discrepancies" — which keeps it below anchor 5's comprehensive synonym coverage but above anchor 3, since the present terms map directly to real user phrasing.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear clinical niche — comparing pre-admission lists against inpatient orders for one patient encounter — with distinct triggers that would rarely fire for the wrong skill (e.g., a drug-interaction checker or prescribing assistant responds to different requests like "check interactions" or "write an order"). Not 4 because the overlap with even closely related medication skills is minimal given the explicit two-list comparison framing.

5 / 5

Total

15

/

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/medication-reconciliation/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.