conductor-implement

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

1.44x

Quality

61%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/conductor-implement/SKILL.md

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

Quality

Content

70%Weight 40%Scale 1-5

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 well-sequenced, highly actionable workflow with strong validation and error-recovery design, but it carries generic boilerplate padding and fails to split its large content into the referenced bundle files.

Suggestions

Remove the generic 'Use this skill when'/'Do not use this skill when'/'Instructions' boilerplate, which restates obvious advice and wastes context.

Create the referenced 'resources/implementation-playbook.md' (or drop the reference) so progressive disclosure points to real files rather than a dangling path.

Extract the lengthy error-handling menus and metadata.json schema into a separate reference file, keeping SKILL.md as a lean overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The core workflow is efficiently procedural, but generic boilerplate sections ('Use this skill when', 'Do not use this skill when', and the abstract 'Instructions' list of best-practice platitudes) add padding that Claude does not need.	3 / 5
Actionability	Concrete, executable guidance abounds — specific git commit commands, the metadata.json schema, exact status markers ([ ], [~], [x]), and precise file paths — with only minor gaps where steps remain abstract ('Parse for incomplete tracks').	4 / 5
Workflow Clarity	A clearly sequenced multi-step process (pre-flight → selection → execution loop → phase/track completion) with explicit validation checkpoints, a CRITICAL approval gate between phases, and dedicated error-recovery feedback loops for tool, test, and git failures.	5 / 5
Progressive Disclosure	Section headers give reasonable structure, but ~380 lines are inlined monolithically in SKILL.md with no bundle files present, and the sole reference to 'resources/implementation-playbook.md' points to a file that does not exist in the bundle.	3 / 5
	Total	15 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 third-person and names a concrete domain, but it omits any explicit 'when to use' trigger guidance and offers only a single high-level action, leaving it competent but not comprehensive.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when implementing tasks from a Conductor track plan or following a TDD workflow on a tracked feature.'

Expand the action list beyond 'Execute tasks' to mention selection, status tracking, commits, and phase verification for greater specificity.

Include natural user-facing synonyms ('implement a track', 'work on planned tasks') alongside the Conductor jargon to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('track's implementation plan', 'TDD workflow') and one concrete action ('Execute tasks'), but coverage is not comprehensive — it does not enumerate the sub-actions the body actually performs (selection, status updates, commits, verification).	3 / 5
Completeness	It states a clear 'what' ('Execute tasks from a track's implementation plan following TDD workflow') but provides no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Relevant terms ('tasks', 'implementation plan', 'TDD workflow', 'track') are present but lean toward Conductor-specific jargon and miss natural variations a user might actually say ('implement a feature', 'work on a track', 'follow TDD').	3 / 5
Distinctiveness Conflict Risk	The 'track's implementation plan' framing ties it to a distinct Conductor niche with minimal conflict risk, though generic dev terms like 'TDD workflow' leave minor overlap with other implementation skills.	4 / 5
	Total	13 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/conductor-implement/SKILL.md
Commit: 57c135b

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