brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

1.00x

Quality

75%

Does it follow best practices?

Impact

88%

1.00x

Average score across 1 eval scenario

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/brainstorming/SKILL.md

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, actionable, and well-sequenced process skill with strong checklists and validation gates. The chief weaknesses are redundancy (the flow diagram duplicates the checklists) and a dangling visual-companion.md reference plus unlinked script bundle files that weaken progressive disclosure.

Suggestions

Either ship visual-companion.md in the bundle or remove the reference to it; if it lives elsewhere, give its real path so navigation is not broken.

Link the server scripts explicitly (e.g. 'run scripts/start-server.sh --open') instead of referring to 'the server' by implication, so the bundle is discoverable.

Consider dropping the dot Process Flow diagram or the redundant checklist restatement — they cover the same sequencing, so keeping both costs tokens for little new information.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and purposeful, but the dot Process Flow diagram restates the Spike/Bounded/Architectural checklists and the approval-gate message recurs across the HARD-GATE, Anti-Pattern, and Red Flags sections — real tightening is possible without losing the point.	3 / 5
Actionability	Highly concrete prescriptive guidance throughout: numbered checklists, exact spec path ('docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md'), a quoted visual-companion offer message, and the '--open' server command — specific examples cover the common cases for an instruction-only skill.	5 / 5
Workflow Clarity	Three numbered checklists sequence each path with explicit approval checkpoints ('STOP and wait for an explicit yes'), decision diamonds in the flow, and a spec self-review feedback loop that fixes inline and re-runs on requested changes.	5 / 5
Progressive Disclosure	Well-sectioned body, but the referenced 'skills/brainstorming/visual-companion.md' is not present in the bundle, the scripts/ bundle files (start-server.sh etc.) are not linked by path, and substantial detail is inlined rather than split out — references are not clearly signaled.	3 / 5
	Total	16 / 20 Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states both purpose and trigger conditions with concrete, natural language. The main weakness is the second-person 'You MUST use this' opening, which violates the third-person voice convention and costs specificity points.

Suggestions

Rewrite in third person to avoid the voice penalty, e.g. 'Explores user intent, requirements, and design before any creative work — creating features, building components, adding functionality, or modifying behavior.'

Add a 'Use when...' style trigger clause with common user phrasings like 'add a feature' or 'change how a component works' to round out trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ('Explores user intent, requirements and design before implementation'), landing at anchor 3, but the second-person 'You MUST use this before any creative work' incurs the -1 voice penalty, dropping it to 2.	2 / 5
Completeness	It explicitly answers both what ('Explores user intent, requirements and design before implementation') and when ('You MUST use this before any creative work - creating features...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural phrases users would say ('creating features', 'building components', 'adding functionality', 'modifying behavior') give good keyword coverage, though a few common variations ('add a feature', 'change how X works') are missing.	4 / 5
Distinctiveness Conflict Risk	The pre-implementation design-gate framing carves a clear niche, though 'any creative work' is broad and risks minor overlap with implementation skills.	4 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: obra/superpowers
Path: skills/brainstorming/SKILL.md
Commit: b36e082

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.