he-compound

Run a bounded Harness Engineering lifecycle across multiple stages. Use when the user wants coordinated brainstorm, spec, plan, work, review, and fix flow rather than one isolated stage.

Quality

72%

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-compound/SKILL.md

Quality

Content

77%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 content is a well-structured, actionable orchestration procedure with strong validation and fail-fast feedback loops. Its main weakness is progressive disclosure: everything is inlined and the referenced asset files are missing.

Suggestions

Move the detailed routing rules and context-disposition policy into a separate reference file linked one level deep from the body to improve progressive disclosure.

Verify and fix the asset links in 'Full Context' — ./assets/icon-small.png and ./assets/icon-large.png do not exist on disk.

Tighten the small overlap between the Procedure, Validation, and Constraints sections to push conciseness toward the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is lean and uses terse bullets and numbered steps with no padding or explanation of concepts Claude already knows; only minor repetition across Procedure, Validation, Constraints, and Anti-patterns keeps it below 5.	4 / 5
Actionability	Provides concrete routing rules, named file contracts ('docs/solutions/', one-file-write), and explicit handoff targets ('skill-refactor', 'skillify', 'he-compound-refresh'); a few steps stay abstract ('Select lifecycle mode using artifact-first evidence') with no code or commands, which is acceptable for an instruction skill but leaves minor gaps.	4 / 5
Workflow Clarity	A clear numbered Procedure (1-9) is paired with an explicit Validation section and a 'Fail fast: stop at first failed gate' feedback loop, including validation before durable artifact writes — explicit checkpoints and error-recovery satisfy the top anchor.	5 / 5
Progressive Disclosure	Section structure is clean, but all guidance is inlined in a single file with no one-level-deep reference files; detailed routing rules and the context-disposition policy could be split out, and the only linked paths (./assets/icon-*.png) do not exist on disk.	3 / 5
	Total	16 / 20 Passed

Description

67%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 capability and an explicit use-trigger, with concrete stage names and a distinctiveness clause. It is held back by project jargon in the trigger and a somewhat abstract 'what'.

Suggestions

Replace or supplement 'Harness Engineering' jargon with natural user-facing phrasing so the trigger reflects what a user would actually say.

Sharpen the 'what' clause with one or two concrete outcomes (e.g., 'routes, executes, and reviews work across stages') instead of the abstract 'bounded lifecycle' framing.

Add common synonyms or variations of the trigger terms to broaden natural-language match coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete actions ('brainstorm, spec, plan, work, review, and fix flow', 'multiple stages'), matching 'lists several specific actions; minor gaps' rather than fully comprehensive coverage of what each stage does.	4 / 5
Completeness	Explicitly answers both 'what' (bounded multi-stage lifecycle) and 'when' via a clear 'Use when...' clause; the 'what' is slightly abstract rather than concrete, keeping it just below the top anchor.	4 / 5
Trigger Term Quality	Includes relevant trigger phrases ('coordinated brainstorm, spec, plan, work, review, and fix flow', 'one isolated stage') but leans on project jargon ('Harness Engineering') that a user would not naturally say, and lacks common synonyms or variations.	3 / 5
Distinctiveness Conflict Risk	The phrase 'rather than one isolated stage' scopes a clear niche distinct from isolated-stage skills, with only minor overlap risk against adjacent Harness Engineering stage skills.	4 / 5
	Total	15 / 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: 2 missing	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-compound/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.