CtrlK
BlogDocsLog inGet started
Tessl Logo

brainstorming

IMMEDIATELY USE THIS SKILL before answering any task - internal design thinking that identifies the question type, selects applicable skills, and converges on the best approach before implementation

54

Quality

60%

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 ./.claude/skills/brainstorming/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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-structured, actionable reasoning workflow with clear sequencing and explicit verification checkpoints; its main weakness is mild verbosity in the template sections.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept-padding Claude already knows, but the large Phase 4 template block and repeated templated phrases could be tightened.

2 / 3

Actionability

Concrete, specific guidance for an instruction-only skill — numbered phases, explicit checklists, and a copy-paste-ready Analysis Plan template; absence of code is acceptable here.

3 / 3

Workflow Clarity

A clear six-phase sequence with explicit validation checkpoints (Phase 5 verify, Phase 6 MANDATORY pre-output verification) and a feedback loop ("If ANY check fails → re-verify").

3 / 3

Progressive Disclosure

A single self-contained file with well-organized sections and no nested references; no bundle files exist to misorganize.

3 / 3

Total

11

/

12

Passed

Description

42%

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 names concrete actions but frames itself as an always-on mandate rather than a distinct, user-triggered skill, which hurts trigger quality, completeness, and conflict risk.

Suggestions

Add an explicit, natural "Use when..." trigger (e.g., the user asks for a complex multi-step task) and remove the always-on 'IMMEDIATELY USE THIS SKILL' framing.

Add concrete user-facing keywords (e.g., "design thinking", "plan an approach", "pick a strategy") so the skill triggers on natural phrasing.

Narrow the trigger to distinguish it from other skills and reduce conflict risk — currently it would fire on every task.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions ("identifies the question type, selects applicable skills, and converges on the best approach") rather than vague language.

3 / 3

Completeness

It states what the skill does, but lacks a proper "Use when..." trigger clause; instead it mandates use before any task, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

The trigger "IMMEDIATELY USE THIS SKILL before answering any task" is an instruction to Claude, not natural keywords a user would say; there are no user-facing trigger terms.

1 / 3

Distinctiveness Conflict Risk

Claiming to apply "before answering any task" makes it conflict with virtually every other skill, the maximum conflict-risk case.

1 / 3

Total

7

/

12

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
sentient-agi/EvoSkill
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.