CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

he-work

Implement approved Harness Engineering work. Use when a plan, todo list, or tiny spec needs traceable delivery and validation.

Quality

69%

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 ./Plugins/harness-engineering/fixtures/budget-archive/2026-04-21/deferred-store/skills/team_automation/he-work/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 lean, well-sectioned process skill with a genuine validation-and-stop discipline and one concrete lint command, but its guidance relies heavily on reference material that is absent from the bundle, and it duplicates rules across Constraints, Anti-patterns, and Gotchas. Fixing the reference wiring and consolidating the redundant guardrail sections would lift it substantially.

Suggestions

Make every reference resolvable: link the actual bundle file (e.g. `references/context-preservation.md` for the context-disposition policy) from the body, and either include the referenced files (execution-modes, handoff-and-shipping) or drop/repair their paths, replacing the `repo:` prefix with a consistent relative path.

Add concrete mechanics for the abstract steps: what the three execution lanes are (or a one-line pointer to a resolvable file), and the exact commands/sequence used to resolve and update the Linear work item, mirroring the specificity of the traceability lint command.

Merge Constraints, Anti-patterns, and Gotchas into a single non-duplicating section (each rule currently appears 2-3 times) and drop the "When to use" section that restates the frontmatter description.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but carries noticeable duplication: "Do not claim completion without validation evidence" and "Do not expand scope beyond approved artifacts/IDs" each appear in both Constraints and Gotchas, the "When to use" section restates the frontmatter description, and the Failure mode section repeats the Validation stop rules. Mostly efficient, but it could be tightened by merging Constraints/Anti-patterns/Gotchas.

3 / 5

Actionability

There is one concrete executable command ("run `python3 Infrastructure/scripts/validation-and-linting/he_linear_traceability_lint.py <artifact-path>`") and specific stop conditions, but most guidance is policy-level ("Choose the execution lane", "Resolve the active Linear work item", "Implement one verified slice at a time") without the concrete steps to execute them. The mechanics are deferred to reference files that do not exist in this bundle, so the guidance is incomplete rather than executable.

3 / 5

Workflow Clarity

The Procedure gives a clear 4-step sequence (choose lane, resolve Linear/IDs/gates, implement verified slices, update handoff), and the Validation section supplies explicit checkpoints including "Stop at the first failed gate" and a drift feedback loop ("Reflect contract drift in the governing artifact before off-plan implementation continues"). Minor gaps remain: steps 1-3 have no concrete commands, and slice-level verification mechanics are unstated.

4 / 5

Progressive Disclosure

The body is well-sectioned and keeps itself to overview length with a clearly labeled References section, which is the right instinct. However, judged against the actual bundle structure: none of the 7 referenced paths (e.g. `Plugins/harness-engineering/fixtures/preserved-context/skills/he-work/SKILL.full.md`) exist in the bundle, one reference uses a non-standard `repo:` prefix, and the one real bundle file (`references/context-preservation.md`) is never referenced from the body, leaving it undiscoverable. Structure is present but navigation is broken.

3 / 5

Total

13

/

20

Passed

Description

70%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 solid description with an explicit "Use when..." trigger clause naming natural trigger artifacts (plan, todo list, spec) and a distinct internal-domain niche. Its main weakness is the vague, near-circular "what" — capabilities are described by qualities ("traceable delivery and validation") rather than concrete actions.

Suggestions

Replace the circular "Implement approved Harness Engineering work" with 2-3 concrete capabilities, e.g. "Implement approved plans and todo lists in verified slices, keeping task state, Linear status, and PR evidence synchronized."

Add a couple of natural user phrasings to the trigger clause (e.g. "or when the user asks to implement/work through an approved plan or todo") to broaden trigger coverage beyond internal jargon like "traceable delivery".

DimensionReasoningScore

Specificity

It names the domain ("approved Harness Engineering work") and gestures at two actions ("Implement", "validation"), but the verbs are generic and "traceable delivery and validation" describes qualities rather than concrete actions like "update task state" or "run the traceability lint". This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) better than anchor 2, since it does state what gets produced, and it falls well short of anchor 4's list of several specific actions.

3 / 5

Completeness

Both parts are explicit: the what is "Implement approved Harness Engineering work" and the when is "Use when a plan, todo list, or tiny spec needs traceable delivery and validation" with concrete trigger nouns. It stops short of anchor 5 because the what is circular ("work" ... "work") and does not crisply enumerate capabilities, fitting anchor 4 (both present, the what could be sharper).

4 / 5

Trigger Term Quality

"Implement", "plan", "todo list", and "spec" are natural terms a user would say when they need this skill, giving good keyword coverage. A few natural variants are missing ("work through this todo", "execute this plan") and "Harness Engineering" plus "traceable delivery" are internal jargon, so it does not reach anchor 5's comprehensive synonym coverage, but it sits above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The "Harness Engineering" qualifier and the approved-artifact trigger set (plan/todo list/tiny spec with traceable delivery) carve a clear niche with minimal conflict risk against generic skills. There is minor overlap risk with any general "implement this plan" request, matching anchor 4 rather than anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/harness-engineering/fixtures/budget-archive/2026-04-21/deferred-store/skills/team_automation/he-work/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.