AB tandoor-recipe-cli
Manage recipes, meal plans, and shopping lists on a Tandoor Recipe Manager instance via CLI.
As a process B 65/100 · Nearly there — weak spots: consistency, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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: 5. 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 65/100
- 30Running it twice. 25 mutating operations with no state check
- 40Consistency. Frontmatter name (tandoor-recipe-cli) differs from the folder (tandoor-cli)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4396 tokens
- 100Steps. 53 steps
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (18 tags): a typed call is more reliable
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)
- +3Description length 92: 120–800 characters recommended
- +2Single-language instructions
- +4Structure: 16 headings
- +3Step-by-step instructions: 53 items
- +3Output format is stated explicitly
- +4Has examples (13 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.
External checks
ClawHub: clean
This skill asks for sensitive Tandoor access, but its powers are disclosed, purpose-aligned, and scoped to user-approved recipe, shopping, and household tasks.
LLM: benign (high) · VirusTotal: · 29 May 2026