CtrlK
BlogDocsLog inGet started
Tessl Logo

054-design-tdd

Use when Java implementation work should be guided by Test-Driven Development, including maintaining a test list, choosing the next behavior, writing a failing test first, implementing only enough production code to pass, and refactoring while keeping tests green. This should trigger for requests such as Apply TDD; Use test-driven development; Drive this Java change with tests; Write the failing test first; Red-green-refactor this feature. Part of Plinth Toolkit

72

Quality

87%

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

75%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 content is a well-structured, mostly efficient interactive process skill with a clear red-green-refactor workflow and a single well-signaled reference file. Its main weakness is triple restatement of the same TDD activities across the overview, constraints, and workflow sections, which adds tokens without adding guidance.

Suggestions

Consolidate the duplicated activity lists: keep the 6-step Workflow as the primary sequencing and trim the 'What is covered' and 'Constraints' lists to point at it rather than restating the same items.

Add one minimal concrete example (e.g., a tiny failing test and the minimal code that passes it) so the red-green-refactor cycle is shown end-to-end, not just described.

Make the validation checkpoint explicit in the workflow (e.g., 'run the test suite; only refactor when green') rather than relying on implicit 'while keeping tests green' phrasing.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude knows TDD, but the same activities are restated three times (the 'What is covered' list, the 'Constraints' MUST list, and the Workflow steps), introducing repetition that could be trimmed.

4 / 5

Actionability

Provides concrete, specific process guidance with explicit MUST constraints and a defined 6-step workflow, but as an instruction skill it lacks any concrete test/cycle example that would make the guidance fully copy-paste ready.

4 / 5

Workflow Clarity

A clearly sequenced 6-step red-green-refactor cycle with an explicit reporting checkpoint and a feedback loop back to the test list; validation is implicit rather than stated as explicit pass/fail commands.

4 / 5

Progressive Disclosure

A single one-level-deep reference file is clearly signaled both as a MUST-read constraint and in a dedicated Reference section, with a concise overview body; the mild duplication of the reference's likely content keeps it just below the top anchor.

4 / 5

Total

16

/

20

Passed

Description

100%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 exemplary: it combines a concrete capability list, an explicit 'Use when' trigger clause, and natural phrasings a user would actually say, all in third person. It clearly distinguishes itself within the Java/TDD niche with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (maintaining a test list, choosing the next behavior, writing a failing test first, implementing only enough code to pass, refactoring while green), giving comprehensive coverage of TDD capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated TDD activities) and 'when' (a clear 'Use when...' clause plus concrete trigger phrases), satisfying the top anchor.

5 / 5

Trigger Term Quality

Includes natural user phrasings and synonyms ('Apply TDD', 'Use test-driven development', 'Drive this Java change with tests', 'Write the failing test first', 'Red-green-refactor this feature'), matching how a user would actually request the skill.

5 / 5

Distinctiveness Conflict Risk

Scoped to Java + TDD with distinct triggers like 'Red-green-refactor this feature', giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/plinth
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.