conductor-implement

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

1.44x

Quality

65%

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/skills/conductor-implement/SKILL.md

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

Quality

Content

77%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 is a well-structured, actionable workflow with strong validation checkpoints and error-handling feedback loops. Its main weakness is progressive disclosure: it is effectively a monolithic file whose single external reference targets a non-existent resource.

Suggestions

Create the referenced resources/implementation-playbook.md (or correct the path) so the progressive-disclosure pointer resolves to a real file, or remove the reference if the detail is intentionally inline.

Move the large simulated console-output templates (menus, summaries, error dialogs) into a reference file to keep SKILL.md as a lean overview.

Tighten the verbose completion-summary and cleanup-offer blocks to essentials to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean instructions, file paths, and code/JSON blocks without explaining concepts Claude already knows; the simulated console menus and completion summaries add some length that could be trimmed but are functional templates.	4 / 5
Actionability	It provides executable git commands, a concrete metadata.json schema, and specific file-path operations, with only minor gaps where placeholders like {trackId} must be filled in.	4 / 5
Workflow Clarity	The task-execution loop is clearly sequenced with explicit validation checkpoints (test runs, phase verification) and feedback loops for error recovery, including 'CRITICAL: Wait for explicit user approval before proceeding to next phase' and HALT-on-failure options.	5 / 5
Progressive Disclosure	Content is well sectioned, but the lone reference ('open resources/implementation-playbook.md') points to a file that does not exist in any bundle directory, and the bulk of the workflow is inlined rather than split into reference files.	3 / 5
	Total	16 / 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 clearly states what the skill does but omits any explicit 'when to use it' trigger guidance, which limits completeness. It is domain-specific with low conflict risk, yet lacks the natural trigger phrases a user would say.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations, e.g. 'Use when executing tasks from a Conductor track plan or following a TDD workflow'.

Include natural user-facing synonyms such as 'implementation plan', 'TDD', 'test-driven development', and 'Conductor track' to broaden trigger coverage.

Consider listing 2-3 concrete actions (e.g. run TDD red/green/refactor cycles, update track status, commit per task) to lift specificity above a single named action.

Dimension	Reasoning	Score
Specificity	It names the domain ('track's implementation plan') and one concrete action ('Execute tasks ... following TDD workflow'), but coverage is not comprehensive — a single action is named rather than multiple.	3 / 5
Completeness	It gives a clear 'what' ('Execute tasks from a track's implementation plan following TDD workflow') but has no 'Use when...' clause or explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	'implementation plan', 'TDD workflow', and 'track' are relevant domain keywords, but common user-facing variations or synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	The Conductor track/TDD niche is fairly specific with minimal conflict risk against unrelated skills, though the phrasing could still overlap with general implementation guidance.	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/skills/conductor-implement/SKILL.md
Commit: 57c135b

Reviewed: 3 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.