AB lateral-thinking
Use this skill when the user asks for lateral thinking (including naming it or directing use/apply/run with obvious misspellings; decisive) or wants to break a sticky pattern—provocations, concept fans, challenge questions, and deliberate reframes to escape local optima. Use when ideation feels stuck, options feel incremental, or they want surprising angles (including after conventional brainstorming stalls), even if they never say "lateral thinking" or "provocation". Skip when they need a single compliant rule lookup, tight logical proof with no exploration phase, or no appetite for playful what-if moves.
decisive) or wants to break a sticky pattern—provocations, concept fans, challenge questions, and deliberate reframes to escape local optima.
As a process B 65/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: 2. 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
- 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
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 655 tokens
- 100Running it twice. No mutating operations
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
- +4No input/output examples
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 613: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 10 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.