conductor-implement

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

1.44x

Quality

55%

Does it follow best practices?

Impact

91%

1.44x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/conductor-implement/SKILL.md

The canonical home for this skill is conductor-implement in sickn33/agentic-awesome-skills

Quality

Content

77%Scale 1-3

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 implementation skill with excellent actionability and workflow clarity. It provides concrete commands, clear validation checkpoints, and proper error handling with user decision points. The main weakness is verbosity - some sections could be more concise, and the skill might benefit from splitting detailed subsections into referenced files.

Suggestions

Consider moving the detailed error handling templates and progress tracking JSON examples to a separate reference file to reduce the main skill's length

Tighten the Context Loading and Track Status Update sections by removing explanatory comments that Claude can infer from file names

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some verbose sections that could be tightened. The selection menu examples and error handling templates add value but some explanatory text is redundant (e.g., explaining what each file contains when Claude can infer this).	2 / 3
Actionability	Provides highly concrete, executable guidance with specific file paths, exact git commands, JSON structures, and clear decision trees. The workflow steps are copy-paste ready with explicit commands and status markers.	3 / 3
Workflow Clarity	Excellent multi-step workflow with explicit validation checkpoints, phase verification gates requiring user approval, clear error handling with options, and feedback loops for test failures. The 'CRITICAL: Wait for explicit user approval' callouts are well-placed.	3 / 3
Progressive Disclosure	References external files appropriately (workflow.md, product.md, implementation-playbook.md) but the skill itself is quite long with inline content that could potentially be split. The structure is good but the monolithic nature of the implementation loop could benefit from modularization.	2 / 3
	Total	10 / 12 Passed

Description

32%Scale 1-3

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 identifies a specific methodology (TDD) and context (track implementation plan) but lacks concrete action details and completely omits trigger guidance. The technical terminology may not match natural user language, and the absence of a 'Use when...' clause makes it difficult for Claude to know when to select this skill over others.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when implementing features from a track plan, following test-driven development, or when the user mentions TDD, red-green-refactor, or implementation tasks'

List specific concrete actions such as 'Write failing tests, implement code to pass tests, refactor, and mark tasks complete'

Include natural language variations users might say: 'write tests', 'implement feature', 'next task', 'TDD cycle'

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 (execute tasks from implementation plan with TDD) 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's implementation plan' and 'TDD workflow' provides some specificity, but 'execute tasks' is generic and could overlap with other task execution or coding skills.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/conductor-implement/SKILL.md
Commit: 7520423

Reviewed: ~15 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.