CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

77%

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

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

63%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 well structured and concise with a clear sequenced procedure and validation checkpoints, but its guidance is more procedural than executable — no concrete inspection commands are given and the HE stages it routes to are undefined. Referenced files (assets icons, session-evidence-contract.md) are missing from the bundle or point outside it.

Suggestions

Add the concrete live-state inspection commands (e.g., the actual branch/PR/CI/Linear check commands to run in step 4) or reference where the HE stage definitions live, so the procedure is executable rather than procedural.

Fix the broken references: create the assets/ directory with the referenced icon files, and correct the session-evidence-contract.md path so it resolves inside the skill bundle instead of escaping via ../../../.

Trim the Philosophy and "Progressive Disclosure Entry" meta sections, which duplicate Failure Modes/Constraints, and fold their unique content into the sections that already carry it.

DimensionReasoningScore

Conciseness

The body is lean, uses terse bullet fragments, and never explains concepts Claude already knows (no definition of Linear, CI, or PR). Minor trimmable material exists: the Philosophy section overlaps Constraints/Failure Modes, and the "Progressive Disclosure Entry" line is meta filler, keeping it below the every-token-earns-its-place anchor.

4 / 5

Actionability

Some concrete guidance exists (the 13-outcome taxonomy, "~/.agents/session-collector", "mode:autofix" normalization, "schema_version: 1"), but key details are missing: "re-run or inspect the smallest safe live-state checks" names no actual commands, and the HE stages to route to are never defined in the bundle. Not score 4 because the core inspection loop lacks any executable command or example.

3 / 5

Workflow Clarity

A clear numbered 8-step procedure is backed by an explicit Validation section, a "Fail fast: stop at first failed gate" checkpoint, and Failure Modes covering error paths. Not score 5 because there is no fix-and-revalidate feedback loop after refresh actions are applied.

4 / 5

Progressive Disclosure

Sections are well organized and references are clearly signaled, but scored against the actual bundle the referenced files do not exist: there is no assets/ directory (icon-small.png and icon-large.png links dangle), and the session-evidence-contract.md link escapes the skill bundle via ../../../. Not score 4 because the bundle structure fails the referenced paths; not score 2 because references are clearly signaled, not buried.

3 / 5

Total

14

/

20

Passed

Description

82%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 explicitly covers what the skill does and when to use it, with a distinct niche and concrete trigger phrases. Its only weakness is that the action verbs (analyze, validate) are few and somewhat abstract relative to the enumerated surfaces.

DimensionReasoningScore

Specificity

The description names the domain and 1-2 concrete actions ("Analyze and validate" applied to run state, blockers, validation status, and Linear context), but coverage is not comprehensive and the verbs are fewer and more abstract than the 'several specific actions' anchor. The enumerated surfaces are specific, which keeps it above the generic-actions anchor.

3 / 5

Completeness

It clearly 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") with concrete trigger phrases, matching the top anchor's pattern.

5 / 5

Trigger Term Quality

"Use when lifecycle runs drift, gates fail, blockers appear, or compound work needs refresh" provides four natural trigger phrases with good domain coverage, but misses common variations the body itself identifies (continue, resume, re-check), so it falls short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Compound Harness Engineering run state" and "Linear context" carve a clear niche with distinct triggers; minimal conflict risk with other skills since no generic capability terms are used.

5 / 5

Total

17

/

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.

Validation — 14 / 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

Path

Plugins/harness-engineering/fixtures/budget-archive/2026-04-21/deferred-store/skills/team_automation/he-compound-refresh/SKILL.md

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.