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.

Quality

74%

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 ./plugins/brainstorming-skill/skills/brainstorming-skill/SKILL.md

Quality

Content

73%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 well-structured, actionable overview with a clear validated workflow and clean one-level references. Its main weaknesses are duplicated workflow presentation (numbered list plus Mermaid) and a set of orphaned reference files not surfaced from SKILL.md.

Suggestions

Collapse the duplicated workflow into a single representation (keep the authoritative Mermaid, link the numbered steps to it) to remove redundancy and lift conciseness.

Either reference the 11 unlisted bundle files from the body or remove them, so every reference file is discoverable from SKILL.md.

Replace the inlined 14-category index with a pointer to pattern-categories-and-documentation.md to avoid duplicating content already in the references.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but the full workflow is duplicated as both a numbered list and a Mermaid diagram, and the 'Process Flow' meta-paragraph about diagram authority adds padding that could be tightened.	3 / 5
Actionability	Provides concrete guidance — a sequenced workflow, a specific output path ('docs/plans/YYYY-MM-DD-<topic>-design.md'), explicit output format rules (numbered list, table columns, 200-400 words), and two executable Mermaid procedures — with the minor gap that the actual prompt templates live in reference files rather than inline.	4 / 5
Workflow Clarity	The brainstorming process is clearly sequenced with explicit validation checkpoints (a HARD-GATE, per-section user approval, an Approve decision node) and a revision feedback loop ('User requests revision - revise and re-present'), matching the anchor for clear sequence with feedback loops.	5 / 5
Progressive Disclosure	SKILL.md is a well-structured overview with a dedicated 'Pattern Documentation References' section linking to 7 real one-level-deep reference files; the gap is that 11 of 18 bundle files in references/ are not navigated from the body and the 14-category index is inlined rather than only referenced.	4 / 5
	Total	16 / 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 clearly answers both what the skill does and when to use it with concrete, natural trigger terms. Its main weaknesses are second-person voice and broad, overlapping trigger phrasing that could fire for general coding tasks.

Suggestions

Rewrite in third person (e.g., 'Explores user intent, requirements, and design before implementation...') to remove the second-person specificity penalty.

Narrow the trigger phrasing ('creating features, building components, adding functionality, modifying behavior') to reduce conflict with implementation skills, or scope it explicitly to pre-implementation design/ideation.

Add common synonyms/extensions users might say (e.g., 'brainstorming', 'designing a feature', 'planning') to lift trigger term coverage to 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete trigger actions ('creating features, building components, adding functionality, modifying behavior') and a clear activity ('Explores user intent, requirements, and design'), but the core 'what' is somewhat abstract and second-person voice ('You MUST use this') triggers the -1 specificity penalty from 4 to 3.	3 / 5
Completeness	Explicitly 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... or when users request help with ideation, marketing, and strategic planning') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of natural terms users would say ('creating features', 'building components', 'ideation', 'marketing', 'strategic planning'), with only minor synonym/extension gaps keeping it below 5.	4 / 5
Distinctiveness Conflict Risk	The 'creating features, building components, adding functionality, modifying behavior' triggers are broad and would overlap with most software-development/implementation skills, though the pre-implementation design and ideation/marketing niche provides some distinction.	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: Jamie-BitFlight/claude_skills
Path: plugins/brainstorming-skill/skills/brainstorming-skill/SKILL.md
Commit: c337daf

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