AB lateral-thinking
Activate when: user says 'we've tried everything,' 'think outside the box,' 'we need a breakthrough,' 'challenge assumptions,' or 'how might we'; a team keeps cycling through the same 2-3 options; an industry assumption has gone unchallenged for years; conventional analysis keeps returning to the same answer. Do NOT activate when: the problem has a mathematical or logical optimum where vertical analysis gives a definitive answer; time pressure requires a decision in under 5 minutes. More: deciqai.com/c/lateral-thinking
As a process B 66/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securitySKILL.md:78Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **Volume before quality in Steps 3–5.** Evaluation kills lateral movement; no feasibility assessment until Step 6.
Files scanned: 4. 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 66/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 6 branches
- 100Tools and files. No external tools needed
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2345 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 524: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 28 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.