conductor-new-track

Create a new track with specification and phased implementation plan

1.92x

Quality

67%

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

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

Quality

Content

81%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 highly actionable with complete templates and a well-sequenced, validated workflow including error handling. Its main weaknesses are some generic filler sections at the top and a reference to a playbook file that is not present in any bundle directory.

Suggestions

Remove or replace the generic 'Instructions' bullets ('Apply relevant best practices and validate outcomes') with concrete guidance already covered later in the skill.

Either create resources/implementation-playbook.md referenced in the Instructions or drop the reference, since no bundle directory exists.

Tighten the 'Use this skill when' / 'Do not use this skill when' sections to specific Conductor triggers rather than generic 'related to new track' phrasing.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient templates and steps, but the generic 'Use this skill when', 'Do not use this skill when', and 'Instructions' sections ('Apply relevant best practices and validate outcomes') are vague filler that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready templates for spec.md, plan.md, metadata.json, index.md, an explicit track-ID format with collision handling, and concrete user prompts, covering the common cases fully.	5 / 5
Workflow Clarity	A clear sequence (pre-flight, classification, spec gathering, generation, user review, plan generation, review, creation) with explicit validation checkpoints (spec/plan reviews) and an error-handling section providing feedback loops.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections with a one-level-deep reference ('resources/implementation-playbook.md'), but no bundle directories exist on disk and that single reference is not strongly signaled, leaving minor organization gaps.	4 / 5
	Total	17 / 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 but omits any 'when to use' trigger guidance, which caps completeness, and its actions are high-level deliverables rather than concrete capabilities. Trigger terms are relevant but lack synonyms or natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when starting a new feature, bug fix, chore, or refactor in a Conductor project and you need a spec and phased plan.'

Enumerate concrete actions instead of deliverables, e.g. 'gather requirements interactively, generate spec.md, produce a phased plan.md, scaffold the track directory, and register it in tracks.md.'

Include natural synonyms users might say (e.g. 'new feature', 'new task', 'scaffold a track') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('new track') and a couple of high-level actions ('with specification and phased implementation plan'), but these are deliverables rather than concrete low-level actions, so coverage is not comprehensive.	3 / 5
Completeness	It clearly states what the skill does, but provides no 'Use when...' clause or explicit trigger guidance, so per the cap completeness cannot exceed 3.	3 / 5
Trigger Term Quality	'new track', 'specification', and 'implementation plan' are relevant keywords, but the description lacks common synonyms, user-natural phrasings, or file/ID hints that would broaden trigger coverage.	3 / 5
Distinctiveness Conflict Risk	'Track' is a Conductor-specific concept giving it a clear niche with only minor overlap risk against other Conductor skills, though the description alone is not maximally distinctive.	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-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.