conductor-implement

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

Quality

40%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/conductor-implement/SKILL.md

Quality

Content

47%

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

This skill has excellent workflow clarity with well-defined phases, validation checkpoints, and error recovery paths. However, it is extremely verbose — much of the content consists of display templates and UI mockups that Claude could generate on its own, and it explains straightforward operations (updating JSON fields, parsing markdown checkboxes) in excessive detail. The skill would benefit significantly from being condensed to roughly one-third its current length while preserving the workflow structure.

Suggestions

Cut the content by 60-70%: remove all UI template mockups (selection menus, error displays, completion summaries) since Claude can generate appropriate user-facing text from brief instructions like 'display track selection menu with in-progress and pending tracks'.

Remove boilerplate sections ('Use this skill when', 'Do not use this skill when', 'Limitations') that consume tokens without adding actionable guidance.

Extract the detailed error handling scenarios and completion/cleanup workflows into a separate reference file, keeping only a brief summary in the main SKILL.md.

Replace verbose JSON examples (metadata.json) with a brief description of which fields to update, since Claude can infer JSON structure from the field names alone.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Contains extensive boilerplate sections ("Use this skill when", "Do not use this skill when", "Limitations") that add little value. Many UI mockups and menu displays are overly detailed. The skill explains obvious concepts like how to parse checkboxes and update JSON fields that Claude already knows how to do.	1 / 3
Actionability	Provides concrete workflow steps and some executable git commands, but most code blocks are display templates rather than executable code. Key details like how to actually parse plan.md, what commit_prefix values to use, and how to run verification are left vague or deferred to external files (workflow.md, implementation-playbook.md).	2 / 3
Workflow Clarity	The multi-step workflow is clearly sequenced with explicit phases (Red/Green/Refactor TDD cycle), validation checkpoints between phases requiring user approval, error handling with explicit halt-and-present-options behavior, and feedback loops for test failures and git errors. The critical rules section reinforces verification requirements.	3 / 3
Progressive Disclosure	References external files like `conductor/workflow.md`, `resources/implementation-playbook.md`, and various track files, but no bundle files are provided to support these references. The SKILL.md itself is monolithic — content like error handling templates, completion summaries, and resumption logic could be split into separate reference files rather than inlined.	2 / 3
	Total	8 / 12 Passed

Description

32%

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 too terse and lacks both concrete action details and explicit trigger guidance. While it references a specific methodology (TDD) and concept (track's implementation plan), it doesn't explain what concrete steps are performed or when Claude should select this skill. The jargon ('track') may be meaningful in context but is not self-explanatory.

Suggestions

Add a 'Use when...' clause with explicit trigger terms, e.g., 'Use when the user asks to implement the next task from a track, run TDD cycles, or work through an implementation plan.'

List specific concrete actions performed, e.g., 'Writes failing tests, implements code to pass tests, refactors, and marks tasks complete in the implementation plan.'

Expand trigger terms to include natural language variations like 'test-driven development', 'red-green-refactor', 'next step', 'implement task', and 'run tests'.

Dimension	Reasoning	Score
Specificity	It names a domain (TDD workflow, implementation plan) and a general action (execute tasks), but doesn't list specific concrete actions like 'write failing tests, implement code to pass tests, refactor' or other TDD steps.	2 / 3
Completeness	It partially answers 'what' (execute tasks from a track's implementation plan) but has no explicit 'when' clause or trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also quite vague, warranting a score of 1.	1 / 3
Trigger Term Quality	Includes some relevant terms like 'TDD', 'implementation plan', and 'track', but misses common natural language variations users might say such as 'test-driven development', 'red-green-refactor', 'run tests', 'implement feature', or 'next task'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'track's implementation plan' and 'TDD workflow' provides some specificity, but 'execute tasks' is generic enough to overlap with other task execution or implementation skills. The term 'track' is domain-specific but unexplained.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 6042393

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