red-green-refactor
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like 'make the test pass', 'test coverage', or 'unit tests before implementation'.
Install with Tessl CLI
npx tessl i github:rohitg00/skillkit --skill red-green-refactor90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that follows best practices. It clearly explains the TDD workflow with specific actions, provides comprehensive trigger terms that developers would naturally use, and explicitly states when Claude should select this skill. The description is well-structured, uses third person voice, and is distinctive enough to avoid conflicts with general testing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'write a failing test first', 'implement the minimum code to make it pass', 'refactor while keeping tests green'. These describe the exact workflow steps clearly. | 3 / 3 |
Completeness | Clearly answers both what (guides red-green-refactor TDD workflow with specific steps) AND when (explicit 'Use when...' clause with comprehensive trigger scenarios and phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'TDD', 'write tests first', 'red-green-refactor', 'test-driven development', 'failing tests before code', 'make the test pass', 'test coverage', 'unit tests before implementation'. These are all phrases developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on TDD methodology with distinct triggers like 'red-green-refactor', 'failing test first', and 'tests before implementation'. Unlikely to conflict with general testing or coding skills due to the specific TDD workflow focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong skill with excellent actionability - the executable code examples clearly demonstrate each TDD phase. The workflow is well-structured with good decision points and verification steps. Minor improvements could be made by trimming explanatory prose Claude already knows and potentially splitting the detailed end-to-end example into a separate reference file.
Suggestions
Trim explanatory statements like 'The test should be focused on ONE behavior, named descriptively' - Claude knows good testing practices
Consider moving the 'End-to-End Example' section to a separate EXAMPLES.md file and linking to it, keeping SKILL.md as a leaner overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some explanatory text that Claude already knows (e.g., 'The test should be focused on ONE behavior, named descriptively'). The examples are good but some surrounding prose could be trimmed. | 2 / 3 |
Actionability | Excellent executable examples throughout - complete Jest test code, implementation code, and refactored versions that are copy-paste ready. Each phase shows concrete, runnable code with expected outputs. | 3 / 3 |
Workflow Clarity | Clear three-phase cycle with explicit steps, a complete end-to-end example showing the full workflow, decision points for when to write tests, and a verification checklist. The sequence is unambiguous with validation built into the cycle (run tests after each phase). | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is somewhat long (~120 lines) and could benefit from splitting detailed examples or the end-to-end walkthrough into separate files. References to related skills at the end are good but brief. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.