AB appliance-buying-guide
Cut through the model soup to buy the right appliance — the features that actually matter for you, the ones that are marketing, and when to buy. Use when asked which [fridge/washer/dishwasher] should I buy, help me choose an appliance, what features do I need, or is this appliance worth it. Produces a needs-based feature shortlist (must-have vs nice-to-have vs marketing fluff), fit and capacity checks, reliability and running-cost considerations, warranty/extended-warranty guidance, and timing tips — flagging to verify current models, prices, and specs before buying.
Cut through the model soup to buy the right appliance — the features that actually matter for you, the ones that are marketing, and when to buy.
As a process B 70/100 · Nearly there — weak spots: failures and branches, running it twice, 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
- 30Running it twice. 1 mutating operations with no state check
- 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
- 100Tools and files. No external tools needed
- 100Steps. 34 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 989 tokens
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 573: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 34 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.