AB cin7-reorder-point-and-stock-cover
Use for "when should we reorder in Cin7", "what's our reorder point for each SKU", "how many weeks of stock do we have in Cin7", "what will run out before the next delivery", "is our Cin7 reorder level set right", "how much safety stock do we need", or "what do we need to order this week" — even when the user never says "reorder point". Use when the decision is what to order, how much, and by when, per SKU and location. Cin7 Core only.
Use for "when should we reorder in Cin7", "what's our reorder point for each SKU", "how many weeks of stock do we have in Cin7", "what will run out before the…
As a process B 69/100 · Nearly there — weak spots: result and completion, inputs and preconditions, 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 69/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
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 21 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3070 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
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 8 example trigger phrases
- +3Description length 439: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.