conductor-implement
Execute tasks from a track's implementation plan following TDD workflow
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill conductor-implement65
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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 provides a basic understanding of the skill's purpose but is too terse and lacks critical guidance for skill selection. It fails to include explicit trigger conditions and doesn't enumerate the specific actions involved in the TDD workflow. The technical terminology may not match how users naturally phrase requests.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when implementing features from a track plan', 'when following TDD', or 'when the user mentions red-green-refactor'
List specific concrete actions such as 'write failing tests, implement code to pass tests, refactor, update implementation plan status'
Include natural language variations users might say: 'test-driven development', 'write tests first', 'implement next task from plan'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (track implementation plan, TDD workflow) and implies actions (execute tasks), but doesn't list specific concrete actions like 'write tests', 'implement features', 'refactor code'. | 2 / 3 |
Completeness | Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant terms ('TDD', 'implementation plan', 'track') but uses somewhat technical jargon. Missing common variations users might say like 'test-driven', 'red-green-refactor', 'write tests first'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'track' and 'implementation plan' provides some specificity, but 'execute tasks' and 'TDD workflow' are broad enough to potentially overlap with general coding or testing skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent workflow clarity and explicit validation checkpoints throughout. The main weakness is its length - while comprehensive, some sections (error handling options, completion summary) are repetitive and could be condensed or extracted to reference files. The skill excels at providing concrete, executable guidance for a complex multi-phase implementation process.
Suggestions
Extract repetitive error handling option blocks into a shared pattern or reference file to reduce redundancy
Consider moving the detailed JSON schema examples and completion summary templates to a separate reference file, keeping only essential inline examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundant explanations and verbose formatting. The extensive code blocks and repeated patterns (like error handling options) could be tightened. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | Provides highly concrete, executable guidance with specific file paths, exact git commands, JSON schemas, and clear decision trees. The task execution loop, commit commands, and metadata updates are all copy-paste ready. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit validation checkpoints, phase completion verification, user approval gates, and clear error handling with recovery options. The TDD workflow has explicit red/green/refactor phases with halt conditions. | 3 / 3 |
Progressive Disclosure | References external files appropriately (workflow.md, product.md, etc.) but the skill itself is monolithic at ~300 lines. The implementation playbook reference is good, but more content could be split into separate reference files for error handling patterns or the resumption logic. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 12 / 16 Passed | |
- 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.