tdd-workflows-tdd-green

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

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill has a clear, well-sequenced workflow with an explicit test-run checkpoint, but its code examples are incomplete/malformed and a referenced playbook file is missing, holding actionability and progressive disclosure at the mid level.

Suggestions

Fix the malformed Python code blocks (missing opening fence and stray closing fence) and make examples complete enough to be executable, or move them into the referenced playbook.

Resolve the dangling reference by either creating resources/implementation-playbook.md or removing the Resources pointer.

Move the refactor (Class-based/Generic view, Express layering) examples out of this green-phase skill, since refactoring is explicitly excluded by the "Do not use when" section.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and does not explain TDD basics Claude already knows, but it carries off-topic refactor examples (in a skill whose own "Do not use" section excludes refactoring) and malformed code fences, so it is not fully tight.	2 / 3
Actionability	It gives concrete code fragments and a numbered procedure, but the code is incomplete (undefined Product model, missing imports, broken Python fences) and the instructions lack specific commands, matching the level-2 anchor.	2 / 3
Workflow Clarity	The Instructions give a clear 4-step sequence with an explicit validation checkpoint ("Run tests after each change to confirm progress"), which for this simple skill meets the level-3 anchor of a clear sequence with explicit validation.	3 / 3
Progressive Disclosure	Sections are well organized, but the body references resources/implementation-playbook.md which does not exist in the bundle, and substantial code examples are inlined rather than split out, matching the level-2 anchor.	2 / 3
	Total	9 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concrete and scoped to the TDD green phase, but it is a single-action statement with no explicit usage triggers, leaving every dimension at the mid level.

Suggestions

Add an explicit "Use when..." clause naming natural triggers (e.g., "Use when moving from red to green in a TDD cycle or when making failing tests pass") to raise completeness and trigger_term_quality.

List a couple of concrete actions (e.g., "write the minimal implementation, run the tests, record shortcuts for the refactor phase") to move specificity toward multiple specific actions.

Avoid jargon-only phrasing by pairing "TDD green phase" with plain-language terms a user would actually say.

Dimension	Reasoning	Score
Specificity	It names a concrete action ("Implement the minimal code needed to make failing tests pass") but describes a single action rather than listing multiple specific actions, so it matches the level-2 anchor.	2 / 3
Completeness	It clearly answers "what" but provides no explicit "Use when..." trigger, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	"failing tests pass" is a natural phrase, but "TDD green phase" is jargon and common variations ("make tests pass", "fix failing tests", "red-green-refactor") are missing, matching the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The "TDD green phase" niche is fairly specific, but without explicit triggers it could still overlap with general test-fixing skills, matching the level-2 anchor rather than the distinct-trigger level-3 anchor.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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
Commit: e63f7dd

Reviewed: about 24 hours ago

Table of Contents

Discovery Implementation Validation

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.