brainstorming-skill
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or when users request help with ideation, marketing, and strategic planning. Explores user intent, requirements, and design before implementation using 30+ research-validated prompt patterns.
78
Quality
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/brainstorming-skill/skills/brainstorming-skill/SKILL.mdQuality
Discovery
59%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 attempts to be comprehensive about when to use the skill but is overly broad, creating high conflict risk with other skills. It provides decent trigger coverage but lacks specific concrete actions. The prescriptive 'MUST use this' language is problematic for skill selection in a multi-skill environment.
Suggestions
Narrow the scope significantly - instead of 'any creative work', specify the unique value proposition (e.g., 'Facilitates structured requirements gathering and design exploration sessions')
Replace 'MUST use this before' with a more selective trigger like 'Use when the user wants to explore requirements, clarify ambiguous requests, or brainstorm approaches before implementation'
Add more specific concrete actions (e.g., 'Generates clarifying questions, creates requirement checklists, produces design alternatives')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names domain (creative work, ideation, marketing, strategic planning) and mentions '30+ research-validated prompt patterns', but the actual concrete actions are vague - 'Explores user intent, requirements, and design' lacks specific actionable verbs like 'generates', 'analyzes', or 'produces'. | 2 / 3 |
Completeness | Clearly answers both what ('Explores user intent, requirements, and design before implementation using 30+ research-validated prompt patterns') and when ('before any creative work - creating features, building components, adding functionality, modifying behavior, or when users request help with ideation, marketing, and strategic planning'). | 3 / 3 |
Trigger Term Quality | Includes some natural terms users might say ('features', 'components', 'ideation', 'marketing', 'strategic planning'), but missing common variations and the phrasing is more prescriptive than matching natural user language. Terms like 'creative work' and 'modifying behavior' are somewhat abstract. | 2 / 3 |
Distinctiveness Conflict Risk | Very broad scope ('any creative work', 'creating features', 'building components', 'adding functionality') would likely conflict with many other skills. The 'MUST use this before' framing makes it overly aggressive and could trigger inappropriately for tasks handled by more specific skills. | 1 / 3 |
Total | 8 / 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 hard gate enforcement and explicit approval loops are particularly strong. The main weakness is some redundancy between the numbered workflow steps and the Mermaid diagram, plus verbose meta-instructions about diagram interpretation that Claude doesn't need.
Suggestions
Remove the duplicate workflow description - keep either the numbered list OR the Mermaid diagram, not both
Trim the verbose Mermaid interpretation instructions (the two paragraphs starting with '> [!IMPORTANT]') - Claude understands flowcharts without explicit meta-instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (the workflow is described both as a numbered list AND a Mermaid diagram). The meta-instructions about Mermaid diagrams are verbose and could be trimmed since Claude understands flowcharts. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific file paths (docs/plans/YYYY-MM-DD-<topic>-design.md), clear step sequences, and references to complete pattern libraries. The workflow steps are specific and actionable. | 3 / 3 |
Workflow Clarity | Excellent workflow clarity with explicit phases, decision points, and validation gates. The Mermaid diagrams clearly show the sequence including the revision loop (Approve -> Present) and the hard gate prevents premature implementation. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview in main file and one-level-deep references to 7 specific reference files for detailed patterns. Navigation is clear with descriptive links to each reference document. | 3 / 3 |
Total | 11 / 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.
- Repository
- Jamie-BitFlight/claude_skills
- Commit
fd243f9
- 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.