he-brainstorm

Define problem scope, requirements, and decision options before spec or plan stages. Use when the user has ambiguity in what to build, why it matters, or which direction to choose.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./Plugins/harness-engineering/fixtures/budget-archive/2026-04-21/deferred-store/skills/team_automation/he-brainstorm/SKILL.md

Quality

Content

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

A well-structured, actionable brainstorm skill with a clear sequenced workflow and validation gates, undermined by significant section redundancy and a broken progressive-disclosure layer where most referenced files (including the promised full guide) do not exist in the bundle.

Suggestions

Restore or remove the missing bundle files — at minimum SKILL.full.md and the references/*.md guides the Full Context section links to — since the entry's premise is deferring to a full guide that is currently absent.

Merge the duplicate "Use" and "When to use" sections into one trigger list, and trim the Outputs/Validation/Anti-patterns lists to the essentials to reduce redundancy.

Replace the abstract Examples bullets with one or two worked scenarios showing the actual requirements artifact shape (R IDs, spec_required/risk_level/complexity values) so the guidance is copy-paste-ready.

Dimension	Reasoning	Score
Conciseness	The body is well-sectioned but noticeably redundant — the "Use" and "When to use" sections repeat the same he-spec/he-plan triggers, and Outputs/Validation/Anti-patterns each run long — fitting 'mostly efficient but could be tightened'; not 2 because no concept-explainer padding of things Claude already knows.	3 / 5
Actionability	Concrete, executable guidance pervades the skill: exact enums ("spec_required: none\|lite\|full", "complexity: small\|medium\|large"), a default artifact path, and stable R1/R2 identifier conventions; not 5 because the Examples are abstract scenarios rather than worked, copy-paste-ready samples.	4 / 5
Workflow Clarity	A 13-step sequenced Procedure plus a dedicated Validation checklist with an explicit "Fail fast: stop at first failed gate" gate and a blocker-handling step (12) gives clear sequencing with feedback loops; not 5 because several procedure steps (pressure-test, derive values) rely on implicit rather than inline checkpoints.	4 / 5
Progressive Disclosure	The Full Context section signals ~13 references, but the bundle only contains references/context-preservation.md — SKILL.full.md (the headline 'full guide' the entry defers to), the other references/*.md files, the Infrastructure/ refs, and assets/ are all absent, so the disclosure structure is largely non-navigable; not 1 because the overview itself is lean and appropriately split rather than a monolith.	2 / 5
	Total	13 / 20 Passed

Description

83%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, third-person description that cleanly states both what the skill does and when to use it, with concrete trigger phrasing. It is held back only by not naming the brainstorm vocabulary and the sibling stages that would sharpen distinctiveness.

Suggestions

Add the word 'brainstorm' and its common synonyms ('think through', 'compare directions') to the trigger clause so users who say 'brainstorm' land on this skill.

Name the Harness Engineering sibling stages (he-spec, he-plan) explicitly in the description to reduce overlap risk with those closely related skills.

Dimension	Reasoning	Score
Specificity	"Define problem scope, requirements, and decision options" names the domain plus several concrete actions (scope, requirements, decision options), matching the 'lists several specific actions; minor gaps' anchor; not 5 because the actions are conceptual rather than comprehensively enumerated.	4 / 5
Completeness	It explicitly answers what ("Define problem scope, requirements, and decision options before spec or plan stages") and when ("Use when the user has ambiguity in what to build..."), with concrete trigger phrases, matching the anchor for both clearly and explicitly.	5 / 5
Trigger Term Quality	"Use when the user has ambiguity in what to build, why it matters, or which direction to choose" supplies several natural trigger phrases; not 5 because common synonyms like 'brainstorm', 'compare options', or 'requirements' are absent.	4 / 5
Distinctiveness Conflict Risk	The "before spec or plan" and "ambiguity / which direction to choose" framing carves a distinct brainstorm niche, but it never names the Harness Engineering family, so minor overlap with he-spec/he-plan remains.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 9 missing, 3 deeper-than-1-level, 5 suspicious	Warning

	Total	14 / 16 Passed

Repository: jscraik/Agent-Skills
Path: Plugins/harness-engineering/fixtures/budget-archive/2026-04-21/deferred-store/skills/team_automation/he-brainstorm/SKILL.md
Commit: 2f91362

Reviewed: 1 day 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.