CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tdd-workflows-tdd-green

Implement the minimal code needed to make failing tests pass in the TDD green phase.

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/tdd-workflows-tdd-green/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 body has a sensible skeleton (when to use, instructions, safety) and a clear sequenced workflow, but it is undermined by a truncated opening code block, an orphaned "Role" convention no step uses, refactor examples that contradict the skill's stated scope, and a Resources pointer to a file that does not exist.

Suggestions

Create resources/implementation-playbook.md (or remove the reference) so the Resources section points to a real file.

Repair the opening Django code block (missing fence/heading and imports) and remove the refactor-phase examples or move them to the playbook, since the skill explicitly excludes refactoring work.

Delete the "Steps marked **Role**..." line — no step is marked Role — and add a concrete test-run command plus a retry step when tests still fail.

DimensionReasoningScore

Conciseness

The prose is tight with no over-explanation of TDD concepts, but the body carries refactor-phase code variants ("Refactor: Class-based view", "Refactor: Full layering") that contradict the skill's own "Do not use this skill when... refactoring" scope and waste tokens. Not 4 because this off-scope content is unnecessary material that should be trimmed.

3 / 5

Actionability

Real Django and Express code plus a 4-step instruction list provide concrete guidance, but the opening Django block is truncated (no opening fence, missing imports), Express examples reference undefined `users`/`userService`, and no actual test-run command is given. Not 4 because these gaps go beyond minor: the first example is malformed and the instructions stay high-level ("identify the smallest fix").

3 / 5

Workflow Clarity

The Instructions section gives a clear sequence (review failing tests, implement minimal change, run tests, record debt) with an explicit validation checkpoint ("Run tests after each change to confirm progress"). Not 5 because there is no error-recovery loop for when tests still fail and no concrete test command; not 3 because a checkpoint is explicitly present, not implicit.

4 / 5

Progressive Disclosure

The only external reference, "resources/implementation-playbook.md", does not exist in the bundle, so navigation fails entirely, and the pattern catalogs that the playbook was meant to hold are inlined in SKILL.md. Not 3 because a broken reference is a worse navigation failure than a present-but-unclear one, and the structure has defects (truncated opening block, orphaned "### Express Patterns" heading, "Role" convention with no matching steps).

2 / 5

Total

12

/

20

Passed

Description

62%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 concise, concrete, third-person description that clearly states what the skill does and scopes it to the TDD green phase. Its main gaps are the absence of an explicit trigger clause and missing natural synonyms for discovery.

Suggestions

Add an explicit trigger clause, e.g. "Use when moving from red to green in a TDD cycle or when implementing minimal code to make failing tests pass."

Include common trigger variations such as "make the tests pass", "red-green-refactor", or "test-driven development" to improve discoverability.

DimensionReasoningScore

Specificity

"Implement the minimal code needed to make failing tests pass" names the TDD domain and one concrete action, but does not list several specific actions. It is not 4 because coverage is a single action rather than several; not 2 because the action stated is concrete rather than generic.

3 / 5

Completeness

The "what" is clear (implement minimal code to pass failing tests) and the "when" is explicitly stated ("in the TDD green phase"), though it could be more specific with a dedicated trigger clause. Not 3 because the when is stated rather than merely implied; not 5 because there is no concrete "Use when..." trigger phrase listing trigger situations.

4 / 5

Trigger Term Quality

"failing tests" and "TDD green phase" are relevant keywords a TDD practitioner would say, but common variations like "make tests pass", "red to green", or "test-driven development" are absent. Not 4 because keyword coverage lacks these natural synonyms.

3 / 5

Distinctiveness Conflict Risk

"TDD green phase" carves out a clear niche with distinct triggers, with only minor overlap risk against closely related refactor-phase or test-writing skills. Not 5 because it shares TDD-cycle vocabulary with those adjacent skills.

4 / 5

Total

14

/

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

rmyndharis/antigravity-skills

Path

skills/tdd-workflows-tdd-green/SKILL.md

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.