BF bring-shopping-list
Manage Bring! shopping lists via CLI — add, remove, complete, and list items. Use when the user wants to interact with Bring! grocery/shopping lists: add items, remove items, check items off, view list contents, or list available shopping lists. Also matches phrases like "bring list", "shopping list", "Einkaufsliste", "add to shopping list", "Bring! API".
As a process F 44/100 · Will not run — References files that are not bundled: scripts/bring.py
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Manage Bring! shopping lists via CLI — add, remove, complete, and … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: scripts/bring.py
Process rating: all ten parameters 44/100
- 0Tools and files. 1 referenced file(s) missing: scripts/bring.py
- 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
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (bring-shopping-list) differs from the folder (bring-app)
- 70When it triggers. States when to use, but not when not to
- 100Steps. 18 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 698 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 357: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.