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.

77

1.66x
Quality

68%

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 is a well-sequenced, highly actionable facilitation process with strong validation gates and checklists, scoring high on workflow clarity and actionability. Its main weakness is redundancy across the Purpose, Operating Mode, and Key Principles sections that inflates token usage without adding guidance.

Suggestions

Remove or compress the 'Key Principles (Non-Negotiable)' section, since each principle already appears in its corresponding step; keep at most a one-line cross-reference if any.

Merge the 'Purpose' prevention list and the 'Operating Mode' restriction list into a single 'Mode & Constraints' section to eliminate overlapping restatements of 'no premature implementation / no silent assumptions'.

Convert 'Explain trade-offs clearly' into a concrete prompt or checklist (e.g. 'state complexity, extensibility, risk, and maintenance impact for each approach').

DimensionReasoningScore

Conciseness

Mostly efficient and free of basic-concept over-explanation, but the 'Key Principles (Non-Negotiable)' section restates rules already given in steps 2/3/5/6 and 'Operating Mode' overlaps 'Purpose', adding redundant tokens.

3 / 5

Actionability

Provides concrete directives ('one question per message', '2–3 viable approaches', '200–300 words max') and copy-paste prompt templates plus an Exit Criteria checklist, though some guidance like 'Explain trade-offs clearly' stays abstract.

4 / 5

Workflow Clarity

Seven clearly numbered steps are sequenced with an explicit validation gate (Understanding Lock, 'Do NOT proceed until explicit confirmation'), a feedback loop (unmet criteria → continue refinement), and an Exit Criteria checklist.

5 / 5

Progressive Disclosure

No bundle files exist; the body is well-sectioned with clear headers and one clearly signaled cross-skill reference (multi-agent-brainstorming), but at ~220 lines it exceeds the simple-skill threshold that would allow a 5 on structure alone.

4 / 5

Total

16

/

20

Passed

Description

62%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 clearly states both purpose and trigger condition in third person, but its trigger vocabulary misses the most natural user terms ('brainstorm', 'design', 'plan') and the 'when' clause could be more concrete. It is solid but not exemplary.

Suggestions

Add natural trigger terms users would actually say — e.g. 'Use when brainstorming a feature, designing architecture, or planning new behavior before implementation.'

Replace the generic 'disciplined reasoning and collaboration' with a more concrete action verb or two (e.g. 'asks one question at a time, surfaces assumptions, and locks understanding before design').

Tighten the 'when' with concrete triggers: 'Use when the user wants to brainstorm, explore approaches, or turn a vague idea into a design.'

DimensionReasoningScore

Specificity

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, so coverage is not comprehensive.

3 / 5

Completeness

Explicitly answers both what ('Transforms vague ideas into validated designs…') and when ('Use before creative or constructive work…') with an explicit trigger clause, but the 'when' lacks concrete 'when the user mentions…' phrasing.

4 / 5

Trigger Term Quality

Includes relevant keywords ('features, architecture, behavior', 'creative or constructive work') but omits the natural terms users actually say such as 'brainstorm', 'design', or 'plan'.

3 / 5

Distinctiveness Conflict Risk

The 'validated designs before implementation' framing carves a fairly distinct niche, though the broad 'creative or constructive work' trigger carries minor overlap risk with general planning or design skills.

4 / 5

Total

14

/

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.

Validation15 / 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.