CtrlK
BlogDocsLog inGet started
Tessl Logo

ce-brainstorm

Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm, scope what to build, or needs collaborative product framing before planning. Also use when they must scope work in territory they do not know, or ask for a blindspot pass. Not for executing already-specified work — implementation, debugging, or code review with no product scope left to decide. Not for a verdict on whether to adopt or switch to a named external technology, library, or platform; that is ce-pov.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 overview that delegates detail to real, one-level-deep reference files and sequences a multi-phase workflow with validation checkpoints. It is efficient and actionable, with mild tightening possible around restated conventions and indirect delegation.

DimensionReasoningScore

Conciseness

Dense and assumes Claude's competence with no basic-concept padding, but the done-bar and config-layer conventions are restated several times and could be tightened.

4 / 5

Actionability

Provides concrete, specific guidance (explicit artifact paths, frontmatter keys, per-phase file-read directives), though much of it delegates to reference files rather than giving fully inline executable steps.

4 / 5

Workflow Clarity

Clear Phase 0.0-4 sequence with a 'Read first' table per phase and explicit validation gates (Ready for Planning Check, 'do not declare it written while any check fails'), with only minor checkpoint gaps.

4 / 5

Progressive Disclosure

The body is a concise overview pointing to well-signaled one-level-deep references under references/ and scripts/, all of which exist on disk, with easy navigation and no nested-reference chains.

5 / 5

Total

17

/

20

Passed

Description

87%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 explicit positive triggers and negative boundaries that distinguish it from sibling skills. It is mostly specific and well-triggered, with only minor jargon and abstractness in the product-framing domain.

DimensionReasoningScore

Specificity

Names several concrete actions ('Explore...ideas into a right-sized requirements-only unified plan', 'brainstorm, scope what to build', 'collaborative product framing') with only minor coverage gaps, though the product-framing domain is somewhat abstract.

4 / 5

Completeness

Explicitly answers both what (explore ideas into a unified plan) and when (multiple 'Use when...' trigger phrases plus explicit 'Not for...' exclusions) with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Includes natural user phrases like 'brainstorm' and 'scope what to build' and 'blindspot pass', but leans on some jargon ('collaborative product framing') and is missing a few common synonyms.

4 / 5

Distinctiveness Conflict Risk

Clear niche (product brainstorming/scoping pre-planning) with explicit routing away from siblings ('Not for...code review', 'that is ce-pov'), giving minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
EveryInc/compound-engineering-plugin
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.