CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

he-spec

Write Harness Engineering specs before planning. Use when a feature, QA report, Linear issue, or UI source needs a clear WHAT contract.

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-spec/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 a disciplined, low-token overview with explicit validation gates and routing rules, appropriate for a spec-writing entry point. Its weaknesses are that the spec artifact itself is never shown concretely (no ID or frontmatter examples) and the References section does not match the actual bundle.

Suggestions

Add a minimal example of the deliverable: a short spec frontmatter block and one SA or VAC acceptance ID, so 'Define expected behavior, non-goals, interface shape, and acceptance IDs' becomes executable rather than aspirational.

Reconcile the References section with the actual bundle: the listed Plugins/harness-engineering/... paths are not present in this skill's directory, while the bundled references/context-preservation.md is never linked from the body despite the context-disposition policy being invoked.

Deduplicate the guidance repeated across sections: 'do not plan sequencing or implement code' appears in Core Contract, Constraints, and Gotchas, and he-deepen-spec routing appears in both Core Contract and Gotchas.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no explanations of concepts Claude already knows, but "do not plan sequencing or implement code" and the he-deepen-spec routing rule are each repeated across Core Contract, Constraints, and Gotchas. Efficient overall with minor duplication that could be trimmed.

4 / 5

Actionability

Some concrete guidance exists (the exact lint command with path, explicit routing targets, stop conditions), but the core deliverable is left undefined: no example spec artifact, no SA/VAC ID format, no frontmatter shape. This is an instruction-only skill whose guidance is only partially actionable.

3 / 5

Workflow Clarity

A three-step procedure is backed by an explicit Validation section with a runnable gate command and "Stop at the first failed gate", plus a Failure-mode stop-and-ask path. Not 5 because there is no fix-and-revalidate feedback loop and the procedure steps themselves remain high-level.

4 / 5

Progressive Disclosure

The body is a well-sectioned overview with clearly labeled references, but the six listed Plugins/harness-engineering/... paths do not exist in this skill's bundle, and the one bundled file (references/context-preservation.md) is never linked from the body even though the "context-disposition policy" it implements is invoked. Navigation dead-ends, so structure is only partially effective.

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: third-person, concise, and complete with an explicit 'Use when' clause and concrete natural trigger terms. The only weakness is that it states a single action, so the scope of what writing a spec involves is not conveyed.

DimensionReasoningScore

Specificity

"Write Harness Engineering specs before planning" names the domain plus one concrete action, but does not enumerate what the spec comprises (acceptance criteria, traceability, non-goals). It is above a generic 'works with specs' (2) but below several specific actions (4).

3 / 5

Completeness

Explicitly answers what ("Write Harness Engineering specs before planning") and when ("Use when a feature, QA report, Linear issue, or UI source needs a clear WHAT contract") with concrete enumerated trigger phrases. Score 4 would apply only if the 'when' were less explicit, which it is not.

5 / 5

Trigger Term Quality

"feature, QA report, Linear issue, or UI source" plus "specs" are natural phrases a user would say, giving good coverage. Not 5 because common synonyms like "specification", "acceptance criteria", or "before implementation" are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (WHAT-before-HOW contract prior to planning, Linear/QA/UI-source triggers) that distinguishes it from sibling skills like he-plan and he-deepen-spec. Conflict risk is minimal.

5 / 5

Total

17

/

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-spec/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.