conductor-new-track

Create a new track with specification and phased implementation plan

1.92x

Quality

61%

Does it follow best practices?

Impact

98%

1.92x

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-new-track/SKILL.md

The canonical home for this skill is conductor-new-track 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 clear, well-sequenced workflow with concrete templates and explicit review checkpoints, scoring high on workflow clarity and actionability. It is held back by generic boilerplate padding and a broken reference to a non-existent resources file with no actual bundle files.

Suggestions

Remove the generic filler in 'Instructions', 'Use this skill when', and 'Do not use this skill when' (e.g. 'Apply relevant best practices and validate outcomes') to tighten conciseness.

Either create `resources/implementation-playbook.md` and move the large spec/plan/metadata templates there, or delete the dangling reference on line 28 so progressive disclosure is honest.

Add one fully-worked concrete example (a sample spec.md and plan.md for a small feature) to lift actionability from 4 to 5.

Dimension	Reasoning	Score
Conciseness	The bulk is concrete templates and prompts, but generic boilerplate sections ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes', and the filler 'Use/Do not use this skill when' bullets) are unnecessary padding; this fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the noticeably-verbose 2-anchor.	3 / 5
Actionability	Copy-paste-ready templates for spec.md, plan.md, metadata.json, and index.md plus exact interactive Q1-Q6 prompts and a concrete track-ID format with examples provide mostly executable guidance with minor gaps (templates are skeletons with placeholders, no fully worked example); it exceeds the incomplete/pseudocode 3-anchor but falls short of the fully-worked 5-anchor.	4 / 5
Workflow Clarity	The body lays out a clear sequence (Pre-flight → Classification → Spec gathering → Spec generation → User review → Plan generation → User review → Track creation) with explicit validation checkpoints, edit-and-re-review feedback loops, and an Error Handling section with checklists, matching the 5-anchor ('explicit validation steps; feedback loops for error recovery; checklists').	5 / 5
Progressive Disclosure	Section headers give reasonable structure, but all content (large spec/plan/metadata templates) is inlined in one ~430-line file with no bundle files, and line 28 references `resources/implementation-playbook.md` which does not exist — a broken, unclearly-signaled reference; this fits the 3-anchor ('some structure, references present but not clearly signaled, content that should be separate is inline') better than the well-organized 4-anchor.	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 states a clear purpose and a couple of concrete deliverables but omits any 'Use when...' trigger guidance, which caps completeness and limits trigger-term quality. Adding explicit trigger phrases and synonyms would notably raise the score.

Suggestions

Append a 'Use when...' clause naming concrete triggers, e.g. 'Use when starting a new Conductor track — a feature, bug fix, chore, or refactor — that needs a spec and phased plan.'

Add natural synonyms/users might say (e.g. 'new feature', 'plan a task', 'scaffold a track') to broaden trigger-term coverage.

Optionally list the concrete artifacts produced ('generates spec.md, plan.md, metadata.json') to lift specificity toward 4-5.

Dimension	Reasoning	Score
Specificity	Quotes "Create a new track with specification and phased implementation plan" name the domain and two concrete deliverables (specification, phased plan), matching the 3-anchor ('Names domain and 1-2 concrete actions, but not comprehensive'); it is not 'several specific actions' (4) nor merely minimal/generic (2).	3 / 5
Completeness	The description gives a clear 'what' ("Create a new track with specification and phased implementation plan") but no explicit 'when' trigger guidance; per the rubric a missing 'Use when...' clause caps completeness at 3, and the 2-anchor requires a vague 'what' which this is not.	3 / 5
Trigger Term Quality	Terms like "new track", "specification", and "phased implementation plan" are domain-relevant but there is no "Use when..." trigger phrase and no synonyms/variations, fitting the 3-anchor ('Some relevant keywords but missing common variations'); it lacks the broader natural-term coverage of 4.	3 / 5
Distinctiveness Conflict Risk	"Create a new track with specification and phased implementation plan" carves a mostly distinct niche with minor overlap risk against related Conductor track skills; it is not the clear-trigger minimal-conflict case of 5 (no explicit triggers) but is more distinct than the broad-overlap 3-anchor.	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-new-track/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.