AC six-thinking-hats
Use this skill when the user asks for six thinking hats, parallel thinking, or Edward de Bono's method (including naming any of these or directing use/apply/run with obvious misspellings; decisive)—or wants a sequential, six-role thinking partner for one focus—keeping facts, feelings, risks, benefits, and new ideas in separate passes instead of one mixed reply. Use for structured brainstorms, decisions, or reviews when they ask for hat-by-hat analysis or name the method or author, even if phrasing is casual or incomplete. Skip for plain factual questions, execution-only implementation with no structured perspective pass, or one-off hot takes and single-angle verdicts where they do not want a fixed, hat-by-hat sequence across six roles.
As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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 61/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
- 40Consistency. Frontmatter name (six-thinking-hats) differs from the folder (six-hats-thinking)
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 29 steps
- 100Execution cost. Instruction body is 1321 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
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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +3Description length 745: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 29 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.