CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

he-reframe

Create evidence-backed HE reframe migration programs. Use when structural drift, routing ambiguity, or source-prompt gaps need phased rollback-safe execution.

Quality

70%

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/skills/he-reframe/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.

The body is a well-structured, safety-conscious instruction skill with a clear sequenced procedure and explicit fail-fast validation, but it is hampered by heavy redundancy across boundary sections and heavy reliance on external contract references that are absent from the bundle, leaving much of the operative detail unresolvable.

Suggestions

Consolidate the repeated boundary rules (Constraints, Execution Boundaries, Failure Mode, Handoff Rules, Gotchas) into a single authoritative section to remove ~4 redundant restatements of the same prohibitions.

Inline the minimal operative definitions for the contracts the procedure depends on (BLUF review contract, stage-arc boundary fields, subagent call policy) or verify/ship those reference files in the bundle, since most ../../references/** paths currently do not resolve.

Replace vague name-drops ("OpenAI-style design, agent-native compression, Pragmatic Programmer, XP") with the specific rule each is meant to invoke, or move them to a reference with clear labels in the References section.

DimensionReasoningScore

Conciseness

Sentences are terse and no basic concepts are explained, but boundary rules repeat across many sections ("do not create Linear objects" appears in Constraints, Execution Boundaries, Failure Mode, and Handoff Rules; "do not implement" is restated ~4 times) and vague name-drops like "OpenAI-style design, agent-native compression, Pragmatic Programmer, XP" pad without instructing. This fits "mostly efficient but could be tightened" rather than anchor 2, since the padding is redundancy rather than concept explanation.

3 / 5

Actionability

The 12-step procedure gives specific structural requirements and two runnable validation commands, but much operative guidance defers to external contracts absent from the bundle ("build the generic Desktop capability packet", "apply the BLUF review contract", "apply the visual reference contract"). Anchor 3 (some concrete guidance, key details missing) fits; anchor 4 fails because a majority of the executable detail lives in unresolved references.

3 / 5

Workflow Clarity

A clearly sequenced 12-step procedure with an explicit, fail-fast Validation section ("stop at the first failed gate and do not proceed"), concrete commands, and defined stop/pivot and rollback conditions. Not 5 because several checkpoints are implicit or conditional ("eval/plugin-eval gates when available", "inspect required sections" without a command); not 3 because validation is explicit rather than absent.

4 / 5

Progressive Disclosure

A dedicated References section clearly signals external files and deep context is correctly moved out of the entrypoint, but scored against the actual bundle most referenced paths do not resolve: only references/contract.yaml and references/evals.yaml exist, while all ../../references/** files (routing-map.json, bluf-review-contract.md, subagent-call-contract.md, stage-arc-boundary-contract.md, etc.) are missing, and the "Shared contracts: ... under ../../references/**" bullet is a vague catch-all. Navigation cannot be completed from the bundle, which blocks anchor 4; references are clearly signaled rather than buried, which avoids anchor 2.

3 / 5

Total

13

/

20

Passed

Description

71%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.

The description is concise, explicitly answers both what and when with a proper "Use when..." trigger clause, and occupies a distinct niche. Its main weaknesses are jargon-heavy trigger terms with no natural synonyms or variations, and a single-action capability statement that could enumerate more concrete outputs.

Suggestions

Enumerate 1-2 more concrete actions or outputs (e.g., what a reframe program contains: phases, rollback gates, eval proof) to raise specificity beyond a single verb.

Add natural-language trigger variations or concrete artifact names (e.g., ".harness", "architecture migration", "refactor program") so users' phrasing matches without knowing internal jargon.

DimensionReasoningScore

Specificity

"Create evidence-backed HE reframe migration programs" names the domain plus a single concrete action, matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several distinct actions (anchor 4), and the action is concrete rather than generic (anchor 2).

3 / 5

Completeness

Both questions are explicitly answered: what ("Create evidence-backed HE reframe migration programs") and when ("Use when structural drift, routing ambiguity, or source-prompt gaps need phased rollback-safe execution") with concrete trigger phrases. The explicit "Use when" clause with specific triggers matches the anchor-5 pattern; anchor 4 would require the when-clause to be only weakly implied.

5 / 5

Trigger Term Quality

Triggers like "structural drift, routing ambiguity, or source-prompt gaps" are domain-relevant but jargon-heavy, offering no synonyms, variations, or concrete artifact/file names a user would naturally say. This fits "some relevant keywords but missing common variations or synonyms" rather than the good-coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

"HE reframe migration programs" carves a clear niche with triggers unlikely to fire for unrelated skills, but "HE" is undefined and "migration programs" risks minor overlap with generic migration/refactoring skills. This is "mostly distinct; minor overlap risk" rather than the fully self-disambiguating 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/skills/he-reframe/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.