brainstorming

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

Quality

48%

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 concise, well-structured catalogue pointer that deliberately outsources the real workflow to an upstream repo. That keeps it lean and navigable but leaves it almost devoid of executable guidance or a defined workflow, which caps the action-oriented dimensions.

Suggestions

Inline at least one concrete, copy-pasteable step for installing or locating the upstream bundle (e.g., the exact clone command and target skills-directory path) instead of only opening the repo URL.

Add a minimal sequenced workflow with explicit checkpoints (install bundle -> verify skill is registered -> invoke by name/trigger), so the skill is actionable without round-tripping to the upstream README.

Remove the verbatim repetition of the description in 'What it does' and the duplicated upstream URL in 'Source' to trim redundant tokens.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept over-explanation; the only padding is the verbatim repeat of the description in 'What it does' and a duplicated upstream URL in 'Source', which are minor trimmable instances rather than pervasive verbosity.	4 / 5
Actionability	Concrete guidance is minimal: the only command is `open https://github.com/obra/superpowers` (opens a browser) and the body defers all real steps to the upstream README, providing no executable install or invocation steps.	2 / 5
Workflow Clarity	A rough sequence exists (inspect upstream README, install bundle, ask agent to invoke) but it is poorly defined with major gaps — no install commands, no paths, no checkpoints — matching the rough-sequence-many-gaps anchor.	2 / 5
Progressive Disclosure	Content is organized into clear sections (What it does / Source / How to use) with a single clearly-signaled one-level external pointer (the upstream repo); no bundle files exist so there is no nesting risk, though the pointer is an external URL rather than an internal reference file.	4 / 5
	Total	12 / 20 Passed

Description

50%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 conveys a clear purpose and domain with third-person voice and no fluff, but offers only two generic actions, no explicit 'Use when' trigger clause, and modest distinctiveness. All dimensions land squarely on the midpoint anchor.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when exploring rough ideas, generating design alternatives, or brainstorming concept directions early in a project').

Broaden the action list beyond 'questioning' and 'exploration' to specific concrete techniques (e.g., 'lists alternative directions, pressure-tests assumptions, maps constraints') to lift specificity and distinctiveness.

Tighten distinctiveness by naming what makes this skill different from general planning (e.g., explicit divergence-before-convergence framing) to reduce overlap with design/planning skills.

Dimension	Reasoning	Score
Specificity	Names the domain (idea-to-design transformation) and two concrete actions ('structured questioning', 'alternative exploration'), but coverage is not comprehensive — fits the 1-2 concrete actions anchor rather than the several-actions anchor at 4.	3 / 5
Completeness	A clear 'what' is present ('Transform rough ideas into fully-formed designs...') but the 'when' is only weakly implied ('Useful early in concept work') with no explicit 'Use when...' clause, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	The description contains a few relevant phrases ('rough ideas', 'concept work') but lacks comprehensive natural-keyword coverage; the broader trigger list lives in a separate frontmatter field, not the description itself.	3 / 5
Distinctiveness Conflict Risk	The brainstorming/ideation niche is recognizable but 'structured questioning and alternative exploration' is broad enough to overlap with general design or planning skills, matching the somewhat-specific-but-overlapping anchor.	3 / 5
	Total	12 / 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: 1a7a23d

Reviewed: about 6 hours 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.