CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/red-green-refactor

Use before changing code to fix a bug or add behavior, in any language, even when the user just says "fix it" or pastes a one-line function: reproduce the problem 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

90%

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

88%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 process skill: concrete commands for eight stacks, explicit validation checkpoints at every step of the loop, error-recovery decision tables, and a worked example with real output. The only weaknesses are mild redundancy (Overview quotes, anti-patterns restating step rules, a duplicate References section) and a monolithic single-file structure that is at the upper bound of what should stay inline.

Suggestions

Trim the Overview's verbatim Fowler/Beck quotes to one-line citations and cut the Anti-patterns rows that restate rules already stated in Steps 3-5, or drop the redundant References section that repeats the inline link definitions.

Consider moving the per-stack single-test command table (Step 1) or the worked example into a reference file to shorten the always-loaded body while keeping them one level deep.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with almost no concept-explanation padding, but a few sections could be trimmed: the Overview's verbatim Fowler/Beck quotes, the Anti-patterns table restating rules already given in Steps 3-5, and a References section duplicating the inline link definitions. This places it just below the lean "every token earns its place" anchor.

4 / 5

Actionability

Fully executable throughout: copy-paste single-test commands for eight stacks (e.g. `pytest tests/test_mod.py::test_func`, `go test ./pkg/... -run 'TestParse$' -count=1`), a concrete test-list example, real failure output (`AssertionError: assert 90 == 5400`), an evidence-block template, and a complete worked example covering the common path.

5 / 5

Workflow Clarity

Seven clearly sequenced steps each with explicit validation: baseline suite run and recorded result (Step 1), a decision table requiring the test to "fail, and fail for the right reason" with recovery moves (Step 3), whole-suite runs after green and after refactor (Steps 4-5), and a final evidence block (Step 7). Feedback loops (fix-the-test, add-stub-and-re-run) are explicit, matching the top anchor.

5 / 5

Progressive Disclosure

A single well-organized file with clear section headers and no nested or buried references (all links are external URLs; no bundle files exist). At roughly 260 lines it stays appropriately inline, though the per-stack command table and the worked example are borderline candidates for separate reference files, keeping it below the ideal split of the score-5 anchor.

4 / 5

Total

18

/

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 that explicitly states both when to use the skill and what the skill does through five concrete, ordered actions. Trigger phrasing is natural (including the user-voice "fix it" case); the only weaknesses are missing common synonyms like "TDD"/"write tests" and some breadth-driven overlap with per-language testing skills.

Suggestions

Add the synonyms users naturally say for this workflow — "TDD", "test-driven development", "write a failing test first" — to the trigger phrasing to improve recall.

Narrow the trigger slightly (e.g. "when changing code in any language") or name the competing per-language unit-test skills as neighbors to reduce overlap risk.

DimensionReasoningScore

Specificity

Lists five distinct concrete actions — "reproduce the problem with a failing test first", "watch it fail for the right reason", "make the smallest change that passes", "refactor", "show the test output" — which matches the comprehensive-coverage anchor rather than the score-4 anchor with minor gaps.

5 / 5

Completeness

Explicitly answers both questions: "Use before changing code to fix a bug or add behavior, in any language, even when the user just says 'fix it'" (when) and the enumerated red-green-refactor loop with evidence (what), matching the anchor requiring concrete trigger phrases for both.

5 / 5

Trigger Term Quality

Includes natural phrases users actually say ("fix a bug", "add behavior", "even when the user just says 'fix it'") but omits common synonyms such as "TDD", "test-driven", "write tests", or "unit test", so it falls just below comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The red-green-refactor loop with shown test output is a clear niche, but the trigger "before changing code to fix a bug or add behavior, in any language" is broad and overlaps closely with per-language unit-test framework skills, leaving minor conflict risk rather than minimal.

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