tdd-orchestrator

Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/tdd-orchestrator/SKILL.md

Quality

Content

21%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 padded capabilities catalog with no executable guidance, no code, and no external references, relying on section headers alone for structure. It reads as a persona description rather than an actionable skill.

Suggestions

Replace abstract capability bullets and persona sections ('Expert Purpose', 'Behavioral Traits', 'Knowledge Base') with concrete, executable guidance — example commands, framework snippets, or step templates for the red-green-refactor cycle.

Add validation/verification checkpoints into the 'Response Approach' workflow (e.g., run tests → confirm red → implement → confirm green → refactor → re-run) rather than vague 'monitor compliance' steps.

Move the long capability and knowledge-base enumerations into separate reference files under ./references/ and link to them one level deep, keeping SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose: 'Expert Purpose', 'Behavioral Traits', and 'Knowledge Base' restate TDD concepts Claude already knows, and ~180 lines of capability bullet lists add little actionable signal; not a 1 because bullets are individually terse.	2 / 5
Actionability	Entirely abstract — 'Clarify goals... Apply relevant best practices and validate outcomes' and an 8-step 'Response Approach' describe rather than instruct, with no code, commands, or concrete steps anywhere.	1 / 5
Workflow Clarity	A rough sequence exists in 'Response Approach' (assess → establish → orchestrate → measure → ...), but steps are poorly defined and concrete validation checkpoints are absent, capping it at 2.	2 / 5
Progressive Disclosure	Section headers provide some structure, but no bundle files or external references exist and sprawling capability lists that belong in separate files are inlined; the under-50-line simple-skill exception does not apply to this ~180-line document.	3 / 5
	Total	8 / 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 third-person description that answers both what and when with good trigger keywords. It would reach the top band by replacing generic phrasing ('best practices') with concrete actions and adding specific user-mentionable trigger phrases.

Dimension	Reasoning	Score
Specificity	Names several concrete capabilities — 'red-green-refactor discipline, multi-agent workflow coordination', 'AI-assisted testing', 'governance' — though 'Enforces TDD best practices across teams' remains somewhat generic, keeping it just below comprehensive.	4 / 5
Completeness	Clearly states what it does and includes an explicit 'Use PROACTIVELY for TDD implementation and governance' trigger, but the 'when' lacks concrete trigger phrases (e.g., 'when the user mentions X'), so it is not a 5.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('TDD', 'test-driven development', 'red-green-refactor', 'TDD implementation and governance') but misses common synonyms like 'unit testing' or 'test-first'.	4 / 5
Distinctiveness Conflict Risk	The 'TDD orchestrator / multi-agent / governance' framing carves a clear niche with only minor overlap risk against general testing skills; not a 5 because 'TDD' alone could collide with a generic testing skill.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/tdd-orchestrator/SKILL.md
Commit: 3eff4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.