CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

he-tdd

Build behavior-safe code changes with TDD and RED/GREEN evidence. Use when he-plan or he-work requires TDD for a concrete behavior target.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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-tdd/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 well-structured as a progressive-disclosure entry point with a clear RED/GREEN procedure, an explicit validation gate, and read-when cues on every reference. Weaknesses are moderate: redundant/meta sections, procedure steps that lack executable detail, and references that all point outside the skill bundle via non-resolvable repo: paths.

Suggestions

Merge the 'Use' and 'When to use' sections and drop the meta-commentary about archived vs. deprecated context and the 'Philosophy' section to tighten token efficiency.

Add one concrete executable example, such as a sample RED test and the repository test command pattern, to make the procedure copy-paste actionable.

Ship the referenced guides (SKILL.full.md, tests.md, mocking.md, interface-design.md, deep-modules.md, refactoring.md) inside the skill's own references/ directory with standard relative links, and remove the duplicate subagent-routing reference.

DimensionReasoningScore

Conciseness

Mostly efficient, but includes unnecessary material: meta-commentary about its own architecture ('Archived means active deferred context, not deprecated guidance'), a redundant pair of 'Use' and 'When to use' sections, and a one-line 'Philosophy' section. Not 4: the redundancy across sections is more than minor; not 2: it never explains concepts Claude already knows (no library tutorials or basic TDD primers).

3 / 5

Actionability

Some concrete guidance exists ('Produce a failing test first (RED), then apply the smallest fix (GREEN)' and the executable 'bin/ask skills audit ... --json' command), but the procedure is otherwise high-level with no example test command or concrete illustration of translating reproduction steps into a RED test. Not 4: key executable details are missing; not 2: the validation command and explicit inline-fallback routing exceed high-level hints.

3 / 5

Workflow Clarity

A clear 5-step numbered Procedure with an explicit validation checkpoint ('Fail fast: stop at the first failed gate and do not proceed') and a hard constraint ('Do not skip RED verification'). Not 5: there is no fix-and-revalidate feedback loop or checklist describing what to do after a failed gate; not 3: the validation checkpoint is explicit, not implicit.

4 / 5

Progressive Disclosure

References are one level deep and well-signaled with per-reference 'Read when:' cues, but the skill's own bundle contains no referenced files at all — every link points outside the skill directory via a non-standard 'repo:' link scheme, the subagent-routing reference is duplicated across two sections, and none of the paths resolve within the skill. Not 4: out-of-bundle, non-resolvable references and duplication are more than minor organization gaps; not 2: references are clearly signaled and organized, not buried.

3 / 5

Total

13

/

20

Passed

Description

62%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, third-person, and covers both what the skill does and when to use it, with a distinctive TDD/RED-GREEN niche. Its main weaknesses are trigger terms anchored on internal skill names (he-plan, he-work) instead of natural user phrasings, and thin coverage of concrete capabilities.

Suggestions

Replace or supplement the internal-skill triggers ('he-plan or he-work') with natural user phrasings such as 'use when the user asks for test-first development, a failing regression test first, or RED/GREEN evidence for a behavior change'.

Add 1-2 more concrete actions to the 'what' clause (e.g., 'translate bug reproduction steps into a failing regression test, then apply the smallest fix') to lift specificity.

Include common synonyms like 'test-driven', 'test-first', and 'write the failing test first' so the description triggers on varied user wording.

DimensionReasoningScore

Specificity

Names the domain ('TDD code changes') and 1-2 concrete actions ('Build behavior-safe code changes', 'RED/GREEN evidence'), but coverage of what the skill actually does is not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor. Not 4: it does not list several distinct specific actions; not 2: the actions go beyond generic domain naming.

3 / 5

Completeness

Both 'what' ('Build behavior-safe code changes with TDD and RED/GREEN evidence') and an explicit 'Use when...' clause are present, so the missing-trigger cap does not apply, but the 'when' is keyed to internal skill names rather than concrete user-facing trigger phrases, fitting the anchor where 'when' could be more explicit or specific. Not 5: the when-clause lacks concrete user-level trigger terms; not 3: the when is explicit, not merely implied.

4 / 5

Trigger Term Quality

'TDD' and 'RED/GREEN evidence' are relevant keywords, but common natural phrases like 'test-first', 'failing test', or 'regression test' are missing, and the triggers lean on internal skill names ('he-plan or he-work') that users would not naturally say, fitting the 'some relevant keywords but missing common variations' anchor. Not 4: synonym coverage is thin; not 2: some genuinely relevant, natural keywords are present.

3 / 5

Distinctiveness Conflict Risk

'TDD' and 'RED/GREEN evidence' establish a clear test-first niche with distinct triggers and minimal conflict risk, though 'Build behavior-safe code changes' is broad enough to overlap minorly with general coding-workflow skills, fitting the 'mostly distinct; minor overlap risk' anchor. Not 5: the opening clause is broader than a tightly bounded niche; not 3: the TDD/RED-GREEN vocabulary is specific, not generic.

4 / 5

Total

14

/

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: 12 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-tdd/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.