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.12x

Quality

58%

Does it follow best practices?

Impact

89%

1.12x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./data/01-productmanager-brainstorming/SKILL.md

Quality

Discovery

32%

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

This description suffers from vague, abstract language that fails to communicate specific capabilities. While it attempts to define when to use the skill, the scope is so broad ('any creative work') that it would likely conflict with many other skills. The description also uses second person voice ('You MUST use this') which violates the third-person requirement.

Suggestions

Replace abstract language with concrete actions (e.g., 'Conducts requirements gathering sessions, creates user stories, drafts technical specifications, produces wireframes').

Narrow the scope to a specific domain and add distinct trigger terms (e.g., 'Use when starting a new feature, when requirements are unclear, or when the user says "let's plan", "what should we build", or "requirements gathering"').

Rewrite in third person voice ('Explores user intent...' → 'Guides requirements discovery and design exploration before implementation begins').

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'creative work', 'features', 'components', 'functionality' without specifying concrete actions. 'Explores user intent, requirements and design' is abstract rather than listing specific capabilities.	1 / 3
Completeness	Has a 'when' clause ('before any creative work - creating features, building components...') but the 'what' is weak - 'Explores user intent, requirements and design' is vague about actual capabilities. The 'Use when' equivalent exists but lacks explicit trigger guidance.	2 / 3
Trigger Term Quality	Contains some relevant terms like 'features', 'components', 'building', 'design', 'requirements' that users might say, but these are generic and could apply to many different skills. Missing specific domain terms.	2 / 3
Distinctiveness Conflict Risk	Extremely generic scope - 'creative work', 'features', 'components', 'functionality', 'modifying behavior' could conflict with virtually any development, design, or planning skill. No clear niche established.	1 / 3
	Total	6 / 12 Passed

Implementation

85%

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

This is a well-structured skill with excellent workflow clarity and progressive disclosure. The content is concise and assumes Claude's intelligence. The main weakness is actionability - while the process is clear, concrete examples of brainstorming questions, design document templates, or sample outputs would make it more immediately executable.

Suggestions

Add 2-3 example brainstorming questions (both multiple choice and open-ended) to demonstrate the questioning style

Include a brief example snippet of what a design section (200-300 words) looks like in practice

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, using bullet points and short phrases. It assumes Claude's competence and doesn't explain basic concepts. Every section serves a clear purpose without padding.	3 / 3
Actionability	Provides clear process guidance and specific file paths (docs/plans/YYYY-MM-DD-<topic>-design.md), but lacks concrete examples of questions to ask, design document templates, or sample outputs. The guidance is directional rather than copy-paste ready.	2 / 3
Workflow Clarity	Clear multi-step process with explicit phases (understanding → documenting → exploring → presenting → after). Includes validation checkpoints ('Ask after each section whether it looks right') and feedback loops ('Be ready to go back and clarify').	3 / 3
Progressive Disclosure	Well-structured overview with clear sections. References to other skills (elements-of-style, superpowers:using-git-worktrees, superpowers:writing-plans) are one level deep and clearly signaled. Content is appropriately scoped for a SKILL.md file.	3 / 3
	Total	11 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: majiayu000/claude-skill-registry-data
Commit: 2bbaa03

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