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

72%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/tdd-workflows-tdd-green/SKILL.md

The canonical home for this skill is tdd-workflows-tdd-green in rmyndharis/antigravity-skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 lean, honest green-phase guide with a clear four-step workflow and a validation checkpoint, but it is undermined by a malformed Django code block (missing opening fence and header), absent test-run commands, and a Resources pointer to a nonexistent playbook file while the pattern content it should hold sits inline. Fixing the broken markdown and the dangling reference would lift actionability and progressive disclosure.

Suggestions

Fix the malformed Django section: add a missing section header (e.g., "## Django Patterns") and the opening ```python fence so "# Green Phase: Simple function" is a code comment rather than a rendered H1 heading and loose text.

Make the test-run step executable: specify the command to use (e.g., `pytest -x`, `npm test`) or instruct to use the project's existing test runner, and add a recovery loop for when tests still fail (reduce the change's scope and re-run).

Resolve the dangling reference: create `resources/implementation-playbook.md` (or correct the path to the actual bundle location) and move the Django/Express pattern catalogs into it, keeping SKILL.md as a concise overview.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanations or padding ("Review failing tests and identify the smallest fix" assumes competence), but the three-variant Django block and the inline framework pattern catalogs add bulk that could be trimmed. Not a 5 because those pattern dumps include redundancy that doesn't all earn its place inline.

4 / 5

Actionability

The numbered instructions and Express code are concrete, but there is no command for actually running tests, and the Django section is malformed (missing opening code fence and section header), so "# Green Phase: Simple function" renders as an H1 with the code as loose text. Not a 4 because key executable details (test-run commands, correct fencing) are missing; not a 2 because real executable code and specific steps are present.

3 / 5

Workflow Clarity

"1. Review failing tests... 2. Implement the minimal change... 3. Run tests after each change to confirm progress... 4. Record shortcuts or debt" is a clear sequence with an explicit validation checkpoint. Not a 5 because there is no error-recovery loop (what to do when tests still fail) or stopping criterion; not a 3 because a checkpoint is explicitly present.

4 / 5

Progressive Disclosure

Section structure is present (Use/Do not use/Instructions/Safety/Resources), but the single reference "resources/implementation-playbook.md" points to a file that does not exist in the bundle, and the Django/Express pattern catalogs are inlined instead of deferred to that reference. Not a 2 because the sections are reasonably organized rather than minimal; not a 4 because the one reference is broken and detailed content is not appropriately split.

3 / 5

Total

14

/

20

Passed

Description

70%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, third-person description that clearly states what the skill does and embeds when to use it via the TDD green-phase qualifier. Its main gaps are a single-action scope, no separate "Use when" trigger clause, and missing common synonyms like "test-driven development".

DimensionReasoningScore

Specificity

Names the domain ("TDD green phase") and one concrete action ("Implement the minimal code needed to make failing tests pass"), matching the 1-2-concrete-actions anchor. Not a 4 because it lists only a single action rather than several specific capabilities.

3 / 5

Completeness

Has a clear "what" and an explicit embedded "when" ("in the TDD green phase") that qualifies as explicit trigger guidance, though it could be more explicit as a separate "Use when..." clause. Not a 3 because the when is stated rather than merely implied; not a 5 because there is no concrete standalone trigger phrase.

4 / 5

Trigger Term Quality

Includes natural phrases users would say in this niche ("failing tests", "TDD", "green phase", "minimal code"), but misses common variations like "test-driven development" or "red-green-refactor". Not a 3 because multiple natural terms are present, not just one generic keyword.

4 / 5

Distinctiveness Conflict Risk

The TDD green phase is a clear niche distinct from red-phase or refactoring skills, but "make failing tests pass" would also naturally trigger outside a formal TDD cycle, creating minor overlap risk. Not a 5 due to that broad triggering potential.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/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.