AB scenario-planning
Activate when: user says 'what are the scenarios,' 'stress test our strategy,' 'what if X happens,' 'multiple futures,' 'strategic resilience,' or is making a high-stakes irreversible decision with a 3+ year horizon where a single forecast could be catastrophically wrong. Do NOT activate when: the decision is short-horizon and easily reversible (sprint priorities, A/B test order); or only one driver matters and it is already measurable — use sensitivity analysis instead. More: deciqai.com/c/scenario-planning
As a process B 65/100 · Nearly there — weak spots: inputs and preconditions, 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: 5. 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 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 4 branches
- 100Steps. 34 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2445 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 513: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 34 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.