AC home-damage-evidence
Route users to the right property-damage evidence tool when their home was hit by a storm, earthquake, or interior water leak (pipe, appliance, AC condensate), or when they want to document their home before damage. Provides claim-documentation guidance (what to photograph, what to keep) and deep links to free checks and claim-ready report tools built on official NOAA/NWS/USGS records. Use for insurance claim documentation, storm damage, hail, wind, hurricane, tornado, earthquake shaking, roof history, water leaks, and pre-storm baselines.
Route users to the right property-damage evidence tool when their home was hit by a storm, earthquake, or interior water leak (pipe, appliance, AC…
As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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: 2. 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 59/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
- 20When it triggers. No condition that starts the skill
- 60Failures and branches. 2 branches
- 100Tools and files. No external tools needed
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1166 tokens
- 100Running it twice. Mutating operations check current state
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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +3Description length 545: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 16 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.