CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

71%

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 ./claude/skills/brainstorming/SKILL.md
SKILL.md
Quality
Evals
Security

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 a well-structured, actionable instruction-only process with clear sequencing and incremental validation, weakened mainly by a redundant Key Principles section and the lack of worked examples.

Suggestions

Remove or de-duplicate the "Key Principles" section, since four of its bullets already appear verbatim in "The Process", to tighten conciseness.

Add one short worked example of a multiple-choice refining question and one of a 200-300 word design section to lift actionability.

Make the per-section validation step more explicit (e.g. a concrete checkpoint phrasing) to push workflow clarity toward 5.

DimensionReasoningScore

Conciseness

Mostly efficient bullet points, but the "Key Principles" section largely restates points already in "The Process" (one question at a time, multiple choice, explore alternatives, incremental validation), which is redundant padding fitting anchor 3 rather than 4.

3 / 5

Actionability

Concrete specific guidance throughout ("one question at a time", "2-3 approaches with trade-offs", "200-300 word sections", "ask after each section"), but no worked examples of a multiple-choice question or a sample design section, so anchor 4 fits better than 5.

4 / 5

Workflow Clarity

Clear sequence (understand -> explore approaches -> present in sections -> document -> implement) with per-section validation checkpoints and a go-back feedback loop, but the validation is light ("whether it looks right") rather than explicit, fitting anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Under ~50 lines, single-purpose, no bundle files, and well-organized with clear sections, so the simple-skill exception applies and progressive disclosure scores 5 on well-organized sections alone.

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 with explicit what-and-when trigger guidance, but is held back by moderate specificity and trigger-term coverage that omits the most natural brainstorming/design synonyms.

Suggestions

Add natural trigger synonyms users would actually say (e.g. "brainstorm", "design", "plan a feature") alongside the current "creating features / building components" list.

Name a couple more concrete actions the skill performs (e.g. "proposes 2-3 design approaches", "writes the validated design to a plan") to lift specificity beyond a single action.

Sharpen the niche wording to reduce overlap with the related planning skill, e.g. frame it as upfront design exploration distinct from implementation planning.

DimensionReasoningScore

Specificity

Names the design domain and one core action ("Explores user intent, requirements and design") but lists trigger contexts rather than multiple concrete actions the skill performs, fitting anchor 3 rather than 4.

3 / 5

Completeness

Explicitly answers both what ("Explores user intent, requirements and design before implementation") and when with concrete trigger phrases ("MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior"), matching anchor 5; trigger guidance is present so no cap at 3 applies.

5 / 5

Trigger Term Quality

Natural phrases like "creating features" and "building components" appear, but the most natural synonyms for a brainstorming skill ("brainstorm", "design", "plan an idea") are missing, so anchor 3 fits better than 4.

3 / 5

Distinctiveness Conflict Risk

Clear design-before-implementation niche with mostly distinct triggers, but real overlap risk with the closely related planning skill referenced in the body, fitting anchor 4 rather than 5.

4 / 5

Total

15

/

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
joshmanders/dotfiles
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.