Name: brainstorming
Rating: 79.4 (1 reviews)
Author: majiayu000

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

71%

Does it follow best practices?

Impact

89%

1.12x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/01-productmanager-brainstorming/SKILL.md

The canonical home for this skill is brainstorming in majiayu000/claude-skill-registry

Quality

Content

67%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 content is a well-structured, actionable brainstorming workflow with clear sequencing and built-in validation checkpoints. Its main weakness is redundancy between The Process and Key Principles sections, which slightly hurts conciseness and organization.

Suggestions

Consolidate the repeated principles: fold 'one question at a time' and 'multiple choice preferred' into a single mention, and trim the Key Principles section to only points not already covered in The Process.

Consider adding a brief checklist at the end of The Process summarizing the validation gate (sections presented and confirmed before moving to design doc) to push workflow clarity toward a 5.

Tighten the bilingual documentation bullets by collapsing the Chinese gloss into one line or moving detailed PRD/feature-doc structure into a referenced file if the skill grows.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and bullet-oriented without explaining concepts Claude already knows, but several principles repeat across sections — "one question at a time" appears three times, "multiple choice preferred" twice, and the Key Principles section largely restates The Process, so it could be tightened.	3 / 5
Actionability	Guidance is concrete and executable for an instruction-only skill: specific paths ("docs/plans/YYYY-MM-DD-<topic>-design.md"), concrete parameters ("200-300 words"), named tools (mcp-feedback-enhanced, superpowers:using-git-worktrees), and a defined sequence, with only minor gaps.	4 / 5
Workflow Clarity	The process is clearly sequenced (Understanding → Documenting → Exploring → Presenting → After the Design) with explicit validation checkpoints ("checking after each section whether it looks right so far") and a feedback loop ("Be ready to go back and clarify"), though no formal checklist is provided.	4 / 5
Progressive Disclosure	The skill is self-contained with clear section headers and no bundle files or nested references, fitting the simple-skill case well; minor organization gaps from the redundant Key Principles section keep it just below a 5.	4 / 5
	Total	15 / 20 Passed

Description

75%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 is strong on completeness, clearly stating both what the skill does and when to use it with concrete triggers. It is slightly weaker on specificity and distinctiveness, where the single action verb and broad creative-work triggers leave some overlap risk with related planning skills.

Dimension	Reasoning	Score
Specificity	"Explores user intent, requirements and design before implementation" names the domain and a couple of concrete actions, but the single verb 'explores' with multiple objects is not comprehensive — closer to the 1-2 concrete actions anchor than the several-distinct-actions anchor at 4.	3 / 5
Completeness	It explicitly answers both 'what' ("Explores user intent, requirements and design") and 'when' with concrete trigger phrases ("You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior"), satisfying the explicit-trigger requirement.	5 / 5
Trigger Term Quality	"creating features, building components, adding functionality, or modifying behavior" are natural phrases users actually say, giving good keyword coverage, though a few synonyms (e.g. 'designing', 'planning a feature') are missing.	4 / 5
Distinctiveness Conflict Risk	Brainstorming/design is a somewhat distinct phase, but the triggers "adding functionality" and "modifying behavior" are broad and could overlap with general coding or planning skills, so overlap risk remains.	3 / 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: majiayu000/claude-skill-registry-data
Path: data/01-productmanager-brainstorming/SKILL.md
Commit: a1e9f44

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