CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brainstorm-refine

Iteratively refine ideas through structured brainstorming loops using the brainstorm-refiner agent

Quality

68%

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

Quality

Content

67%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 orchestration procedure with a genuinely clear iteration loop, explicit exit conditions, and concrete user-interaction details. Its weaknesses are redundant renderings of the same loop (dot graph, phases, example flow, critical rules) and the absence of a concrete prompt template for launching the brainstorm-refiner agent.

Suggestions

Collapse redundancy: drop the dot digraph (Phase 2 already specifies the loop precisely) and fold Critical Rules items 2-3 into their existing sections to remove re-statements of Exit Conditions and Context Accumulation.

Add a concrete example prompt to pass to the brainstorm-refiner agent (idea + accumulated context + requested structured output), so the most important step — launching the agent — is copy-paste ready rather than hinted at.

Add a brief edge-case checkpoint for the iteration loop, e.g. what to do when the agent's output is off-target or the user's choice is ambiguous, to strengthen workflow validation.

DimensionReasoningScore

Conciseness

Bullet-driven and free of explanations of concepts Claude already knows, but the same loop is rendered four times — the dot digraph, Phase 2, the Example Flow, and Critical Rules (which re-state Exit Conditions and Context Accumulation). The redundancy is more than minor trimming, so below anchor 4.

3 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: exact question to ask, labeled AskUserQuestion options, `subagent_type=brainstorm-refiner`, and the output path `docs/plans/YYYY-MM-DD-<topic>-design.md`. The minor gap is that no sample prompt to pass to the brainstorm-refiner agent is given, only 'Request structured output (options, questions, validation)', so not a 5.

4 / 5

Workflow Clarity

Clear phased sequence (Initial Exploration, Iteration Loop, Completion) with an explicit per-iteration checkpoint (user direction), enumerated exit conditions, and defined context accumulation — a genuine feedback loop. Minor validation gaps remain: no handling for unproductive agent responses and no verification step for the written design doc, so not a 5.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is self-contained with well-organized, clearly headed sections; external references (superpowers plugins, brainstorm-challenger) are clearly signaled. The dispensable inline dot graph is the main organization gap keeping it from a 5.

4 / 5

Total

15

/

20

Passed

Description

53%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 communicates a clear and fairly distinct purpose, but it is a 'what'-only description: it lacks any 'Use when...' trigger guidance and misses natural user phrasings for brainstorming/idea refinement. Adding an explicit trigger clause with synonyms would lift both completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause with concrete triggers, e.g. 'Use when the user has a vague idea to develop, wants to flesh out a concept, explore multiple approaches, or sharpen requirements before implementation.'

Include natural trigger synonyms users would actually say — 'flesh out an idea', 'explore approaches', 'develop a concept', 'stuck between options' — to improve trigger-term coverage and distinctiveness.

Mention what the process produces (presented options, challenged assumptions, a written design doc) so the capability list is concrete rather than a single generic action.

DimensionReasoningScore

Specificity

Names the domain (idea refinement) and one action plus a mechanism ('structured brainstorming loops', 'brainstorm-refiner agent'), but coverage is not comprehensive — nothing about what the loops produce (options, challenges, design docs). Sits above anchor 2's generic actions but below anchor 4's several specific actions.

3 / 5

Completeness

The 'what' is clear (iterative idea refinement via agent loops), but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. Not 4 because the 'when' is entirely absent rather than implicit.

3 / 5

Trigger Term Quality

'refine ideas' and 'brainstorming' are natural keywords, but common user phrasings like 'flesh out an idea', 'explore approaches', or 'develop an idea' are missing. Matches the anchor for some relevant keywords missing common variations or synonyms.

3 / 5

Distinctiveness Conflict Risk

The niche of structured iterative brainstorming with a named agent is mostly distinct, with only minor overlap risk against generic ideation/planning skills. Not 5 because 'refine ideas' is broad enough to collide with general planning skills absent disambiguating trigger phrases.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fernandezbaptiste/claude-playground-explorer

Path

brainstorm-refine/SKILL.md

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.