CtrlK
BlogDocsLog inGet started
Tessl Logo

brainstorm-refine

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

54

Quality

60%

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 content is a well-structured, actionable orchestration guide with clear phased workflows and explicit exit conditions. Its main weakness is redundancy between the Workflow, Example Flow, and Critical Rules sections, which inflates the token budget without adding guidance.

Suggestions

Merge or trim the 'Example Flow' section, since it duplicates the Workflow and Implementation phases; reference the phases instead of restating them.

Add a concrete Task-tool invocation snippet showing the exact prompt/context payload passed to the brainstorm-refiner agent to push actionability toward fully executable.

Consolidate 'Critical Rules' into the relevant workflow steps rather than a separate restating list to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is mostly efficient and does not over-explain concepts Claude already knows, but the 'Example Flow' section largely restates the Workflow/Implementation steps and the Critical Rules repeat guidance already implied, so it could be tightened, matching the 'mostly efficient but includes some unnecessary explanation' anchor.

3 / 5

Actionability

It gives concrete, executable guidance — `subagent_type=brainstorm-refiner`, specific AskUserQuestion options, a concrete output path `docs/plans/YYYY-MM-DD-<topic>-design.md` — with only minor gaps, fitting the 'mostly executable guidance' anchor; it stops short of 5 because no exact Task-tool invocation snippet is shown.

4 / 5

Workflow Clarity

The three-phase sequence (Initial Exploration, Iteration Loop, Completion) is clearly numbered with explicit exit conditions and a decision graph, matching 'clear sequence with most checkpoints present'; it is not a destructive/batch operation so the validation cap does not apply, but it lacks explicit error-recovery feedback loops that would warrant a 5.

4 / 5

Progressive Disclosure

No bundle files exist, so all content is appropriately inline in a self-contained skill with well-organized sections (Overview, When to Use, Workflow, Implementation, Exit Conditions), matching 'good structure; most content appropriately placed'; the under-50-line 5-exception does not apply since the body exceeds 50 lines.

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 is third-person and states a clear purpose, but it omits any 'when to use' trigger guidance, which caps completeness and limits trigger-term quality. It is specific enough to be distinguishable yet would benefit from explicit trigger phrases.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g., 'Use when developing vague ideas into concrete concepts, evaluating approaches, or sharpening requirements before implementation.'

Include natural synonyms and variations users might say, such as 'flesh out an idea', 'explore options', or 'brainstorm a design'.

Mention the concrete outputs (a design document) to make the 'what' more comprehensive.

DimensionReasoningScore

Specificity

Names the domain ('idea refinement') and a concrete action ('refine ideas through structured brainstorming loops') but offers only one to two actions rather than comprehensive coverage, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

'refine ideas' and 'brainstorming' are natural terms users would say, but common synonyms and variations (e.g., 'flesh out', 'explore', 'flesh out an idea') are missing, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The 'brainstorm-refiner agent' and 'structured brainstorming loops' phrasing carves a clear niche distinct from generic planning skills, with only minor overlap risk, matching the 'mostly distinct' anchor rather than the fully-distinct 5 because it lacks explicit 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fernandezbaptiste/claude-playground-explorer
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.