AC storm-ready
Use when a hurricane/typhoon, ice storm, tornado outbreak, atmospheric river, wildfire season, or blizzard is approaching your area, when building a household emergency kit, when deciding how much water and food to store, when sizing a generator or power station for outages, when an advisory or watch is issued and you don't know what to do in what order, or annually to audit family preparedness — profiles your region's real hazards (gulf-coast hurricanes demand 14-day supplies, tornado country demands shelter kits, wildfire WUI demands go-bags), sizes water/food/power for YOUR people and pets with real math, runs a gap audit against your inventory, and prints phase-by-phase countdown checklists from T-72h through the storm to recovery, with the life-safety rules (CO, flood water, downed lines) that kill people every year.
Use when a hurricane/typhoon, ice storm, tornado outbreak, atmospheric river, wildfire season, or blizzard is approaching your area, when building a household…
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, 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: 7. 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 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 29 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1785 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
- +3Description length 833: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 9 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (1 code blocks)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.