AB ot-evaluation-report
Use this skill when a licensed Occupational Therapist (OT), OTA under supervision, or documentation specialist needs to draft an initial OT evaluation report for an outpatient, inpatient, school-based, or home-health client. Covers occupational profile, ADL/IADL performance analysis, standardized assessment scores, clinical impressions, and SMART goals aligned to AOTA OTPF-4 and CMS documentation requirements. Produces a DRAFT report for licensed OT sign-off before any payer submission or medical record entry.
Use this skill when a licensed Occupational Therapist (OT), OTA under supervision, or documentation specialist needs to draft an initial OT evaluation report…
As a process B 78/100 · Nearly there — weak spots: 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: 4. 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 78/100
- 0Progress reporting. Says nothing while it works
- 50When 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
- 70Failures and branches. 4 branches
- 85Steps. 55 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2717 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 515: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 55 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.