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.
78
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 overly broad scope and vague capability statements. While it attempts to define when to use the skill, the trigger conditions are so expansive ('any creative work') that it would conflict with many other skills. The actual capabilities ('explores user intent, requirements and design') lack specificity about what concrete actions or outputs the skill provides.
Suggestions
Narrow the scope by specifying the domain or type of work (e.g., 'software features', 'UI components', 'API endpoints') rather than generic 'creative work'
Replace 'Explores user intent, requirements and design' with specific actions like 'Asks clarifying questions, documents requirements, creates design specifications, identifies edge cases'
Add specific trigger terms users would naturally say, such as 'plan', 'scope', 'requirements gathering', 'design doc', 'before I start', 'help me think through'
| 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 and outputs. | 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' would conflict with virtually any development, design, or implementation skill. | 1 / 3 |
Total | 6 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that effectively guides Claude through a collaborative design process. It excels at providing clear workflow with explicit gates and validation points, concrete actionable steps, and efficient use of tokens. The HARD-GATE pattern and anti-pattern section effectively prevent common failure modes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what brainstorming or design processes are. | 3 / 3 |
Actionability | Provides concrete, specific guidance: exact file paths for design docs, explicit checklist items, clear process steps, and specific behaviors (one question at a time, multiple choice preferred). The graphviz diagram adds executable clarity to the workflow. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit sequence, validation checkpoints (user approval gates), and feedback loops (revise if not approved). The HARD-GATE and checklist provide clear validation points, and the process flow diagram makes the sequence unambiguous. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections (Overview, Checklist, Process Flow, The Process, After the Design, Key Principles). References to other skills (writing-plans, elements-of-style) are one level deep and clearly signaled. Content is appropriately organized for a skill of this complexity. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%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.
- Reviewed
Table of Contents
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.