BC supermarket-deals
Search German supermarket flyers (Aldi, Lidl, REWE, EDEKA, Kaufland) for product deals via Marktguru. Results ranked by best price per litre (EUR/L). No API key needed.
Search German supermarket flyers (Aldi, Lidl, REWE, EDEKA, Kaufland) for product deals via Marktguru.
As a process C 52/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:74High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…xCA+ORZv…wO5/ywWF…Tag==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:95High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…ZiR+BeGu…dXd+qTiw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:105High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GD3+82K6JgJlm/Y+KI92…no5+4jh9sw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:131High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…MfZ+71RA…HvA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:138High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Kxf+MSr9…jrj/FHl8…mYA+ftRkP/3oKQ==",
detector
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 52/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 14 steps, 2 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 683 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 168: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 14 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.