CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

he-reinforce

Create or refresh evidence-bound Harness Engineering learning artifacts from verified solved problems. Use when a fix worked, a repeated failure should become durable knowledge, or .harness/solutions and Project Brain need maintenance.

Quality

73%

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-reinforce/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 has a genuine skeleton of a good skill — sequenced procedure, explicit validation gates, fail-fast failure handling, and one concrete executable command — but execution guidance stays abstract, navigation is cluttered by an eight-times-repeated pointer line and a prose-heavy References section, and six ../../ references dangle unresolved. It reads as a compressed internal contract spec rather than an operational guide.

Suggestions

Replace the eight repeated 'See references/hot-path-folded-context.md for folded X detail' lines with a single pointer at the top or bottom of the skill, and consolidate the duplicated 'memory, artifact, goal, Chronicle, Local Memory, vault, or native citation surfaces' enumerations into one defined list.

Add one worked example of a captured learning artifact (frontmatter, solved evidence, validation output, prevention note) — or point to assets/resolution-template.md from the body — so the capture/refresh procedure is executable rather than a list of eligibility rules.

Fix the six dangling '../../references/*' paths by copying those files into this skill's references/ or correcting the relative paths, and restructure the References section as a bulleted list of 'read when -> file' pairs.

DimensionReasoningScore

Conciseness

The body is compressed rather than padded — it never explains concepts Claude already knows — but it carries real waste: the boilerplate line "See references/hot-path-folded-context.md for folded X detail" is repeated in eight sections, and the enumeration "memory, artifact, goal, Chronicle, Local Memory, vault, or native citation surfaces" is repeated almost verbatim in two places. This is 'mostly efficient but could be tightened' rather than anchor 2, since the padding is duplicated pointers, not unnecessary explanation.

3 / 5

Actionability

Concrete elements exist — the exact command "python3 Plugins/harness-engineering/scripts/check_bluf_structure.py <learning-artifact-path> --json" and a fully enumerated structured-output field list — but the core procedure steps are abstract directives ("Prove eligibility", "Keep scope tight", "Avoid duplicate memory") with no worked example, template, or artifact sample. This matches anchor 3 (some concrete guidance but incomplete) better than 4, whose 'concrete code or commands with minor gaps' would require the primary workflow itself to be executable, not just its validation script.

3 / 5

Workflow Clarity

The Procedure is a numbered five-step sequence, and the Validation section adds explicit fail-fast gates with per-gate pass/fail/blocked reporting plus a blocked_reason/next_evidence_needed recovery path in Failure Handling — checkpoints are present, not implicit. It falls short of anchor 5 because most gates name what to check (solved evidence, redaction, discoverability) without any method or re-validate loop beyond the single structure script; it is above anchor 3 because validation and error handling are explicit sections.

4 / 5

Progressive Disclosure

Local references are real and well-signaled with read-when conditions (contract.yaml, evals.yaml, source-prompt-preservation.md, compound-learning-migration.md all exist), but the References section is a tangle of prose-like bullets, and six cited paths point outside the bundle to "../../references/*" (codex-native-memory-baseline.md, stage-arc-boundary-contract.md, bluf-review-contract.md, subagent-call-contract.md, visual-reference-contract.md, deferred-context-index.md) that do not resolve from the skill directory. That mix of working but disorganized navigation and dangling paths fits anchor 3 (some structure, could be better organized) rather than 2, since references are explicitly signaled rather than buried.

3 / 5

Total

13

/

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 strong description with an explicit, multi-trigger 'Use when' clause and a concrete statement of what it does, written in third person without fluff. Its weaknesses are moderate: only two of the skill's several modes are named in the what-clause, and a few natural trigger synonyms (solved, worth remembering) appear in the body but not the description.

DimensionReasoningScore

Specificity

"Create or refresh evidence-bound Harness Engineering learning artifacts from verified solved problems" names the domain and two concrete actions (create, refresh) with a specific source, but omits other capabilities the skill performs (consolidate overlap, Project Brain sync, continuity snapshot), so coverage is not comprehensive. It fits the 'names domain and 1-2 concrete actions, but not comprehensive' anchor rather than 4, whose 'several specific actions with minor gaps' would require more of the mode set to be listed.

3 / 5

Completeness

It clearly answers what ("Create or refresh evidence-bound ... learning artifacts from verified solved problems") and when, with an explicit "Use when" clause listing three concrete triggers (fix worked, repeated failure worth durable knowledge, .harness/solutions and Project Brain need maintenance). This matches the anchor-5 example structure of concrete what plus explicit trigger phrases; it is not 4 because the when clause is already specific and multi-trigger, not merely 'could be more explicit'.

5 / 5

Trigger Term Quality

Natural phrases users would say are present — "a fix worked", "a repeated failure", "durable knowledge" — plus concrete paths like ".harness/solutions" and "Project Brain". Common variations the body itself uses ("solved", "worth remembering", ".harness/knowledge") are missing from the description, so it is good-but-not-comprehensive coverage rather than the anchor-5 synonym-and-extension level.

4 / 5

Distinctiveness Conflict Risk

"Learning artifacts from verified solved problems", ".harness/solutions", and "Project Brain" form a clear niche distinct from sibling HE stages (reconcile, fix-bugs, eval-report). Minor overlap risk remains: "need maintenance" could pull requests belonging to `he-reconcile` (lifecycle/freshness reconciliation), and the description does not name the siblings to disambiguate, so it is mostly-distinct rather than the minimal-conflict anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

jscraik/Agent-Skills

Path

Plugins/harness-engineering/skills/he-reinforce/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.