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.

Quality

88%

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

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, highly actionable, and well-structured with a clear multi-step workflow and explicit validation checkpoints. As a compact, single-purpose instruction skill it appropriately needs no external bundle files and is well organized.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient, assumes Claude's competence, and contains no concept-explaining filler, matching the anchor for a lean, every-token-earns-its-place document.	3 / 3
Actionability	It provides concrete executable guidance such as 'Ask questions one at a time', 'present the design in small sections (200-300 words)', and a specific output path 'docs/plans/YYYY-MM-DD-<topic>-design.md', giving copy-paste-ready instruction.	3 / 3
Workflow Clarity	A clear sequence is laid out (understand idea → explore approaches → present design → document/implementation) with explicit validation checkpoints ('Ask after each section whether it looks right so far') and a feedback loop ('Be ready to go back and clarify').	3 / 3
Progressive Disclosure	The skill is under 50 lines with no need for external references, yet is well-organized into clearly labeled sections, meeting the simple-skills criterion for top progressive disclosure scoring.	3 / 3
	Total	12 / 12 Passed

Description

77%

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 states both what the skill does and when to use it with a concrete action list, making it strong on specificity and completeness. It is weakened slightly by somewhat abstract trigger phrasing ('creative work') and broad triggers that could overlap with related skills.

Suggestions

Replace or augment 'creative work' with natural user phrasings like 'brainstorming', 'designing a feature', or 'planning implementation' to improve trigger term quality.

Narrow the trigger scope so it is less likely to fire for routine code edits — emphasize the upfront design/exploration intent distinct from general feature-building skills.

Consider adding a few explicit example trigger phrases a user would naturally say to boost distinctiveness and trigger coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ('creating features, building components, adding functionality, or modifying behavior') and a specific activity ('Explores user intent, requirements and design'), matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	It explicitly answers both 'what' ('Explores user intent, requirements and design before implementation') and 'when' ('You MUST use this before any creative work'), matching the anchor that clearly answers both with explicit triggers.	3 / 3
Trigger Term Quality	It offers relevant triggers ('creating features', 'building components', 'adding functionality') but leans on the abstract phrase 'creative work' and omits common natural phrasings users would say like 'brainstorm', 'design', or 'plan a feature', so it falls short of full coverage.	2 / 3
Distinctiveness Conflict Risk	The skill has a recognizable niche (pre-implementation brainstorming/design), but the broad triggers 'creative work' and 'adding functionality' could overlap with general coding or design skills, keeping it at the 'somewhat specific but could overlap' anchor rather than the clearly distinct top level.	2 / 3
	Total	10 / 12 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: revokslab/ShipFree
Path: .cursor/skills/brainstorming/SKILL.md
Commit: 67b7e3a

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