CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

he-router

Route ambiguous Harness Engineering requests to one lifecycle stage when users ask where to start, resume, plan, implement, review, debug, schedule a heartbeat, or resolve domain terminology.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./Infrastructure/references/deferred-skill-context/harness-engineering-he-router/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 SKILL.md body is lean and clearly organized with a deterministic, well-sequenced routing procedure. Its critical weakness is the reference layer: the routing map and deterministic decision order it depends on are missing from the bundle, several listed references do not exist, and three actual bundle files are orphaned with no inbound links.

Suggestions

Ship the routing map and deterministic decision order inside the skill bundle (e.g., references/routing-map.json and references/deterministic-stage-routing.md) or inline the stage set and precedence table in SKILL.md, since the Procedure and Validation steps cannot execute without them.

Fix the References section: remove or restore the missing references/evals.yaml and references/task-profile.json, and correct the ../../references/* paths that resolve outside the bundle.

Link the orphaned bundle files (context-preservation.md, heartbeat-routing-preservation.md, role-resolution-fallback.md) from the body or References section so their content is discoverable, and drop the duplicated text of Procedure steps 8-9 in favor of those references.

DimensionReasoningScore

Conciseness

The body is terse and well-sectioned with no explanations of concepts Claude already knows. Not a 5 because the Philosophy section adds little operational value and Procedure steps 8-9 ('Resolve mapped roles...', 'Return outputs with...') duplicate text preserved verbatim in references/context-preservation.md and references/role-resolution-fallback.md.

4 / 5

Actionability

Procedure steps 4-7 give concrete, stage-named routing rules, which is real executable guidance. However the core lookup inputs — the stage set in '../../references/routing-map.json' and the deterministic decision order in '../../references/deterministic-stage-routing.md' — resolve to files that do not exist in the bundle, so the skill's central decision procedure cannot actually be executed. That missing key detail places it at the 'incomplete' anchor rather than 4.

3 / 5

Workflow Clarity

A clear 10-step sequence exists with an explicit terminal fallback ('return blocked with exactly one missing input') and a Validation section with fail-fast gating. But the validation checkpoints ('Ensure selected stage is in the HE stage set from routing-map.json') depend on a nonexistent artifact, leaving the gates unexecutable — sequence present but checkpoints broken, matching the anchor 3 description rather than 4's 'most checkpoints present'.

3 / 5

Progressive Disclosure

Scored against the actual bundle: of the files cited in the body and References section, only references/contract.yaml exists; references/evals.yaml and references/task-profile.json are missing, and all seven '../../references/*' links point outside the bundle to a nonexistent directory. Meanwhile three of the four real bundle files (context-preservation.md, heartbeat-routing-preservation.md, role-resolution-fallback.md) are never linked from SKILL.md, making them undiscoverable. The navigation layer is broken despite well-organized in-file sections, fitting the anchor 2 'references are buried/minimal structure' case better than 3.

2 / 5

Total

12

/

20

Passed

Description

78%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 with a clear what/when structure and good natural trigger phrases. Its main gap is that it describes only one action (routing to a stage) without naming what the router produces, e.g., the next skill invocation, confidence, or subagent plan.

Suggestions

Add 1-2 more concrete actions to lift specificity, e.g., 'return one exact next skill invocation with confidence and a blocked/missing-input result'.

Include a couple of natural trigger synonyms such as 'which stage', 'route me', or 'next step' to sharpen trigger matching.

Qualify the generic verbs (plan, review, debug) with the Harness Engineering context inline (e.g., 'review an implemented HE branch') to reduce overlap with general development skills.

DimensionReasoningScore

Specificity

Names the domain ('Harness Engineering requests') and one concrete action ('Route... to one lifecycle stage'), but stops at a single action rather than listing several specific capabilities. It is not a 4 because the description never enumerates multiple concrete actions (e.g., what the router returns or how it resolves conflicts).

3 / 5

Completeness

Explicitly answers both what ('Route ambiguous Harness Engineering requests to one lifecycle stage') and when ('when users ask where to start, resume, plan, implement, review, debug, schedule a heartbeat, or resolve domain terminology') with concrete trigger phrases. The when-clause is present and specific, so neither the 4 anchor (weakly implied when) nor the 3 cap applies.

5 / 5

Trigger Term Quality

Good natural trigger coverage: 'where to start, resume, plan, implement, review, debug, schedule a heartbeat, or resolve domain terminology' are phrases users would plausibly say. Not a 5 because common synonyms and phrasings ('which stage', 'route me', 'next step', 'heartbeat') are only partially covered.

4 / 5

Distinctiveness Conflict Risk

'Harness Engineering' and 'schedule a heartbeat' establish a clear niche with distinct triggers. Not a 5 because generic lifecycle verbs ('plan', 'implement', 'review', 'debug') create minor overlap risk with general planning/review/debugging skills.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 2 missing, 9 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Infrastructure/references/deferred-skill-context/harness-engineering-he-router/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.