AD baby-fever-triage
Use when a baby or small child has a fever at 2 AM and the parents must decide: ER now, doctor in the morning, or watch-and-wait at home. Age-aware triage rules (0-3 months = automatic urgent), red-flag symptom checks, correct weight-based acetaminophen/paracetamol and ibuprofen dosing by weight (never by age), alternating-dose scheduler with safe intervals, temperature-trend log, and a structured handoff summary to bring to the pediatrician. Informational support, not a doctor — but it prevents the two most common and dangerous mistakes: under-dosing a suffering child and over-dosing by accident.
Age-aware triage rules (0-3 months = automatic urgent), red-flag symptom checks, correct weight-based acetaminophen/paracetamol and ibuprofen dosing by weight…
As a process D 47/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, 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: 6. 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 47/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 6 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 85Steps. 34 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1968 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 604: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.