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/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 skill is a well-sequenced, highly actionable facilitation process with excellent workflow clarity and validation gates. Its main weakness is conciseness, with several constraints restated multiple times across sections.

Suggestions

Consolidate the repeated constraints (one question at a time, explicit assumptions, YAGNI) into a single Key Principles section and reference it rather than restating throughout.

Add one short worked example of an Understanding Summary and a Decision Log entry to lift actionability to fully concrete.

Trim redundant emphasis labels ("Mandatory", "Hard Gate", "Non-Negotiable") where the surrounding instruction already enforces the step.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but repeatedly restates the same constraints ("one question at a time", "YAGNI ruthlessly", "assumptions must be explicit", "Mandatory"/"Non-Negotiable" labels) across sections and could be tightened.

3 / 5

Actionability

Provides concrete, specific directives ("one question per message", "5–7 bullets", "200–300 words max", "2–3 viable approaches", exact prompts to ask) with only minor gaps; it lacks worked examples of expected output.

4 / 5

Workflow Clarity

A clearly numbered 7-step process with explicit hard gates (Understanding Lock), confirmation checkpoints, feedback loops (confirm→proceed, continue refinement if unmet), and a complete Exit Criteria checklist.

5 / 5

Progressive Disclosure

Single well-organized file with clear section headers and no nested references; over 50 lines with no external bundle files to navigate, so structure is good but there is no progressive disclosure to reference materials.

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 answers both what and when with mostly concrete triggers and a distinct niche, but its actions remain somewhat abstract and it lacks fuller natural trigger-term coverage. Strengthening the trigger phrasing would lift the weaker dimensions.

Suggestions

Add concrete action verbs and a fuller trigger phrase, e.g. "Transforms vague ideas into validated designs and specs. Use when brainstorming features, architecture, or behavior before implementation."

Include natural synonyms users actually say ("brainstorm", "spec", "design", "plan") to improve trigger-term coverage.

Tighten "creative or constructive work" to more specific, distinguishable triggers that reduce overlap with generic planning skills.

DimensionReasoningScore

Specificity

Names the domain and a couple of actions ("Transforms vague ideas into validated designs", "disciplined reasoning and collaboration") but the actions are abstract rather than a comprehensive concrete list.

3 / 5

Completeness

Clearly states what it does ("Transforms vague ideas into validated designs") and gives an explicit when clause ("Use before creative or constructive work (features, architecture, behavior)") with concrete triggers, though the when could be more specific.

4 / 5

Trigger Term Quality

Includes some relevant natural terms ("features, architecture, behavior", "ideas", "designs") but misses common variations users would say such as "brainstorm", "spec", or "plan".

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (pre-implementation design facilitation) with distinct triggers; only 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.