CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

Quality

79%

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

92%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 body is a model instruction-only skill: concrete, quantified, script-level guidance organized into a clearly sequenced five-phase workflow with explicit validation checkpoints and backtracking rules. Its only flaw is a modestly redundant 'Remember' recap section that restates content from the phase sections.

DimensionReasoningScore

Conciseness

The body is lean bullet-point guidance with no explanations of concepts Claude already knows, but the 'Remember' section largely restates phase content ('One question per message during Phase 1', 'Explore 2-3 alternatives before settling', 'Go backward when needed'), which is trimmable redundancy — anchor 4 rather than 5.

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: exact dialogue scripts ('Does this look right so far?', 'Ready to create the implementation plan?'), specific quantities (2-3 approaches, 200-300 word sections), explicit coverage lists (architecture, trade-offs, complexity assessment), and exact handoff paths to sibling skills.

5 / 5

Workflow Clarity

The five phases are clearly sequenced with explicit validation checkpoints (per-section confirmation, affirmative-response gate before planning handoff) and explicit feedback loops for error recovery ('Return to Phase 1/2' with the triggering conditions enumerated), matching the top anchor.

5 / 5

Progressive Disclosure

The body has a clear overview, well-organized sections, and well-signaled one-level-deep references with explicit paths ('.agency/plugins/nori/skills/using-git-worktrees', 'writing-plans'); nothing that belongs in a separate file is inlined, and navigation is easy.

5 / 5

Total

19

/

20

Passed

Description

55%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 what the skill does and includes an explicit when-clause, but its trigger scope ('creating or develop anything') is so broad that it risks firing for nearly every development task, and it misses the most natural keyword ('brainstorm'). The imperative opening voice and a grammar slip ('creating or develop anything') further weaken it.

Suggestions

Rewrite the opening in third-person voice describing capabilities, e.g., 'Refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation', dropping the 'IMMEDIATELY USE THIS SKILL' imperative.

Add the natural trigger terms users would actually say — 'brainstorm', 'brainstorming', 'flesh out an idea', 'explore design options' — and fix the 'creating or develop anything' grammar to 'creating or developing anything'.

Narrow the when-clause to design-refinement contexts, e.g., 'Use when the user has a rough idea to turn into a design before implementation planning', to reduce conflict with coding, planning, and implementation skills.

DimensionReasoningScore

Specificity

The description names the domain and three concrete actions ('structured Socratic questioning, alternative exploration, and incremental validation'), which sits at anchor 4, but the imperative 'IMMEDIATELY USE THIS SKILL' opener is second-person directive voice rather than third person, so the rubric's voice penalty reduces it by 1.

3 / 5

Completeness

It explicitly answers both 'what' ('refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation') and 'when' ('when creating or develop anything and before writing code or implementation plans'), but the when-clause is maximally broad rather than concrete trigger phrases, matching anchor 4.

4 / 5

Trigger Term Quality

It includes some natural phrases ('rough ideas', 'designs', 'writing code', 'implementation plans') but omits the most natural keyword a user would say for this skill — 'brainstorm'/'brainstorming' — plus common variants like 'flesh out an idea' or 'explore options'.

3 / 5

Distinctiveness Conflict Risk

The trigger 'when creating or develop anything and before writing code' would fire for virtually any development task, creating high overlap with planning, design, and implementation skills; the 'IMMEDIATELY USE THIS SKILL' framing amplifies the conflict risk, matching the 'very broad; high overlap risk' anchor.

2 / 5

Total

12

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

microsoft/FluidFramework

Path

.agency/plugins/nori/skills/brainstorming/SKILL.md

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.