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

63%

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

56%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 highly actionable with a strong executable example and explicit validation steps, but it is padded with duplicated guidance and framework basics Claude already knows, and the large embedded prompt template should live in a reference file. Trimming duplication and moving the template out would improve both conciseness and structure.

Suggestions

Move the ~80-line Prompt Template into a references/ file (e.g., references/prompt-template.md) and keep a short pointer plus the key constraints in SKILL.md.

Deduplicate the Instructions section against the Prompt Template — coverage of behavior, edge cases, and failure verification currently appears in both.

Cut the Framework Patterns and Quality Checklist entries that re-state basics Claude knows (Arrange-Act-Assert, RSpec let/let!, pytest fixtures), keeping only project-specific conventions.

Add an explicit error-recovery step to Validation: if tests fail due to setup/syntax errors rather than missing behavior, fix the test setup and re-run.

DimensionReasoningScore

Conciseness

The ~80-line embedded Prompt Template duplicates the Instructions section (behavior coverage, failure verification, edge cases), the Framework Patterns and Quality Checklist re-explain basics Claude already knows (Arrange-Act-Assert, RSpec let/let!, pytest fixtures), and the "[Extended thinking: ...]" line is meta-padding duplicating the Role section. This is noticeably verbose rather than mostly efficient.

2 / 5

Actionability

A complete, executable Jest example with mocks and a concrete prompt template with a [user request] placeholder provide mostly executable guidance; the minor gap is that no actual commands for running the tests are given in the skill itself.

4 / 5

Workflow Clarity

A clear four-step sequence is followed by an explicit Validation section ("Run tests - confirm they fail") plus a quality checklist, but an explicit error-recovery loop (e.g., what to do when tests fail for the wrong reasons such as syntax/import errors) is missing.

4 / 5

Progressive Disclosure

Section headers are clear and well-organized, but with no bundle files the ~80-line prompt template is inline content that clearly belongs in a separate reference file, leaving the structure only partially appropriate.

3 / 5

Total

13

/

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 names a concrete action and a well-scoped domain, but it lacks an explicit "Use when..." trigger clause and natural keyword variations. Adding trigger guidance and spelling out "test-driven development" would materially improve it.

Suggestions

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

Spell out "test-driven development" alongside "TDD" so users who don't use the acronym still match the description.

List one or two more concrete actions (e.g., covering happy paths, edge cases, and error handling) to broaden capability coverage.

DimensionReasoningScore

Specificity

"Generate failing tests" is a concrete action and the domain ("TDD red phase") is clearly named, but the remaining phrases ("to define expected behavior and edge cases") are purpose clauses rather than additional distinct actions, so coverage is not comprehensive.

3 / 5

Completeness

The "what" is clear (generate failing tests for the TDD red phase), but there is no "Use when..." clause or equivalent trigger guidance — the "when" is only weakly implied, capping this dimension at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Relevant keywords like "failing tests", "TDD red phase", and "edge cases" are present, but common natural variations such as "test-driven development" (spelled out), "write tests first", or "unit tests" are missing.

3 / 5

Distinctiveness Conflict Risk

The description is scoped to the red phase and failing tests, clearly distinguishing it from sibling green/refactor skills; only minor overlap risk exists with generic test-writing skills.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

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