conductor-implement

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

Quality

56%

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

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers a clear, well-sequenced TDD implementation workflow with strong validation checkpoints and error-handling feedback loops, but it is a long monolithic document whose actionable guidance is partly template placeholders mixed with generic filler.

Suggestions

Trim the generic 'Instructions' section and condense the fixed menu/JSON template blocks to only the structural essentials to improve token efficiency.

Split large reference material (error-handling templates, the metadata.json schema, menu formats) into a referenced file and link to it from a concise overview to enable progressive disclosure.

Replace abstract guidance like 'Apply relevant best practices' and 'Manual verification as needed' with concrete, specific steps to raise actionability.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and avoids explaining concepts Claude already knows, but the generic 'Instructions' bullets and large fixed menu/JSON template blocks are padding that could be tightened.	2 / 3
Actionability	Provides concrete, executable git commands and specific file paths with status transitions, but much is template-style with placeholders and the guidance also includes abstract filler like 'Apply relevant best practices' and an illustrative 'npm test / pytest / etc.'.	2 / 3
Workflow Clarity	Clear numbered task-execution sequence with explicit validation steps (Red/Green/Refactor test runs, phase verification), feedback loops for error recovery, and CRITICAL wait-for-approval checkpoints between phases.	3 / 3
Progressive Disclosure	Well-organized into clear sections, but it is a ~380-line monolithic SKILL.md with no bundle/reference files and no signaled one-level-deep references; large template and JSON content that could be split out is inline.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 is concise and names a clear niche with a couple of concrete actions, but it omits any explicit 'Use when...' trigger guidance and only lists a couple of actions, leaving it at the mid-level across all dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when implementing tasks from a Conductor track plan, running TDD red/green/refactor cycles, or resuming an in-progress track.'

List more concrete actions (e.g. verify checkpoints, commit per task, update plan.md/metadata.json) to raise specificity and distinctiveness.

Include natural user-facing terms like 'implement a track', 'run TDD', 'resume implementation' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('track's implementation plan') and a couple of actions ('Execute tasks', 'following TDD workflow'), but does not enumerate multiple specific concrete actions like verifying, committing, or phase-gating.	2 / 3
Completeness	Clearly states what the skill does, but the 'when' is entirely missing from the description field with no explicit trigger guidance, capping completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes some relevant domain keywords ('TDD workflow', 'implementation plan') but lacks natural trigger variations a user would actually say and has no 'Use when...' trigger phrase.	2 / 3
Distinctiveness Conflict Risk	Has a recognizable niche (Conductor tracks, TDD) but 'implement track tasks' could overlap with general coding/implementation skills and distinct trigger terms are absent.	2 / 3
	Total	8 / 12 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: e63f7dd

Reviewed: about 5 hours 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.