CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

he-fix-bugs

Restore broken behavior by reproducing failures, identifying root cause, and delivering verified fixes. Use when the user needs regression debugging, incident triage, or bug repair from tracker or direct reports.

Quality

78%

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/deferred-store/skills/team_automation/he-fix-bugs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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 strong sequenced workflow with explicit validation gates and largely concrete guidance for a policy-style skill, but progressive disclosure is badly broken: dangling reference paths, a missing assets directory, and orphaned 'Read when' lines make the navigation layer unreliable, and the Philosophy section duplicates the Procedure verbatim.

Suggestions

Repair the 'Full Context' section: restore the missing file headings for the three orphaned 'Read when:' lines and verify every referenced path resolves inside the bundle (e.g., ./assets is referenced but the directory does not exist; only ./references/context-preservation.md is present and it is never named).

Remove or compress the Philosophy section, whose bullets restate Procedure steps 5-8 nearly verbatim, and fold the thin 'Use' section into the intro line to cut redundancy.

Consolidate the duplicated subagent-routing reference (../../../references/subagent-routing.md appears in both 'Full Context' and 'Subagent Routing') into one clearly labeled section.

DimensionReasoningScore

Conciseness

Mostly efficient — terse bullets, no padding explaining concepts Claude already knows — but the Philosophy section duplicates Procedure steps nearly verbatim ('Test one hypothesis at a time, and for uncertain links require a prediction...'; 'Reproduce first, then diagnose, then fix' vs. Procedure steps 5-6), and the 'Use' section is a thin near-empty header. Fits the score-3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened'); not 4 because the duplication is more than a minor trim, not 2 because there is no concept over-explanation or heavy padding.

3 / 5

Actionability

For an instruction-only skill, guidance is mostly concrete: 'ask at most 2-3 focused questions', 'read only tails or targeted matches, capture [ERROR]/[WARN] markers', 'Resolve available roles from ~/.codex/agents/manifest.json', 'Include schema_version: 1'. Minor gaps keep it from 5: 'check workspace safety' and 'bounded runtime evidence' are undefined, and the key operational details (Linear payload format, contract specifics) delegate to reference files whose content is not in the bundle — not 3, since what is written is specific and executable rather than pseudocode-level.

4 / 5

Workflow Clarity

The Procedure is a clearly sequenced 9-step workflow with a dedicated Validation section acting as an explicit checkpoint list, and feedback loops are present ('prefer failing-test-first validation... verify no regressions', 'Fail fast: stop at first failed gate and do not proceed'). This matches the score-5 anchor (clear sequence, explicit validation steps, error-recovery checkpoints); score 4 would leave a checkpoint implicit, which is not the case here.

5 / 5

Progressive Disclosure

The 'Full Context' section is broken navigation: three orphaned 'Read when:' lines with no parent file heading, a path ('./assets') whose directory does not exist in the bundle, and most referenced paths (./Infrastructure/references/contract.yaml, evals.yaml, task-profile.json, ../../../references/*.md) resolve to nothing inside the bundle — only ./references exists and its single file (context-preservation.md) is never named. References are effectively buried and unverifiable, fitting the score-2 anchor ('references are buried' / navigation broken) rather than 3, which presumes present, mostly working references that are merely unclearly signaled.

2 / 5

Total

14

/

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: concrete action verbs, explicit 'Use when' triggers with natural terms, and both what and when clearly answered in third person. Minor improvements possible by broadening trigger synonyms and naming the QA-intake/Linear capability.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'reproducing failures, identifying root cause, and delivering verified fixes' — which are specific behaviors, but coverage has minor gaps (e.g., QA intake and Linear issue filing, which the body treats as core capabilities, are absent). This fits the score-4 anchor ('lists several specific actions; minor gaps in coverage') rather than 5, whose comprehensive multi-action example covers a broader capability sweep, and rather than 3, since more than 1-2 concrete actions are named.

4 / 5

Completeness

It explicitly answers both questions with concrete trigger phrases: what — 'Restore broken behavior by reproducing failures, identifying root cause, and delivering verified fixes'; when — 'Use when the user needs regression debugging, incident triage, or bug repair from tracker or direct reports.' This matches the score-5 anchor exactly (clear what AND when with concrete triggers); score 4 would require the 'when' clause to be weaker or less explicit than it is.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: 'regression debugging', 'incident triage', 'bug repair', 'tracker or direct reports'. A few common natural terms are missing (e.g., 'fix a bug', 'crash', 'reproduce', file/issue-type synonyms), matching the score-4 anchor ('good keyword coverage; a few natural terms missing') rather than 5's synonym-and-extension completeness.

4 / 5

Distinctiveness Conflict Risk

The debugging/fix-verification niche ('reproducing failures', 'verified fixes', 'regression debugging') is mostly distinct with clear triggers, but overlaps somewhat with generic coding-assistant and debugging skills. Fits the score-4 anchor ('mostly distinct; minor overlap risk with closely related skills') rather than 5, since 'bug repair' is a fairly common trigger space.

4 / 5

Total

17

/

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: 5 missing, 4 deeper-than-1-level, 6 suspicious

Warning

Total

14

/

16

Passed

Repository

jscraik/Agent-Skills

Path

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