AB medication-management-system
Set up a system to manage medications safely — for yourself or someone you care for — so doses aren't missed, doubled, or dangerously combined. Use when asked help me manage medications, keep track of my parent's pills, set up a medication system, or I keep forgetting my meds. Produces an organized medication list (what, dose, when, why), a routine and reminder setup that fits the person, a refill-tracking method so nothing runs out, safety checks (interactions and duplications to raise with a pharmacist), and an emergency-ready summary — because medication errors are common and dangerous, and a system prevents most of them. Not medical advice.
Set up a system to manage medications safely — for yourself or someone you care for — so doses aren't missed, doubled, or dangerously combined.
As a process B 72/100 · Nearly there — weak spots: when it triggers, failures and branches
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: 1. 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 72/100
- 0Failures and branches. Linear process with no failure handling
- 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. 33 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1121 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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 652: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 33 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.