CtrlK
BlogDocsLog inGet started
Tessl Logo

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 research-validated prompt patterns.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 excels at workflow clarity and progressive disclosure, with an authoritative sequenced procedure and well-organized one-level references. It is weaker on conciseness (workflow is duplicated in prose and diagram) and actionability (the prompt templates that drive the skill live only in reference files).

Suggestions

Collapse the duplication between the 6-step numbered workflow and the Phase 1-3 Mermaid diagram — keep the authoritative diagram and trim the prose list to the phase labels, or vice versa.

Inline one or two concrete prompt templates (e.g., one Perspective Multiplication and one Inversion example) so the body is self-contained for the most common cases before pointing to references.

DimensionReasoningScore

Conciseness

Mostly efficient with no padding of concepts Claude already knows, but the numbered 6-step workflow and the Phase 1-3 Mermaid diagram state nearly the same procedure twice, a real redundancy beyond minor over-explanation.

3 / 5

Actionability

Concrete workflow steps and a named output path are provided, but the core executable content (the actual prompt templates) is deferred to reference files rather than included inline, leaving key details absent from the body.

3 / 5

Workflow Clarity

A clearly sequenced workflow is given both as a numbered list and an authoritative Mermaid diagram with an explicit approval decision branch and a revision feedback loop (re-present on revision).

5 / 5

Progressive Disclosure

The body is a clear overview with seven well-labeled, one-level-deep references to real reference files (all verified to exist), with the bulk pattern detail appropriately split out for easy navigation.

5 / 5

Total

16

/

20

Passed

Description

81%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 highly specific and fully answers what and when, with strong natural trigger terms. Its main weakness is distinctiveness: the broad 'creative work / adding functionality' triggers risk colliding with generic implementation and content skills.

Suggestions

Narrow the 'when' triggers toward design/ideation-specific phrasing (e.g., 'brainstorming', 'design exploration', 'defining requirements') to reduce overlap with generic implementation skills.

Lead with the distinguishing action ('Explores and structures ideas and designs before implementation') so the skill's niche is clear before the broad trigger list.

DimensionReasoningScore

Specificity

Lists multiple distinct concrete actions — 'creating features, building components, adding functionality, modifying behavior' plus 'Explores user intent, requirements, and design' — giving comprehensive coverage of its domain.

5 / 5

Completeness

Explicitly answers both what ('Explores user intent, requirements, and design before implementation using research-validated prompt patterns') and when ('before any creative work... or when users request help with ideation, marketing, and strategic planning') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural trigger coverage ('creating features', 'building components', 'ideation', 'marketing', 'strategic planning') but missing common synonyms such as 'brainstorming' itself.

4 / 5

Distinctiveness Conflict Risk

Triggers like 'adding functionality', 'modifying behavior', and 'marketing' are very broad and overlap heavily with general implementation and content skills, giving high conflict risk despite the 'before/brainstorm' framing.

2 / 5

Total

16

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Jamie-BitFlight/claude_skills
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.