CtrlK
BlogDocsLog inGet started
Tessl Logo

trellis-brainstorm

Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.

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

73%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 well-structured, actionable planning skill with an explicit gated workflow and validation checklist. Its main weakness is the first-principles teaching section, which over-explains a known concept and slightly inflates the token budget.

Suggestions

Condense or remove the "Thinking Framework: First Principles Analysis" section, or move it to a reference file, since first-principles reasoning is already within Claude's competence.

Add one or two more concrete command examples (e.g., seeding design.md/implement.md or an example PRD skeleton) to lift actionability from procedural to fully copy-paste ready.

Trim redundant framing lines such as "This is mandatory" and "This is not optional cleanup" where the imperative already conveys the requirement.

DimensionReasoningScore

Conciseness

The bulk is lean and actionable, but the "Thinking Framework: First Principles Analysis" section (fundamental-truths table, Bad/Good restating) spends tokens teaching a concept Claude already knows and could be tightened.

3 / 5

Actionability

It provides a copy-paste `task.py create` command, concrete artifact filenames, an explicit per-question structure, and a lossless convergence procedure, though only one runnable command is shown and the rest is procedural guidance.

4 / 5

Workflow Clarity

A clearly sequenced numbered Planning Flow is gated by an explicit PRD Convergence Pass (with a read-through verify loop) and a Quality Bar checklist before `task.py start`, giving feedback loops and validation checkpoints.

5 / 5

Progressive Disclosure

Sections are well-organized with clear `##` headers in a single file with no bundle references, but the sizable inline first-principles teaching block could arguably be split into a separate reference.

4 / 5

Total

16

/

20

Passed

Description

88%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.

A strong, specific description that clearly covers both capabilities and explicit use-when triggers with mostly natural language. Its only weakness is modest overlap risk from broadly applicable trigger terms and a few missing common synonyms.

DimensionReasoningScore

Specificity

"Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope" lists multiple specific concrete actions with comprehensive coverage.

5 / 5

Completeness

It explicitly states both what it does (requirements discovery, PRD seeding, scoped questioning) and when to use it via a concrete "Use when..." clause with multiple trigger conditions.

5 / 5

Trigger Term Quality

Triggers like "requirements are unclear", "multiple valid approaches", "new feature", and "complex task" are natural user phrases, but common synonyms such as "brainstorm" or "spec out" are missing.

4 / 5

Distinctiveness Conflict Risk

The Trellis/PRD framing gives it a clear planning niche, but broad triggers like "new feature" and "complex task" leave minor overlap risk with other planning or requirements skills.

4 / 5

Total

18

/

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
EcoPasteHub/EcoPaste
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.