CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tdd-implement

Test-Driven Development (TDD) and Incremental Implementation discipline. Use when implementing any feature or fixing bugs to enforce Red-Green-Refactor, vertical slicing, and atomic commits.

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a high-quality, actionable instruction skill: a clearly sequenced Red-Green-Verify-Commit loop backed by concrete commands, named patterns, and specific anti-pattern examples, with no filler. The main improvements are removing the redundant ASCII diagram, adding an explicit fix-and-retry feedback loop, and considering a reference file for the red-flags/anti-patterns material.

Suggestions

Add an explicit error-recovery step to the loop (e.g., "If VERIFY fails: fix, re-run the focused test, then re-run the full verification") to complete the feedback loop.

Delete or shrink the ASCII diagram — it duplicates the numbered loop immediately above it and costs ~15 lines of context.

If the skill grows, move the Agent Red Flags and Test Anti-Patterns sections into a references/ file linked from the body to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is dense and free of basic-concept padding (no explainer on what TDD is), but the 15-line ASCII diagram restates the numbered loop it follows, and a few inline *Tips* could be trimmed — minor over-explanation that keeps it below the lean 5 anchor.

4 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: specific commands ("npx tsc --noEmit", "git revert", "./gradlew"), a verbatim tautological-test example ("expect(add(a,b)).toBe(a+b)"), a ready-to-use user-reporting phrase, and named patterns (Prove-It, AAA) covering the common cases.

5 / 5

Workflow Clarity

The 7-step loop is clearly sequenced with an explicit VERIFY checkpoint (focused test, full suite, build, type checker, linter), but unlike the 5 anchor there is no explicit error-recovery feedback loop (e.g., "if verification fails, fix and re-run") — the red-flags section only partially covers self-correction.

4 / 5

Progressive Disclosure

A single well-organized file with clear section headers and no buried or nested references; however, at ~80 lines it exceeds the under-50-line simple-skill exception, and sections like the red-flags and anti-patterns lists are candidates for a separate reference if the skill grows, leaving minor organization gaps versus the 5 anchor.

4 / 5

Total

17

/

20

Passed

Description

80%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 that clearly states what the skill does and when to use it, with concrete named practices and natural trigger phrases. Its main weakness is breadth: the 'when' clause covers virtually all implementation work, which raises conflict risk with other coding skills.

Suggestions

Narrow the trigger clause (e.g., "Use when implementing features or bug fixes where tests or disciplined increments matter") or add distinguishing qualifiers so it does not compete with every general coding skill.

Add one or two common user phrasings as triggers (e.g., "write the test first", "add a feature", "build X incrementally") to improve natural-term coverage without adding bulk.

DimensionReasoningScore

Specificity

Lists several concrete practices — "enforce Red-Green-Refactor, vertical slicing, and atomic commits" — which is more than the 1-2 actions of a score-3 anchor, but coverage has gaps (no mention of test-first verification or refactoring discipline), so it falls short of the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both questions: what ("TDD and Incremental Implementation discipline... enforce Red-Green-Refactor, vertical slicing, and atomic commits") and when ("Use when implementing any feature or fixing bugs") with concrete trigger phrases, matching the 5 anchor rather than the 4 anchor where 'when' is only weakly specified.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — "implementing any feature", "fixing bugs", "TDD" — giving good keyword coverage, but misses common variations such as "adding a feature", "writing tests first", or "building X", so it does not reach the synonym-level coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The 'what' carves out a distinct niche (TDD/incremental implementation discipline), but the trigger "any feature or fixing bugs" would fire on nearly every coding task, creating real overlap risk with general coding and code-review skills — more than the 'minor overlap' of a 4, yet the specific 'what' keeps it above the generic 2 anchor.

3 / 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

glenrioariesto/social-content-studio

Path

.agents/skills/tdd-implement/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.