CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tdd-workflows-tdd-cycle

Coordinate the test-driven development cycle from requirements and failing tests through implementation, refactoring, and validation. Use when building a feature with a structured TDD workflow.

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 ./skills/tdd-workflows-tdd-cycle/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

55%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 workflow itself is excellently sequenced with gates, checklists, and error recovery, but the body is padded with templated filler and duplicated guidance, and the actionable specifics (flags, coverage tooling) lack executable commands. Splitting content into references and stripping boilerplate would lift both conciseness and progressive disclosure.

Suggestions

Delete the templated filler: the "Use this skill when" / "Do not use this skill when" sections, the generic Instructions bullets, the "[Extended thinking: ...]" block, and the trailing "TDD implementation for: [user request]" line.

Make the actionable elements executable: define what command the `--incremental` and `--suite` flags apply to, and specify how coverage reports are generated (e.g., a pytest/coverage command) instead of just listing metrics.

Deduplicate and externalize: consolidate Validation Checkpoints, Anti-Patterns, and Notes (which repeat the same constraints), and move coverage thresholds, refactoring triggers, and metrics tracking into a reference file so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

Whole sections are filler: the templated "Use this skill when" bullets ("Working on tdd workflows tdd cycle tasks or workflows"), generic Instructions ("Apply relevant best practices"), the bracketed "[Extended thinking: ...]" block, and the dangling "TDD implementation for: [user request]" trailer; checklists, anti-patterns, and notes also duplicate each other and re-explain red-green-refactor, which Claude already knows.

2 / 5

Actionability

Concrete specifics exist (80/75/100% coverage thresholds, complexity > 10 triggers, per-step role prompts, GATEs), but nothing is executable as written: the `--incremental` and `--suite` flags attach to no defined command, coverage report generation has no mechanism, and prompts are `[user request]` templates.

3 / 5

Workflow Clarity

Six phases and twelve numbered steps with explicit gates ("GATE: Do not proceed until all tests fail appropriately"), per-phase validation checklists, and a failure-recovery feedback loop (STOP, identify, rollback, resume) — a clear match for the top anchor.

5 / 5

Progressive Disclosure

No bundle files exist and all 220 lines are inlined under good headers; configuration, checklists, metrics, and anti-pattern lists would be better split into reference files, but the body remains navigable as structured.

3 / 5

Total

13

/

20

Passed

Description

75%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 solid description that clearly states what the skill does and when to use it, with natural TDD trigger terminology and a distinct niche. It could reach the top anchor by naming concrete operations and adding trigger synonyms like "red-green-refactor" or "test-first".

DimensionReasoningScore

Specificity

Enumerates concrete stages ("requirements and failing tests through implementation, refactoring, and validation") but at workflow-stage altitude; "coordinate" is abstract and no concrete operations like writing unit tests or measuring coverage are named.

4 / 5

Completeness

Clear "what" plus an explicit "Use when building a feature with a structured TDD workflow" clause; the when-clause is a single scenario rather than multiple concrete trigger phrases, which keeps it below a 5.

4 / 5

Trigger Term Quality

"test-driven development", "TDD workflow", and "building a feature" are phrases users naturally say; common synonyms like "red-green-refactor" or "test-first" are missing.

4 / 5

Distinctiveness Conflict Risk

TDD is a clear niche with distinct triggers, but "building a feature" is broad until qualified, leaving minor overlap risk with general testing or coding-workflow skills.

4 / 5

Total

16

/

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-cycle/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.