brainstorm-solution

Structured brainstorming for technical solutions

Install with Tessl CLI

npx tessl i github:jpoutrin/product-forge --skill brainstorm-solution

What are skills?

Overall
score

61%

Review — 46%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

15%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague to be useful for skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient specificity to distinguish it from general technical assistance skills. The description would benefit significantly from listing specific brainstorming techniques and clear usage triggers.

Suggestions

Add a 'Use when...' clause specifying triggers like 'exploring options', 'comparing approaches', 'need ideas for', 'architecture decisions', or 'design alternatives'

List specific concrete actions the skill performs, such as 'generates multiple solution options, creates comparison matrices, identifies tradeoffs, structures pros/cons analysis'

Narrow the scope by specifying what types of technical solutions (e.g., 'software architecture', 'system design', 'API design') to reduce conflict with other technical skills

Dimension	Reasoning	Score
Specificity	The description uses vague language ('structured brainstorming') without listing any concrete actions. It doesn't specify what kind of technical solutions or what the skill actually does (e.g., generate options, compare tradeoffs, create diagrams).	1 / 3
Completeness	The description only vaguely addresses 'what' (brainstorming) and completely lacks any 'when' guidance. There is no 'Use when...' clause or explicit trigger guidance.	1 / 3
Trigger Term Quality	'Brainstorming' and 'technical solutions' are somewhat natural terms users might say, but the description lacks common variations like 'ideation', 'problem solving', 'architecture options', 'design alternatives', or specific technical domains.	2 / 3
Distinctiveness Conflict Risk	'Technical solutions' is extremely broad and could conflict with many skills covering coding, architecture, debugging, design, or any problem-solving task. Nothing distinguishes this from general technical assistance.	1 / 3
	Total	5 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill with excellent actionability and workflow clarity, providing Claude with concrete instructions for running an interactive brainstorming session. The main weaknesses are moderate verbosity (some content could be tightened) and the monolithic structure that could benefit from splitting detailed templates and prompts into separate files.

Suggestions

Consider moving section-specific prompts (Data Models, System Components, etc.) to a separate PROMPTS.md reference file to reduce main skill length

Condense the interactive menu examples - show one complete example rather than repeating similar patterns for each section

Dimension	Reasoning	Score
Conciseness	The skill is moderately verbose with some repetition between the usage examples and execution instructions. The section-specific prompts and interactive menu details could be more condensed, though most content is necessary for the complex workflow.	2 / 3
Actionability	Provides concrete, executable guidance with specific directory structures, exact menu formats, file naming conventions, and complete markdown templates. Claude can follow these instructions directly without ambiguity.	3 / 3
Workflow Clarity	Clear 10-step numbered sequence with explicit checkpoints (parse args → initialize → create directory → interactive flow → completion). Includes error handling section and auto-save progress as validation mechanisms.	3 / 3
Progressive Disclosure	Content is well-structured with clear sections, but everything is in a single monolithic file. The section-specific prompts and template details could be split into separate reference files for better organization.	2 / 3
	Total	10 / 12 Passed

Validation

91%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.