tdd-workflows-tdd-green

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

Quality

51%

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

50%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 is a compact, well-sectioned skill with usable code and a clear when/not-when split, but it is held back by malformed code fences, refactor-phase content mixed into a green-phase skill, an unverifiable resource reference, and no explicit failure-feedback loop.

Suggestions

Fix the malformed code fences: open each Django block (def product_list, class ProductListView(ListView)) with its own ```python fence so the examples render and copy-paste correctly.

Move the class-based-view and generic-view refactor examples into resources/implementation-playbook.md and keep SKILL.md focused on the minimal green-phase implementation, then ensure the referenced file actually exists.

Add an explicit validation feedback loop to the Instructions, e.g. 'If tests still fail, re-read the assertion, adjust the minimal change, and re-run until green' to lift workflow clarity above 3.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but the class-based and generic-view refactor examples belong to the refactor phase rather than green, adding tokens that could be trimmed or moved to the playbook.	3 / 5
Actionability	Concrete code is provided, but the Django code fences are malformed (missing opening fences) and the examples are illustrative rather than directly executable in context, leaving key details incomplete.	3 / 5
Workflow Clarity	A four-step sequence with a 'run tests after each change' checkpoint exists, but there is no explicit validate-on-failure / fix-and-retry feedback loop, so checkpoints remain implicit.	3 / 5
Progressive Disclosure	Sections are present and there is a one-level reference to resources/implementation-playbook.md, but no bundle file exists to verify it and refactor content is inlined that arguably belongs in the referenced file.	3 / 5
	Total	12 / 20 Passed

Description

53%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.

The description is clear and on-domain but one-dimensional: it states what the skill does without any explicit trigger guidance for when to invoke it. Adding a "Use when..." clause with natural synonyms would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when moving from red to green in a TDD cycle and you need the smallest code change to make failing tests pass.'

Include natural trigger synonyms users actually say, such as 'make tests pass', 'test-driven development', and 'red-green-refactor'.

Mention the broader set of concrete actions (e.g. write minimal implementation, run tests, defer refactoring) to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the TDD domain and one concrete action ("Implement the minimal code needed to make failing tests pass") but offers no broader coverage of actions, matching the 1-2 concrete actions anchor.	3 / 5
Completeness	The description gives a clear "what" but includes no "Use when..." trigger clause, so per the guideline completeness is capped at 3 with the "when" only weakly implied.	3 / 5
Trigger Term Quality	"TDD green phase" and "failing tests" are relevant keywords but common natural variations ("make tests pass", "red-green", "test-driven") are missing.	3 / 5
Distinctiveness Conflict Risk	The TDD green-phase framing is a fairly distinct niche with only minor overlap risk against the adjacent refactor phase.	4 / 5
	Total	13 / 20 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: 3eff4af

Reviewed: 1 day 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.