brainstorm

Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes

Quality

71%

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/sdd/skills/brainstorm/SKILL.md

Quality

Content

71%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 well-structured and actionable with a clear phased workflow and concrete numeric guidance for approach generation. Its main weakness is redundancy between 'The Process' and 'Key Principles' sections, which inflates token usage without adding information.

Suggestions

Merge or trim 'Key Principles' to remove items already stated in 'The Process' (one question at a time, multiple choice, explore alternatives, incremental validation, be flexible).

Resolve the inconsistency between 'Generate 6 possible approaches' (Process) and 'Always propose 2-3 approaches before settling' (Principles) so the guidance agrees.

Add an explicit error-recovery/revision loop note for the design-presentation phase to push workflow clarity to the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and avoids explaining concepts Claude already knows, but the 'Key Principles' section largely restates 'The Process' (one question at a time, multiple choice, explore alternatives, incremental validation, be flexible), adding redundant tokens.	3 / 5
Actionability	Concrete, executable guidance throughout: 'Generate 6 possible approaches... numeric probability', 'first 3 over 0.80', 'last 3 less than 0.10', 'sections of 200-300 words', and a specific post-design workflow ('/clear' then '/plan-task <task-file-path>').	4 / 5
Workflow Clarity	A clear four-phase sequence (Understanding → Exploring → Presenting → After) with validation checkpoints ('checking after each section whether it looks right') and a feedback loop ('go back and clarify'), though without an explicit error-recovery checklist.	4 / 5
Progressive Disclosure	A single-file skill under 50 lines with no external references needed and well-organized sections (Overview, The Process, After the Design, Key Principles), meeting the simple-skill exception for a top score.	5 / 5
	Total	16 / 20 Passed

Description

71%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, explicitly stating both what the skill does and when to use it (including a negative trigger). It is somewhat weaker on trigger-term naturalness and action specificity, leaning on process language rather than crisp concrete operations.

Suggestions

Add the natural keyword 'brainstorm' (and synonyms like 'idea' or 'spec') to the description so users' actual phrasing matches the trigger.

Replace abstract process terms ('alternative exploration', 'incremental validation') with more concrete deliverable actions to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the design domain and several mechanisms ('collaborative questioning, alternative exploration, and incremental validation'), but these read as process framing rather than crisp concrete capabilities, so coverage is not comprehensive.	3 / 5
Completeness	Explicitly answers both 'what' ('refines rough ideas into fully-formed designs...') and 'when' ('Use when creating or developing, before writing code...'), plus a negative trigger ('Don't use during clear mechanical processes').	5 / 5
Trigger Term Quality	Includes relevant phrases like 'creating or developing', 'rough ideas', and 'designs', but omits the most natural trigger term ('brainstorm') and common synonyms a user would actually say.	3 / 5
Distinctiveness Conflict Risk	The pre-implementation ideation niche and explicit 'Don't use during mechanical processes' carve a clear boundary, leaving only minor overlap risk with general planning/design skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: NeoLabHQ/context-engineering-kit
Path: plugins/sdd/skills/brainstorm/SKILL.md
Commit: 8539779

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