CtrlK
BlogDocsLog inGet started
Tessl Logo

tdd-workflows-tdd-red

Generate failing tests for the TDD red phase to define expected behavior and edge cases.

56

Quality

62%

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-red/SKILL.md
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 well-structured and actionable with a concrete example and framework patterns, supported by a validation section. Its main weaknesses are redundancy between the prompt template and body sections, inlined content that would benefit from reference files, and the absence of an explicit error-recovery feedback loop.

Suggestions

Move the large Prompt Template and framework-specific patterns into reference files (e.g., references/prompt-template.md, references/framework-patterns.md) and link to them to improve progressive disclosure and reduce duplication.

De-duplicate content that appears both in body sections and inside the Prompt Template to tighten conciseness.

Add an explicit validation feedback loop (e.g., "If tests pass or fail for the wrong reasons, revise and re-run") to lift workflow clarity.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, but the large Prompt Template duplicates content already covered in body sections (Test Structure, Behavior Coverage, Edge Cases), creating avoidable redundancy.

3 / 5

Actionability

Provides an executable TypeScript Jest example, concrete framework patterns (Jest, pytest, Go, RSpec), and a parameterized prompt template; minor gaps include TS-only example and absent concrete run/verify commands.

4 / 5

Workflow Clarity

A clear numbered Instructions sequence and a Validation section with checkpoints are present, but there is no explicit error-recovery feedback loop (fail → fix → retry) to reach a 5.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but at ~158 lines with no bundle files, content that could be split out (framework patterns, the full prompt template, edge-case categories) is inlined, and the simple-skill exception does not apply.

3 / 5

Total

14

/

20

Passed

Description

61%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 clearly states what the skill does within a specific TDD niche, but it lacks an explicit "when to use" trigger clause and its listed actions are conceptual rather than comprehensive. It is reasonably distinctive and uses natural developer terminology.

Suggestions

Add an explicit trigger clause, e.g. "Use when starting the TDD red phase, writing failing tests, or defining expected behavior before implementation."

Make the actions more concrete and comprehensive (e.g., "generate framework-appropriate failing unit, integration, and contract tests") to lift specificity.

Add a few natural synonyms (e.g., "unit tests", "test cases") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (TDD red phase) and a couple of actions ("Generate failing tests", "define expected behavior", "edge cases"), but the actions are conceptual rather than a comprehensive concrete listing.

3 / 5

Completeness

Has a clear "what" but no explicit "Use when..." trigger clause; "for the TDD red phase" only weakly implies when, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural developer terms ("failing tests", "TDD red phase", "edge cases") that users would actually say, though it lacks common synonyms like "unit tests" or "write tests".

4 / 5

Distinctiveness Conflict Risk

The "TDD red phase" niche is mostly distinct from general test-generation skills, with only minor overlap risk against closely related testing 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-skills
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.