CtrlK
BlogDocsLog inGet started
Tessl Logo

brainstorming

Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.

76

1.66x
Quality

72%

Does it follow best practices?

Impact

93%

1.66x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/brainstorming/SKILL.md

The canonical home for this skill is brainstorming in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 presents a well-sequenced, strongly gated facilitation workflow with genuine validation checkpoints and hard stops — the strongest aspect of this skill. Its weaknesses are repetition between the Purpose, Operating Mode, and Key Principles sections, a filler 'When to Use' section, and moderate length that could be tightened or partly offloaded to reference files.

Suggestions

Delete or rewrite the empty 'When to Use' section ('This skill is applicable to execute the workflow or actions described in the overview.') with real trigger conditions, and merge the dangling 'multi-agent-brainstorming' handoff paragraph into a proper section — this would raise both conciseness and progressive_disclosure.

Deduplicate content repeated across Purpose, Operating Mode, and Key Principles (e.g. 'One question at a time' and 'YAGNI ruthlessly' each appear twice), keeping each principle in exactly one place.

Add one short example of a well-formed multiple-choice clarifying question and a sample Decision Log entry to make the strongest instructions copy-paste ready and lift actionability toward 5.

DimensionReasoningScore

Conciseness

The process guidance is mostly tight, but there is noticeable redundancy: the 'Operating Mode' section restates the Purpose, 'Key Principles (Non-Negotiable)' duplicates rules already stated in the steps ('One question at a time', 'YAGNI ruthlessly' each appear twice), and the closing 'When to Use' section is a contentless filler sentence. This matches anchor 3 (mostly efficient but includes some unnecessary explanation or could be tightened) rather than 4.

3 / 5

Actionability

The body gives concrete, executable directives throughout — 'Ask one question per message', 'Prefer multiple-choice questions', 'a concise summary (5-7 bullets)', 'Propose 2-3 viable approaches', sections of '200-300 words max', plus verbatim prompts to ask at each checkpoint. For an instruction-only skill this is mostly executable guidance with minor gaps (e.g. no example of a well-formed multiple-choice question), matching anchor 4 rather than 5.

4 / 5

Workflow Clarity

A clearly numbered 7-step process with explicit validation checkpoints and feedback loops: a mandatory context review first, the Understanding Lock hard gate with a verbatim confirmation prompt ('Do NOT proceed until explicit confirmation is given'), incremental validation after each design section ('Does this look right so far?'), a mandated Decision Log, exit criteria with hard stop conditions, and 'Be willing to go back and clarify'. This matches anchor 5 (clear sequence, explicit validation steps, feedback loops, checklists).

5 / 5

Progressive Disclosure

No bundle files exist, so the body is evaluated on its own structure: clean section headers, a clearly signaled handoff to the 'multi-agent-brainstorming' skill, and no monolithic walls or buried references. However, at ~230 lines with self-contained checklists (non-functional requirements, decision log format) that could be split into reference files, plus an oddly placed dangling paragraph before 'When to Use', this matches anchor 4 (good structure, minor organization gaps) rather than 5.

4 / 5

Total

16

/

20

Passed

Description

58%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 correctly uses third person, states both what the skill does and when to use it, and anchors itself to a design phase before implementation. Its weaknesses are vague capability language ('disciplined reasoning and collaboration'), missing natural trigger words like 'brainstorm' or 'design', and a broad 'creative or constructive work' trigger that risks overlap with other planning skills.

Suggestions

Add natural trigger phrases users would actually say, e.g. 'Use when the user wants to brainstorm, explore approaches, or turn a rough idea into a design before coding' — this would lift both trigger_term_quality and completeness.

Replace the abstract 'through disciplined reasoning and collaboration' with the skill's concrete mechanisms, e.g. 'asks clarifying questions one at a time, proposes 2-3 design approaches, and maintains a decision log' to raise specificity.

Narrow the trigger scope (e.g. tie it to design/brainstorming work rather than all 'creative or constructive work') to reduce conflict risk with general planning or architecture skills.

DimensionReasoningScore

Specificity

The description names the domain ('creative or constructive work (features, architecture, behavior)') and one concrete transformation ('Transforms vague ideas into validated designs'), but 'disciplined reasoning and collaboration' is generic filler and there is no list of several specific actions, matching anchor 3 rather than 4.

3 / 5

Completeness

Both 'what' ('Transforms vague ideas into validated designs through disciplined reasoning and collaboration') and 'when' ('Use before creative or constructive work (features, architecture, behavior)') are present in third-person voice, but the 'when' clause could be more explicit with concrete trigger phrases like 'when the user wants to brainstorm or design a new feature', matching anchor 4 rather than 5.

4 / 5

Trigger Term Quality

'features, architecture, behavior' are relevant keywords, but the natural phrases a user would actually say — 'brainstorm', 'design', 'explore approaches', 'flesh out an idea' — are absent, so coverage matches anchor 3 (some relevant keywords, missing common variations).

3 / 5

Distinctiveness Conflict Risk

'Creative or constructive work (features, architecture, behavior)' is a broad trigger that could overlap with general planning, architecture, and code-review skills; it is somewhat specific but matches anchor 3 (could still overlap with similar skills) rather than 4.

3 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.