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.

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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-structured, actionable brainstorming workflow with clear sequencing and explicit validation checkpoints. Its only weakness is mild redundancy between the process description and the Key Principles restatement, which slightly trims conciseness.

DimensionReasoningScore

Conciseness

The body is lean bullet-point prose that assumes Claude's competence and avoids explaining known concepts, with only mild redundancy where the 'Key Principles' section restates points already made in 'The Process' (one question at a time, 2-3 approaches, incremental validation).

4 / 5

Actionability

Concrete, executable guidance throughout: specific numbers ('200-300 words', '2-3 approaches', 'one question per message'), a concrete output path ('docs/plans/YYYY-MM-DD-<topic>-design.md'), and named companion skills to invoke, with only minor gaps in the implementation handoff.

4 / 5

Workflow Clarity

A clearly sequenced multi-step process (Understanding → Exploring approaches → Presenting the design → After the design) with explicit validation checkpoints ('ask after each section whether it looks right so far') and feedback loops ('be ready to go back and clarify').

5 / 5

Progressive Disclosure

A short (~50 line), single-purpose skill with no external bundle files needed; it is well-organized with clear section headers and appropriately signals companion skills, meeting the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

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.

The description clearly states both what the skill does and when to use it, with strong explicit trigger phrases for the creative-work design phase. The main weakness is the second-person 'You MUST use this' voice, which the rubric penalizes, and slightly broad trigger scope that risks minor overlap.

DimensionReasoningScore

Specificity

Names the design domain and lists several specific trigger situations ('creating features, building components, adding functionality, or modifying behavior') plus the action 'Explores user intent, requirements and design', but the second-person 'You MUST use this' triggers the -1 specificity penalty per the rubric.

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...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('creating features', 'building components', 'adding functionality', 'modifying behavior', 'design') that users would actually say, with a few synonyms (e.g. 'brainstorm', 'plan') missing.

4 / 5

Distinctiveness Conflict Risk

Carves a clear pre-implementation design/brainstorming niche distinct from coding skills, though 'any creative work' and 'modifying behavior' are broad enough to create minor overlap with general 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
revokslab/ShipFree
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.