brainstorming

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/brainstorming/SKILL.md

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 content is a well-sequenced facilitation process with strong validation gates and exit criteria, losing points mainly to redundant restatements of the same principles and the absence of a worked dialogue example.

Suggestions

Remove the "Key Principles (Non-Negotiable)" section or fold it into the steps, since each principle is already stated inline where it applies, to cut repeated tokens.

Add one short worked example dialogue showing the one-question-at-a-time flow and the Understanding Lock confirmation, to make the abstract process concrete.

Tighten vague directives like "Review the current project state (if available)" into a concrete checklist of what to look for.

Dimension	Reasoning	Score
Conciseness	The body is mostly purposeful process guidance, but the "Key Principles (Non-Negotiable)" section repeats rules already stated inline (one question at a time, explicit assumptions, explore alternatives, YAGNI), and the Purpose/Operating Mode bullets overlap with later steps.	3 / 5
Actionability	For an instruction-only skill the guidance is concrete and specific — "Ask one question per message", "2-3 viable approaches", "200-300 words max", explicit gates — with only minor vagueness such as "Review the current project state".	4 / 5
Workflow Clarity	A clearly sequenced 7-step process with hard validation gates (Understanding Lock requiring explicit confirmation, Exit Criteria hard stop) and an explicit feedback loop ("If any criterion is unmet: Continue refinement").	5 / 5
Progressive Disclosure	No bundle files exist and the skill is self-contained with well-organized one-level sections; it is over 50 lines so the simple-skill exception does not apply, but structure is good with only minor length/organization gaps.	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 an explicit trigger clause and stays in third person, but its action list is thin and its trigger vocabulary lacks the most natural synonyms a user would say.

Suggestions

Replace abstract method language ("disciplined reasoning and collaboration") with 2-3 concrete actions, e.g. "Surfaces assumptions, proposes 2-3 design approaches, and records a decision log."

Add natural trigger terms users actually say, such as "brainstorm", "design", "spec", or "requirements", alongside the existing "features, architecture, behavior".

Tighten the "when" clause from "creative or constructive work" to a sharper trigger like "Use before designing features, architecture, or behavior changes."

Dimension	Reasoning	Score
Specificity	It names the domain ("creative or constructive work (features, architecture, behavior)") and one concrete action ("Transforms vague ideas into validated designs"), but "disciplined reasoning and collaboration" is abstract method rather than a list of concrete capabilities.	3 / 5
Completeness	It has a clear "what" ("Transforms vague ideas into validated designs...") and an explicit "Use before..." trigger clause, so the missing-trigger cap at 3 does not apply; the "when" is present but somewhat broad.	4 / 5
Trigger Term Quality	Phrases like "creative or constructive work", "features, architecture, behavior", and "vague ideas" are relevant, but common natural synonyms users would say ("brainstorm", "design", "spec") are missing.	3 / 5
Distinctiveness Conflict Risk	The pre-implementation design-facilitation niche is mostly distinct, though "constructive work" is broad enough to create minor overlap with general planning or design skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/brainstorming/SKILL.md
Commit: b1aebac

Reviewed: ~18 hours ago

Table of Contents

Discovery Implementation Validation

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.