CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

he-refine

Refine Harness Engineering artifacts, plans, specs, or work into clearer action plans. Use when users ask for tightening, simplification, or lifecycle repair.

Quality

75%

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/skills/team_automation/he-refine/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 compact, well-sectioned instruction document with a clear gated workflow and fail-fast validation. It is held back by missing executable detail (no commands, probe recipes, or file formats) and weak bundle navigation: the real reference files are unlinked and the only file links present are broken asset paths.

Suggestions

Add executable specifics to the Procedure: the launch-config file name to read (e.g., launch.json), a concrete localhost probe command, and the fallback project-type detection recipe, so steps can be run without invention.

Link each reference file with a one-line signal of its contents (e.g., "Triggers, risks, and rollback: [contract.yaml](references/contract.yaml)"; "Acceptance cases: [evals.yaml](references/evals.yaml)") so the archived context is discoverable.

Fix or remove the broken asset links in "Full Context" — ./assets/icon-small.png and ./assets/icon-large.png do not exist in the bundle; either ship the assets or drop the section.

DimensionReasoningScore

Conciseness

The body is built from tight one-line bullets with no explanations of concepts Claude already knows. Minor trimmable content remains: the meta "Progressive Disclosure Entry" note, the "Philosophy" section that overlaps "When to use" and "Validation", and the "Full Context" section that merely lists icon files. This fits 'Efficient; minor instances of over-explanation that could be trimmed' rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

The procedure gives sequenced direction with some specifics ("block if the current branch is a protected default branch", "Resolve dev-server startup from launch config first, then fall back to project-type and port detection", one-issue-per-loop), but no executable detail anywhere: no probe command, no startup recipe, no launch-config file name or format. This matches 'Some concrete guidance but incomplete; missing key details' — below anchor 4, which requires mostly executable guidance.

3 / 5

Workflow Clarity

The five-step procedure is clearly sequenced with explicit checkpoints: block on protected branches, "Start and probe the dev server before claiming readiness", regression-risk check before stage exit, and "Fail fast: stop at first failed gate and do not proceed". It falls short of anchor 5 because error recovery is not addressed — e.g., what to do when the server probe fails (log inspection, escalation) is never specified, leaving a minor validation gap.

4 / 5

Progressive Disclosure

The bundle contains three real one-level-deep reference files (references/contract.yaml, references/evals.yaml, references/task-profile.json), but the body never names or links any of them — it only vaguely says it "keeps full operational context in archived references". Worse, the only concrete file links in the body ([icon-small.png](./assets/icon-small.png), [icon-large.png](./assets/icon-large.png)) point to a nonexistent assets/ directory. This fits 'references present but not clearly signaled' rather than anchor 4's mostly-clear references.

3 / 5

Total

14

/

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 well-formed description that explicitly states both what the skill does and when to use it, with reasonably natural trigger phrases anchored to a distinct domain. Its main weakness is thin capability specificity — one generic action verb — and trigger terms that overlap with generic polish/refactor skills.

DimensionReasoningScore

Specificity

The description names its domain ("Harness Engineering artifacts, plans, specs, or work") and one concrete transformation ("Refine ... into clearer action plans"), but offers only a single generic action verb rather than a list of specific capabilities. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' — above anchor 2 because a concrete output is stated, below anchor 4 because no several specific actions are listed.

3 / 5

Completeness

It explicitly answers both parts: what ("Refine Harness Engineering artifacts, plans, specs, or work into clearer action plans") and when ("Use when users ask for tightening, simplification, or lifecycle repair") with concrete trigger phrases. This mirrors the anchor-5 example structure; the when-clause is already explicit and specific, so it does not fall to anchor 4.

5 / 5

Trigger Term Quality

"Use when users ask for tightening, simplification, or lifecycle repair" supplies natural phrases a user would plausibly say, covering the main trigger space. It stays at 4 rather than 5 because common variations like "polish", "clean up", or "clarify" are absent, and "lifecycle repair" is more jargon than a natural user phrase.

4 / 5

Distinctiveness Conflict Risk

The "Harness Engineering" niche makes the skill mostly distinct with clear domain triggers, but generic polish terms like "tightening" and "simplification" create minor overlap risk with general refactoring or code-polish skills. It fits 'Mostly distinct; minor overlap risk with closely related skills' rather than anchor 5's minimal conflict risk.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

jscraik/Agent-Skills

Path

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