CtrlK
BlogDocsLog inGet started
Tessl Logo

he-brainstorm

Explore Harness Engineering options, filter ornate or weak ideas, recover dropped leverage, and select survivor routes before commitment. Use when intent, stage choice, tradeoffs, idea quality, or possible solution shapes are still unsettled before spec, plan, Linear, or implementation work.

67

Quality

81%

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

70%Weight 40%Scale 1-3

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

A well-structured, well-disclosed skill body with a clear sequenced procedure and validation loops. It leans on contract references and abstract directives that reduce in-place actionability and add cross-reference density.

Suggestions

Inline one or two concrete examples of 'stated facts vs inferred bets vs guesses' output so the procedure is executable without opening references.

Consolidate the long References enumeration and duplicated contract-path mentions to reduce cross-reference overhead in the main body.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, but the 12-step procedure and dense contract-style sections (Stage Arc Boundary, References list of 15+ paths) carry repetition and cross-referencing overhead that could be tightened.

2 / 3

Actionability

Guidance is concrete in places (artifact paths, the validation command `check_bluf_structure.py ... --json`) but most steps are abstract directives ('Separate stated facts', 'Apply the first-principles contract') without executable detail, and many contracts are deferred to references.

2 / 3

Workflow Clarity

The 12-step procedure is clearly sequenced with an explicit Validation section, fail-fast checkpoints, and a validation script invocation with feedback loops for non-trivial artifacts.

3 / 3

Progressive Disclosure

SKILL.md is an overview with well-signaled one-level-deep references (e.g. 'Read when detailed flow is needed: references/brainstorm-workflow-details.md'); referenced files like ideation-mode.md, requirements-artifact-guide.md, and discovery-interview.md all exist in references/.

3 / 3

Total

10

/

12

Passed

Description

92%Weight 40%Scale 1-3

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 description that is specific, complete, and trigger-rich in third person voice. The main weakness is some overlap with sibling HE skills on tradeoff/idea-quality triggers.

Suggestions

Sharpen distinctiveness by binding triggers more tightly to the pre-spec/pre-plan brainstorming stage versus sibling skills like he-spec or he-plan.

Trim the long 'Use when...' clause slightly — it enumerates many conditions, which dilutes the strongest trigger signal.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'Explore Harness Engineering options, filter ornate or weak ideas, recover dropped leverage, and select survivor routes' — these are specific operations, not vague language.

3 / 3

Completeness

Explicitly answers both what ('Explore options, filter ideas, recover leverage, select survivor routes') and when ('Use when intent, stage choice, tradeoffs... are still unsettled before spec, plan, Linear, or implementation').

3 / 3

Trigger Term Quality

Covers natural trigger phrases users would say — 'intent, stage choice, tradeoffs, idea quality' — with good coverage of brainstorming vocabulary.

3 / 3

Distinctiveness Conflict Risk

Niche is fairly specific to HE/brainstorming, but the trigger 'tradeoffs, idea quality' overlaps with general ideation/planning skills and could trigger for related skills.

2 / 3

Total

11

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
jscraik/Agent-Skills
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.