brainstorming

Transform rough ideas into fully-formed designs through structured questioning and alternative exploration. Useful early in concept work.

Quality

44%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

47%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.

The body is a well-organized, token-efficient catalogue entry, but as an advertisement stub it contains essentially none of the actual skill content: no brainstorming process, questions, or examples, and the only pointer is an external URL the agent cannot follow autonomously. An agent acting on this file alone could not perform any part of the advertised workflow.

Suggestions

Inline a minimal version of the core workflow (e.g. the key structured questions or the alternative-exploration steps) so the skill is usable without fetching the upstream repo.

Replace the interactive `open https://github.com/obra/superpowers` instruction with a concrete, machine-executable command such as a git clone or curl of the skill bundle, including the target install path.

Remove the duplicated description and source metadata sections, or merge them, since the frontmatter already carries both verbatim.

Dimension	Reasoning	Score
Conciseness	The ~30-line body is lean with no padding or explanations of concepts Claude already knows, but "What it does" repeats the frontmatter description verbatim and "Source" repeats the upstream URL and category, which is trimmable duplication ('efficient; minor instances of over-explanation that could be trimmed').	4 / 5
Actionability	The only concrete guidance is "open https://github.com/obra/superpowers" and an instruction to invoke the skill by name; the actual brainstorming workflow is entirely absent, matching 'minimal concrete guidance; high-level hints but missing the specific steps to execute'.	2 / 5
Workflow Clarity	A rough two-step sequence exists (install the upstream bundle, then invoke by name or trigger), but there are no install commands, no paths, and no validation of the installed bundle — 'rough sequence present but many gaps; steps poorly defined; validation absent'.	2 / 5
Progressive Disclosure	No bundle files exist and the under-50-line body is well organized into clear sections (What it does / Source / How to use), so the simple-skill exception applies; however, its single reference is an external URL requiring manual installation rather than a well-signaled one-level-deep local file, keeping it at 'good structure; minor organization gaps'.	4 / 5
	Total	12 / 20 Passed

Description

42%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.

The description gives a clear, concise statement of what the skill does but relies on abstract process language and omits an explicit 'Use when...' trigger clause, leaving the when-to-use guidance only weakly implied. Natural trigger keywords live in the frontmatter's separate triggers list rather than in the description itself, costing trigger discoverability.

Suggestions

Add an explicit trigger clause to the description, e.g. "Use when the user wants to brainstorm, explore design alternatives, or develop rough ideas early in concept work."

Replace abstract phrasing like "structured questioning and alternative exploration" with concrete actions, e.g. "asks clarifying questions, generates multiple design directions, and develops a chosen direction into a full design".

Fold 2-3 of the most natural user phrasings (brainstorm, ideation, rough ideas) into the description itself so trigger matching does not depend on the separate triggers list.

Dimension	Reasoning	Score
Specificity	"Transform rough ideas into fully-formed designs" names the domain and "structured questioning and alternative exploration" names 1-2 actions, but these are abstract processes rather than concrete operations, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor.	3 / 5
Completeness	The 'what' is clear ("Transform rough ideas into fully-formed designs through structured questioning and alternative exploration") but the 'when' is only weakly implied by "Useful early in concept work"; there is no explicit 'Use when...' clause, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	The description text contains no natural trigger keywords or 'Use when' phrasing — only "concept work" gestures at a context, matching 'one or two generic keywords; missing the natural phrases users say'. The frontmatter's separate triggers list is outside the evaluated description field.	2 / 5
Distinctiveness Conflict Risk	"rough ideas", "design alternatives", and "concept work" carve out a niche, but this vocabulary is shared with adjacent design/creative skills, so overlap risk remains ('somewhat specific but could still overlap with similar skills').	3 / 5
	Total	11 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/brainstorming/SKILL.md
Commit: 1b47e60

Reviewed: 3 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.