CtrlK
BlogDocsLog inGet started
Tessl Logo

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

64

Quality

76%

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 ./app/skills/brainstorming/SKILL.md
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.

A well-structured, highly actionable process skill with strong workflow clarity and explicit feedback loops. The main weakness is conciseness: the workflow is restated across several sections and some general software-design rationale is included that Claude already knows.

Suggestions

Consolidate the repeated workflow across the Checklist, Process Flow, The Process, After the Design, and Key Principles sections into a single canonical sequence plus the diagram, removing restated principles.

Trim or remove the "Design for isolation and clarity" section, which restates general modularity concepts Claude already knows; keep only any brainstorming-specific guidance.

Verify the referenced files (skills/brainstorming/visual-companion.md and spec-document-reviewer-prompt.md) are present in the bundle, and clearly signal what spec-document-reviewer-prompt.md contains.

DimensionReasoningScore

Conciseness

Mostly actionable process detail, but the workflow is restated across the Checklist, Process Flow diagram, The Process, After the Design, and Key Principles sections, and the "Design for isolation and clarity" section explains general modularity rationale Claude already knows.

3 / 5

Actionability

Provides concrete, executable guidance for an instruction skill: specific output paths ("docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md"), a named subagent dispatch ("spec-document-reviewer"), and copy-paste message templates for the visual-companion offer and user review gate, with only minor gaps.

4 / 5

Workflow Clarity

A clearly sequenced multi-step process with explicit validation checkpoints and feedback loops: per-section user approval, a spec review loop with max 5 iterations and re-dispatch on failure, and a final user review gate, reinforced by a decision-flow diagram.

5 / 5

Progressive Disclosure

Well-structured with section headers and a clearly signaled one-level-deep reference ("read the detailed guide before proceeding: skills/brainstorming/visual-companion.md") that keeps only the offer/decision logic inline; the referenced bundle files are not present in this review bundle, which prevents a top score.

4 / 5

Total

16

/

20

Passed

Description

78%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.

A strong description that clearly states both capability and trigger conditions with concrete, natural phrasing. The only real weakness is the second-person voice ("You MUST use this"), which costs a specificity point under the rubric's voice rule.

DimensionReasoningScore

Specificity

Names the trigger domain with several concrete contexts ("creating features, building components, adding functionality, or modifying behavior") and the skill's actions ("Explores user intent, requirements and design"), but the second-person phrasing "You MUST use this" triggers a 1-point specificity penalty per the voice guideline.

3 / 5

Completeness

Explicitly answers both what ("Explores user intent, requirements and design before implementation") and when ("You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users say ("creating features", "building components", "adding functionality", "modifying behavior") with good coverage, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Carves a clear pre-implementation design/brainstorming niche with explicit hand-off to writing-plans, with only minor overlap risk against adjacent planning skills.

4 / 5

Total

16

/

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
ZHangZHengEric/Sage
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.