CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

he-spec

Create bounded, evidence-backed Harness Engineering specs from approved intent. Use when a selected issue, milestone, reframe phase, or execution slice needs acceptance criteria, traceability, risk gates, and validation boundaries before planning or implementation.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 dense, boundary-heavy instruction skill with an unusually disciplined workflow: explicit sequence, runnable validation gates with block conditions, recovery steps, and handoff rules. Its main weakness is bundle alignment — nearly every named reference and script resolves outside the shipped bundle while the local references/ files are orphaned — plus notable rule repetition across sections.

Suggestions

Align the reference graph with the actual bundle: either ship the referenced files (../../references/skills/he-spec/spec-mode-rules.md, spec-artifact-contract.md, the boundary contracts, and the two Plugins/.../scripts/*.py validators) at paths the bundle resolves, or rewrite the body's paths to the existing references/ contents (contract.yaml, evals.yaml, task-profile.json), which are currently never cited.

Consolidate the repeated boundary rules: coding_lens/testing_lens, the runtime persistence boundary, and the strict scope contract are each restated in Procedure, Validation, Stage Arc Boundary, and References — state each once and reference it elsewhere.

Inline one-line trigger conditions for each gate family in step 5 (or point to one reachable reference), since the current "only when triggered" defers to files that are missing from the bundle, leaving the reader unable to act.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no concept tutorials, no padding, telegraphic contract-style prose — but rules repeat across sections: coding_lens/testing_lens and the runtime boundary contract each appear in Procedure, Validation, Stage Arc Boundary, and References, and Outputs describes fields in two overlapping paragraphs, so not every token earns its place.

4 / 5

Actionability

It includes concrete validation commands ("python3 Plugins/harness-engineering/scripts/check_bluf_structure.py <spec-path> --json"), enumerated output fields with a list of valid linear_mutation_status values, and two worked input/expected-output examples. Minor gaps remain: gate triggering conditions (step 5's "gate-selection, first-principles, hook, domain, security... gates only when triggered") are never defined inline and the defining references are outside the bundle.

4 / 5

Workflow Clarity

The 9-step procedure is clearly sequenced with explicit validation checkpoints — two runnable lint commands with block conditions, "record each gate as pass, fail, or blocked; never claim readiness from unrun checks", a Failure Mode section with blocked_reason plus one recovery step, and handoff gates before he-plan. This matches the top anchor including feedback loops and error recovery.

5 / 5

Progressive Disclosure

Referenced paths are well signaled (conditional "Read when" clauses, conceptually one level deep), but scored against the actual bundle the structure is misaligned: the named reference files (../../references/skills/he-spec/spec-mode-rules.md, spec-artifact-contract.md, ../../references/*.md, Plugins/.../scripts/*.py) do not exist in the bundle, while the shipped references/ files (contract.yaml, evals.yaml, task-profile.json) are never referenced by name from the body, leaving an unnavitable link graph. It sits above anchor 2 (references are clearly signaled, not buried) but below anchor 4 because most referenced content is not actually reachable.

3 / 5

Total

16

/

20

Passed

Description

83%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 voice, explicit what-and-when structure, and a clearly carved niche. Its only weaknesses are heavy ecosystem jargon in the trigger list and the absence of everyday synonyms like "specification" or "requirements" that a user might naturally say.

DimensionReasoningScore

Specificity

The description names the domain and several concrete deliverable actions — "Create bounded, evidence-backed Harness Engineering specs" with "acceptance criteria, traceability, risk gates, and validation boundaries" — but phrases like "bounded, evidence-backed" are abstract properties rather than actions, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

It explicitly answers both what ("Create bounded, evidence-backed Harness Engineering specs from approved intent") and when ("Use when a selected issue, milestone, reframe phase, or execution slice needs acceptance criteria... before planning or implementation") with concrete trigger objects and a clear precondition, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger nouns are present ("selected issue", "milestone", "spec", "acceptance criteria", "planning or implementation") alongside ecosystem jargon ("reframe phase", "execution slice") that HE-workflow users would say, but common synonyms like "specification", "write/draft a spec", or "requirements" are missing.

4 / 5

Distinctiveness Conflict Risk

The HE-spec niche (specs from approved intent, before planning) is distinct with domain-specific triggers, but it sits in a family of closely related skills (he-plan, he-linear-plan) that are not distinguished in the description itself, leaving minor overlap risk with generic spec-writing or planning requests.

4 / 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/skills/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.