CtrlK
BlogDocsLog inGet started
Tessl Logo

he-compound-refresh

Analyze and validate compound Harness Engineering run state, blockers, validation status, and Linear context. Use when lifecycle runs drift, gates fail, blockers appear, or compound work needs refresh.

65

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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-refresh/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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-organized, concise instruction skill with a clear sequenced workflow and validation checkpoints. It loses points on actionability (no executable commands) and progressive disclosure (the referenced bundle files do not exist in the skill directory).

Suggestions

Provide at least one concrete executable command or invocation example in the Procedure (e.g., the exact session-collector command or a validation command) to lift actionability toward 4-5.

Either create the referenced references/session-evidence-contract.md and assets/icon-small.png / icon-large.png bundle files, or remove the broken links so navigation targets are real.

Inline the one or two most-used validation/inspection commands rather than only describing them as 'smallest safe live-state checks', so the workflow's checkpoints become runnable.

DimensionReasoningScore

Conciseness

Lean bullet-driven body with no padding or explanation of concepts Claude already knows; every section (Philosophy, Failure Modes, Procedure, Validation) earns its place.

5 / 5

Actionability

Concrete enumeration of targets, outcomes, and mode normalization is actionable, but the procedure is instruction-level with no executable commands, code, or exact validation invocations beyond the one session-collector reference.

3 / 5

Workflow Clarity

An 8-step sequenced procedure with a dedicated Validation section and an explicit 'Fail fast: stop at first failed gate' checkpoint, though validation steps are described rather than given as runnable commands.

4 / 5

Progressive Disclosure

The body references a session-evidence-contract.md at ../../../references/ and two asset icons, but no references/, scripts/, or assets/ bundle directories exist, so the referenced one-level-deep files are broken/missing.

2 / 5

Total

14

/

20

Passed

Description

91%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 description that clearly states what the skill does and when to use it, with rich natural trigger terms. It is distinct from generic skills, though the niche is highly specialized which keeps conflict risk low.

DimensionReasoningScore

Specificity

Names the domain (compound Harness Engineering run state) and several concrete actions (analyze, validate run state, blockers, validation status, Linear context), with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('Analyze and validate compound Harness Engineering run state, blockers, validation status, and Linear context') and when ('Use when lifecycle runs drift, gates fail, blockers appear, or compound work needs refresh').

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms users actually say ('lifecycle runs drift, gates fail, blockers appear, or compound work needs refresh').

5 / 5

Distinctiveness Conflict Risk

The compound Harness Engineering niche with specific triggers (Linear, gates, blockers, lifecycle drift) is mostly distinct, with minor overlap risk with adjacent HE maintenance skills.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 2 missing, 1 suspicious

Warning

Total

14

/

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.