CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tdd-workflows-tdd-red

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

Quality

70%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 skill is highly actionable with a concrete subagent dispatch, a complete prompt template, an executable example, and explicit validation steps. Its main weakness is verbosity: framework-specific idioms, edge-case taxonomies, and TDD checklists restate knowledge Claude already has and pad the body.

Suggestions

Cut or drastically trim the Framework Patterns, Edge Case Categories, Quality Checklist, and Anti-Patterns sections — they restate knowledge Claude already has.

Add an error-recovery feedback loop to Validation, e.g. "If failures are due to syntax/import errors, regenerate the affected tests before proceeding."

Move the long prompt template to a references/ file (e.g. references/prompt-template.md) and keep a one-line pointer in SKILL.md.

DimensionReasoningScore

Conciseness

Several sections restate knowledge Claude already has: framework idiom listings for Jest/pytest/Go/RSpec ("t.Parallel()", "let for lazy loading"), a generic edge-case taxonomy (null/empty, boundaries), and standard TDD quality checklists and anti-patterns. This matches "noticeably verbose; several unnecessary explanations or padded sections" rather than the mostly-efficient anchor 3.

2 / 5

Actionability

The body provides fully executable guidance: numbered instructions, a concrete subagent dispatch (subagent_type="unit-testing::test-automator"), a copy-paste-ready prompt template with $ARGUMENTS substitution, and a complete runnable TypeScript test example. This matches the fully-executable, copy-paste-ready anchor.

5 / 5

Workflow Clarity

A clear sequence exists (identify behaviors → generate failing tests → ensure failures are for the right reason → document run commands) with an explicit Validation section listing four post-generation checks. It falls short of 5 because there is no error-recovery feedback loop (e.g. what to do when tests fail due to syntax/setup errors rather than missing behavior).

4 / 5

Progressive Disclosure

The single-file body is well organized into clear sections (use/do-not-use, instructions, role, template, validation, example) with no buried or nested references and no bundle files to navigate. Minor gap: the ~80-line prompt template is inlined where a separate reference file could keep SKILL.md leaner, matching the good-structure-with-minor-gaps anchor.

4 / 5

Total

15

/

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 with a well-scoped TDD niche, but omits any explicit "Use when" trigger guidance and lacks common trigger synonyms like "test-driven development". Adding a trigger clause would raise both completeness and trigger-term quality.

Suggestions

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

Include common user phrasings and synonyms such as "test-driven development" and "write tests first" to broaden natural trigger matching.

Name one more concrete capability (e.g. "covering happy paths, edge cases, and error handling") to strengthen specificity.

DimensionReasoningScore

Specificity

"Generate failing tests" is one concrete action within the named TDD red-phase domain, and "define expected behavior and edge cases" reads as purpose rather than additional actions — matching the anchor for domain plus 1-2 concrete actions. It is not a 4 because the description does not list several distinct specific actions.

3 / 5

Completeness

The "what" is clear (generate failing tests that define expected behavior), but there is no "Use when..." clause — "for the TDD red phase" only weakly implies timing, matching the anchor for clear what with weakly implied when. Per the guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural phrases a user would say are present ("failing tests", "TDD red phase", "edge cases", "expected behavior"), giving good keyword coverage. It falls short of 5 because common variations like "test-driven development", "write tests first", or framework terms are missing.

4 / 5

Distinctiveness Conflict Risk

"Failing tests for the TDD red phase" carves out a fairly distinct niche (red phase specifically, not green/refactor), so it is mostly distinct. It is not a 5 because "generate tests" still carries minor overlap risk with general test-generation skills.

4 / 5

Total

14

/

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

skills/tdd-workflows-tdd-red/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.