CC brainstorm
TRIGGER when: asked to brainstorm, think through, explore, or pressure-test a technical idea or decision through conversation. Interviews adaptively, asks one question at a time, and closes with a chat recap. For technical products, architecture, infrastructure, tools, operations, and engineering workflows. Written design/specification and task-list requests belong to /kk:design; durable domain glossary/reference kits to /kk:model; implementation and fixes to /kk:implement. Not for nontechnical brainstorming.
TRIGGER when: asked to brainstorm, think through, explore, or pressure-test a technical idea or decision through conversation.
As a process C 53/100 · Has gaps — References files that are not bundled: shared-ideation-frameworks.md, shared-idea-refinement-criteria.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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 Obfuscation
obf-base64-blobSKILL.md:33Long base64-looking blob (quoted — discussed, not commanded)The prerequisite-aware interview and separation of researched facts from user decisions draw on [Matt Pocock's grilling skill, pinned at `85f83d3`](https://github.com/mattpocock/skills/blob/85f83d3fde
quoted
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: shared-ideation-frameworks.md - warning
missing-refreference to a missing file: shared-idea-refinement-criteria.md
Process rating: all ten parameters 53/100
- 0Tools and files. 2 referenced file(s) missing: shared-ideation-frameworks.md, shared-idea-refinement-criteria.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 7 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1102 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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 514: enough signal without eating the budget
- +4Structure: 3 headings
- +3Step-by-step instructions: 7 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.