conductor-implement
Execute tasks from a track's implementation plan following TDD workflow
47
35%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/conductor-implement/SKILL.mdQuality
Discovery
22%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 vague and lacks concrete actions, explicit trigger terms, and a 'Use when...' clause. While it references TDD and implementation plans, it fails to explain what specific actions the skill performs or when Claude should select it. It would be difficult for Claude to reliably choose this skill from a large pool of available skills.
Suggestions
Add a 'Use when...' clause specifying explicit triggers, e.g., 'Use when the user asks to implement the next task from a track plan, write tests first, or follow a TDD red-green-refactor cycle.'
Replace 'Execute tasks' with specific concrete actions, e.g., 'Writes failing tests, implements code to pass tests, refactors, and marks tasks complete in a track's implementation plan.'
Define what 'track' means in this context and add natural user terms like 'test-driven development', 'write tests first', 'red-green-refactor' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'TDD workflow' and 'implementation plan' but does not list any concrete actions (e.g., write tests, run tests, implement code, refactor). 'Execute tasks' is vague and abstract. | 1 / 3 |
Completeness | The 'what' is vaguely stated ('execute tasks') and there is no 'when' clause or explicit trigger guidance at all. The absence of a 'Use when...' clause caps this at 2, but the weak 'what' brings it to 1. | 1 / 3 |
Trigger Term Quality | Includes 'TDD' and 'implementation plan' which are somewhat relevant keywords, but 'track' is ambiguous and it misses natural user terms like 'test-driven development', 'red-green-refactor', 'write tests first', or 'test then implement'. | 2 / 3 |
Distinctiveness Conflict Risk | 'TDD workflow' and 'track's implementation plan' provide some specificity that narrows the domain, but 'execute tasks' is generic enough to overlap with any task execution or planning skill. The term 'track' is unclear and could conflict with other project management skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
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 handling, but suffers significantly from verbosity. The content is roughly 3x longer than necessary, with many sections spelling out UI prompts, JSON schemas, and procedural descriptions that could be dramatically condensed. The actionability is moderate - while git commands and JSON structures are concrete, the core implementation logic relies on procedural descriptions rather than executable guidance.
Suggestions
Reduce verbosity by at least 50%: remove verbose UI prompt templates (Claude can generate appropriate prompts), eliminate the 'Do not use this skill when' and 'Limitations' boilerplate sections, and condense error handling options into a single compact table.
Move detailed sections (Track Completion, Progress Tracking JSON schema, Resumption logic) into a separate reference file and link to it, keeping SKILL.md as a concise overview.
Replace procedural descriptions like 'Parse plan.md to find next incomplete task' with concrete examples showing actual regex/parsing patterns or file content snippets that demonstrate the expected format.
Consolidate the TDD workflow into a compact checklist rather than spelling out each phase with redundant announcement templates.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, with significant redundancy. Many sections describe things Claude can infer (e.g., explaining what metadata.json fields mean, spelling out every UI prompt verbatim, explaining what git errors might indicate). The 'Do not use this skill when' and 'Limitations' sections add little value. Much of this could be condensed to 1/3 the length. | 1 / 3 |
Actionability | The skill provides concrete steps and some executable commands (git commands, JSON structures), but much of the guidance is procedural description rather than executable code. The TDD workflow sections use placeholder text rather than real executable examples. Many steps describe what to do conceptually ('Parse plan.md to find next incomplete task') without showing how. | 2 / 3 |
Workflow Clarity | The multi-step workflow is clearly sequenced with explicit phases (pre-flight, track selection, context loading, task execution loop, completion). Validation checkpoints are explicit (phase verification with user approval gates, error handling with HALT behavior). The critical rules section reinforces verification requirements. Error recovery options are well-defined. | 3 / 3 |
Progressive Disclosure | The skill references external files appropriately (workflow.md, resources/implementation-playbook.md, various conductor files) but the SKILL.md itself is monolithic - it inlines extensive detail about every sub-process that could be split into separate reference files. The track completion section alone has 5 sub-sections that could be a separate document. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%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
93c57b2
- 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.