AB physio-discharge-summary
Write a physiotherapy discharge summary that closes the episode properly — outcomes against the goals that were set, what the patient is leaving with, what would bring them back, and what the referrer actually needs to know. Use when asked to write a discharge summary, close an episode of care, write to a referrer at discharge, or discharge a patient who has not fully recovered. Produces the outcome summary against baseline, the self-management plan, the flare-up and return criteria, the referrer letter, and the record of incomplete goals. A documentation framework for a licensed clinician.
Write a physiotherapy discharge summary that closes the episode properly — outcomes against the goals that were set, what the patient is leaving with, what…
As a process B 70/100 · Nearly there — weak spots: when it triggers, failures and branches, progress reporting
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 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 1375 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 597: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 37 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.