conductor-implement

Execute tasks from a track's implementation plan following TDD workflow

Quality

67%

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/conductor-implement/SKILL.md

Quality

Content

81%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 well-structured, actionable workflow with strong sequencing and validation checkpoints. The main weaknesses are minor boilerplate padding and a long single-file form that could benefit from splitting dialogue/error templates into reference files.

Suggestions

Remove the generic 'Use this skill when / Do not use this skill when / Instructions' boilerplate sections; they restate the description without adding actionable value.

Move the verbose error-handling, completion, and resumption terminal dialogue templates into a one-level-deep reference file (e.g. references/dialogues.md) linked from the main flow.

Tighten the dialogue code blocks to essential prompts only, reducing token cost while preserving the checkpoint behavior.

Dimension	Reasoning	Score
Conciseness	The body is largely lean process guidance, terminal templates, and concrete commands that assume Claude's competence; it is not a 5 because the generic 'Use this skill when / Do not use this skill when / Instructions' boilerplate at the top and some dialogue templates could be trimmed.	4 / 5
Actionability	Provides concrete file paths, executable git/commit commands, a full metadata.json schema, and step-by-step task execution; it is not a 5 because many commands carry placeholders ({trackId}, {commit_prefix}) that require resolution rather than being copy-paste ready.	4 / 5
Workflow Clarity	Multi-step process is clearly sequenced with explicit validation checkpoints (TDD red/green/refactor, phase verification, 'CRITICAL: Wait for explicit user approval') and feedback loops for error/test/git failures, matching the score-5 anchor.	5 / 5
Progressive Disclosure	Single self-contained file (no bundle dirs present) with well-organized, clearly headed sections; it is not a 5 because at ~380 lines some content (error-handling and completion dialogue templates) could be split into one-level-deep reference files, and the generic header sections add bulk.	4 / 5
	Total	17 / 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 states a clear purpose but omits any explicit 'when to use' trigger guidance and uses only moderately natural trigger terms. Adding a concrete 'Use when...' clause with user-facing phrases would lift completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when implementing a Conductor track, running TDD task cycles, or resuming an in-progress track.'

Add natural trigger synonyms users actually say (e.g. 'implement track', 'run TDD cycle', 'resume track') alongside the technical terms.

List 1-2 more concrete actions (e.g. 'commits each task, runs phase verification') to move specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('track's implementation plan', 'TDD workflow') and 1-2 concrete actions ('Execute tasks', 'following TDD workflow') but coverage is not comprehensive, matching the score-3 anchor; it is not a 4 because only two actions are listed.	3 / 5
Completeness	Provides a clear 'what' but no explicit 'Use when...' trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 3, so it cannot reach 4.	3 / 5
Trigger Term Quality	Contains relevant keywords ('implementation plan', 'TDD workflow') but these are moderately technical and miss common natural variations a user would say; it sits above 2 (which requires only generic keywords) but below 4 (good natural-term coverage).	3 / 5
Distinctiveness Conflict Risk	The phrase 'track's implementation plan following TDD workflow' ties it to a specific Conductor workflow niche with minimal overlap risk; it is not a 5 because the trigger phrasing is not as crisply distinctive as a fully expanded example.	4 / 5
	Total	13 / 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/conductor-implement/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.