CtrlK
BlogDocsLog inGet started
Tessl Logo

brainstorming

IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation

57

Quality

65%

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 ./.agency/plugins/nori/skills/brainstorming/SKILL.md
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 concise, well-structured instruction-only process skill with a clear five-phase workflow, explicit partner-validation checkpoints, and a useful backward-revisit loop. It assumes Claude's competence and avoids over-explanation. The only minor gap is that some validation steps are framed as open questions rather than explicit pass/fail gates.

DimensionReasoningScore

Conciseness

The body is lean and efficient: short phase headers, terse bullet directives ('Ask ONE question at a time', 'Apply YAGNI ruthlessly'), and no padding or explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Most guidance is concrete and executable ('Check current project state in working directory', 'Propose 2-3 different approaches', 'Present in 200-300 word sections', with literal announcement strings to say); it is an instruction-only skill so absence of code is not penalized, but a few bullets stay somewhat high-level ('Gather: Purpose, constraints, success criteria').

4 / 5

Workflow Clarity

The five-phase process is clearly sequenced with explicit validation checkpoints ('Ask after each section: Does this look right so far?', 'When your human partner confirms'), plus a backward-revisit loop section; it is not a 5 because some checkpoints are phrased as questions to the partner rather than explicit pass/fail validation gates.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, it is well-organized into clearly labeled sections (Overview, The Process by phase, When to Revisit, Remember), satisfying the simple-skill exception for a 5; no bundle files exist so there are no nested references to penalize.

5 / 5

Total

18

/

20

Passed

Description

46%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 conveys what the skill does but relies on an all-caps imperative trigger and an overly broad 'creating or develop anything' condition that both weakens natural trigger phrasing and raises conflict risk. It lacks an explicit, well-scoped 'Use when...' clause. Tightening the trigger to specific situations (rough ideas needing refinement, design before implementation) would lift completeness and distinctiveness.

Suggestions

Replace the all-caps 'IMMEDIATELY USE THIS SKILL' directive with a natural third-person 'Use when...' trigger clause naming concrete situations (e.g., 'Use when refining a rough idea into a design before writing an implementation plan').

Narrow the over-broad 'when creating or develop anything' condition to the skill's actual niche so it does not collide with general coding or planning skills.

Use third-person voice consistently and fix the grammatical 'develop' -> 'developing' to keep trigger phrasing natural.

DimensionReasoningScore

Specificity

The description names the domain ('refines rough ideas into fully-formed designs') and a couple of concrete techniques ('structured Socratic questioning, alternative exploration, and incremental validation'), but these are process abstractions rather than the multiple specific concrete actions a score of 4-5 requires; 'creating or develop anything' is itself generic.

3 / 5

Completeness

It clearly states 'what' (refines rough ideas into fully-formed designs via questioning/exploration/validation) but the 'when' is framed as a pushy directive ('IMMEDIATELY USE THIS SKILL when creating or develop anything') rather than an explicit 'Use when...' trigger clause, so per the judging guideline a missing/clear 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

It does include natural user phrasing ('creating or develop anything', 'before writing code or implementation plans'), but it lacks common synonyms and the awkward 'develop' (vs 'developing') plus the all-caps 'IMMEDIATELY USE THIS SKILL' directive weakens the naturalness; some relevant terms are missing.

3 / 5

Distinctiveness Conflict Risk

The trigger 'when creating or develop anything and before writing code or implementation plans' is extremely broad and would overlap with virtually every design, coding, or planning skill, creating high conflict risk; only the 'brainstorming/design' framing gives it slight specificity.

2 / 5

Total

11

/

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
microsoft/FluidFramework
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.