CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/red-green-refactor

Use before fixing a bug or adding a feature in any language, even a one-line fix: reproduce it with a failing test first, watch it fail for the right reason, make the smallest change that passes, refactor, and show the test output before saying it is fixed or works.

Quality

89%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%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 unusually actionable, well-sequenced process skill: every step has runnable commands, validation checkpoints, and a worked example ending in an evidence block. Its weaknesses are token efficiency (an 8-framework command table Claude largely knows) and a monolithic structure that inlines reference material instead of splitting it into bundle files.

Suggestions

Move the Step 1 single-test command table to references/single-test-commands.md and keep only 2-3 common examples inline, since the body already defers framework coverage to the per-language unit-test skills.

Trim the Overview's generic TDD explanation to the Canon TDD test-list rule and the evidence principle, dropping background Claude already knows about what TDD is.

Move the full worked example to references/worked-example.md and reference it from Step 7, keeping only the evidence-block template inline in SKILL.md.

DimensionReasoningScore

Conciseness

Mostly lean, high-value content (Canon TDD rules, the red-triage table, anti-patterns with reasons), but the 8-framework single-test command table and parts of the Overview restate commands and concepts Claude already knows. Above anchor 3 because the over-explanation is confined to one table and a few sentences, fitting "minor instances that could be trimmed".

4 / 5

Actionability

Fully executable throughout: copy-paste commands like `pytest tests/test_mod.py::test_func`, a concrete test-list example, a triage table giving the next move for each failure mode, a worked example with real outputs, and a final evidence-block template. Specific examples cover the common cases.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit validation checkpoints (baseline suite run, right-reason red check, whole-suite verification in Steps 4 and 5, refactor-only-on-green) and feedback loops for error recovery ("Fix the test until it runs and fails on its assertion"), plus an anti-patterns checklist. Matches the top anchor.

5 / 5

Progressive Disclosure

Well-sectioned and easy to navigate, but monolithic at ~260 lines with no bundle files: reference-grade material is inlined, notably the 8-stack single-test command table that the body itself says the per-language unit-test skills cover. The under-50-lines exception does not apply, so this sits at "content that should be separate is inline" rather than anchor 4.

3 / 5

Total

17

/

20

Passed

Description

88%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: it names the complete TDD loop as concrete actions and gives an explicit, broad trigger clause with natural phrasing. Its only weaknesses are a few missing common synonyms (TDD, test-driven, write tests first) and a trigger scope so broad it could contend with general coding skills.

DimensionReasoningScore

Specificity

Lists five concrete actions covering the full loop — "reproduce it with a failing test first", "watch it fail for the right reason", "make the smallest change that passes", "refactor", "show the test output" — matching the comprehensive-coverage anchor; it is not 4 because there are no gaps in the action list.

5 / 5

Completeness

Explicitly answers both parts: the what is the concrete five-action loop, and the when is the explicit trigger clause "Use before fixing a bug or adding a feature in any language, even a one-line fix". Not 4 because the when-clause is explicit with concrete trigger phrases rather than merely present.

5 / 5

Trigger Term Quality

Includes natural phrases users say such as "fixing a bug", "adding a feature", "failing test", and "one-line fix", but omits common synonyms and variations like "TDD", "test-driven", "write the test first", or "unit test".

4 / 5

Distinctiveness Conflict Risk

The what occupies a clear niche (the red-green-refactor loop with evidence), distinct from framework-specific test skills. Not 5 because the trigger "before fixing a bug or adding a feature ... even a one-line fix" fires on nearly every coding task, creating overlap risk with closely related coding and unit-test skills.

4 / 5

Total

18

/

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.

Reviewed

On this page