AB medication-therapy-review
Structure a pharmacist's medication therapy review so it finds the problems worth escalating and documents them in a form a prescriber will act on. Use when asked to conduct a medication review, run an MTM or MUR, deprescribing review, or polypharmacy assessment, or to prepare a review for a patient on many medicines. Produces the medication list reconciled, the drug-therapy-problem list classified and prioritised, the patient-goal alignment, the prescriber recommendations with rationale, and the follow-up plan. A documentation and reasoning framework for a licensed pharmacist; it makes no clinical determination and recommends no specific drug or dose.
Structure a pharmacist's medication therapy review so it finds the problems worth escalating and documents them in a form a prescriber will act on.
As a process B 70/100 · Nearly there — weak spots: when it triggers, failures and branches, progress reporting
The same skill appears in 2 more places: pm-claude-skills, pm-claude-skills
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 70/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 37 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1443 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 660: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 37 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.