CtrlK
BlogDocsLog inGet started
Tessl Logo

tdd

Drive a change through a red-green-refactor loop - failing test first, minimal code to pass, then clean up. Use when implementing a feature or fixing a bug where correctness matters and a test can pin the behavior. Says "TDD", "test first", "red green refactor", "write the test first".

78

Quality

98%

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

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

An exemplary instruction-only skill body: the red-green-refactor loop is sequenced with explicit validation checkpoints and feedback at every step, the test-quality rules are concrete and skill-specific rather than generic testing tutorials, and the whole thing is tight at 44 lines with no bundle sprawl.

DimensionReasoningScore

Conciseness

Lean throughout — no padding, no explaining what testing is; every sentence adds a skill-specific judgment rule ("a test that mocks the thing under test asserts nothing"). Matches the 5 anchor: every token earns its place.

5 / 5

Actionability

Concrete, directly followable instruction at every step — "Confirm it fails for the right reason", "Write the least code that makes the test pass", "Mock at the system boundary (network, clock, filesystem)", with `expect(x).toBe(x)` as a concrete anti-pattern. Per the rubric's code_vs_instruction note, the absence of code in an instruction-only skill is not penalized.

5 / 5

Workflow Clarity

The Red → Green → Refactor → Repeat loop is clearly sequenced with explicit validation checkpoints at every step ("Run it. Confirm it fails for the right reason", "Run the test. Green.", "Re-run after every edit") plus error-recovery guidance (fix test setup first if it errors). Matches the 5 anchor.

5 / 5

Progressive Disclosure

A 44-line self-contained skill with no bundle files and clear sections (The loop / What makes a test worth writing / When to reach for it / Output contract). Per the rubric's guideline for skills under 50 lines with no need for external references, well-organized sections alone warrant a 5.

5 / 5

Total

20

/

20

Passed

Description

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

An exemplary description: concrete three-action capability statement, an explicit 'Use when' clause, and quoted trigger terms covering the acronym and its expansions. Only the slight overlap between its generic test-first triggers and a hypothetical general testing skill keeps distinctiveness from a 5.

DimensionReasoningScore

Specificity

"failing test first, minimal code to pass, then clean up" lists the three concrete actions of the loop in full — comprehensive coverage of the skill's behavior, matching the 5 anchor rather than 4 (no coverage gaps).

5 / 5

Completeness

Answers both what ("Drive a change through a red-green-refactor loop - failing test first, minimal code to pass, then clean up") and when ("Use when implementing a feature or fixing a bug where correctness matters") with concrete trigger phrases — exactly the 5 anchor.

5 / 5

Trigger Term Quality

Explicitly quotes four natural user phrases — "TDD", "test first", "red green refactor", "write the test first" — covering the acronym and its synonyms, which matches the comprehensive 5 anchor.

5 / 5

Distinctiveness Conflict Risk

"red green refactor" and "TDD" are unambiguous, but "test first" / "write the test first" could also naturally fire for a generic test-writing skill — minor overlap risk with a closely related skill, matching the 4 anchor rather than 5.

4 / 5

Total

19

/

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
rohitg00/pro-workflow
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.