conductor-new-track

Create a new track with specification and phased implementation plan

Install with Tessl CLI

npx tessl i github:sickn33/antigravity-awesome-skills --skill conductor-new-track

What are skills?

1.92x

Quality

38%

Does it follow best practices?

Impact

98%

1.92x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/conductor-new-track/SKILL.md

SKILL.md

Review

Evals

Quality

Discovery

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is critically weak across all dimensions. It fails to specify what kind of 'track' is being created, provides no concrete actions, lacks trigger terms users would naturally use, and has no guidance on when Claude should select this skill. The ambiguous terminology makes it nearly impossible to distinguish from other planning or specification-related skills.

Suggestions

Define what 'track' means in this context (e.g., 'learning track', 'project track', 'curriculum track') and list specific actions like 'define milestones, create module outlines, set dependencies'

Add a 'Use when...' clause with natural trigger terms users would say, such as 'Use when the user asks to create a curriculum, design a learning path, or plan a multi-phase project'

Include file types, domains, or specific outputs to distinguish this skill from generic planning skills (e.g., 'outputs a structured markdown document with phases, timelines, and deliverables')

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'specification' and 'phased implementation plan' without explaining what kind of track, what the specification contains, or what the implementation involves. No concrete actions are listed.	1 / 3
Completeness	The description only vaguely addresses 'what' (create a track with spec and plan) and completely lacks any 'when' guidance or explicit triggers. There is no 'Use when...' clause or equivalent.	1 / 3
Trigger Term Quality	The term 'track' is ambiguous (could mean music track, project track, learning track, etc.) and 'specification' and 'phased implementation plan' are generic technical jargon. Users would not naturally say these phrases when seeking this skill.	1 / 3
Distinctiveness Conflict Risk	The description is extremely generic and could conflict with project planning skills, specification writing skills, roadmap skills, or any planning-related skill. 'Track' is undefined and could mean many things.	1 / 3
	Total	4 / 12 Passed

Implementation

77%

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, highly actionable skill with excellent workflow clarity and explicit validation checkpoints. The main weakness is verbosity - the inline templates and question flows make it longer than necessary, and some boilerplate sections (use/don't use) add little value. The content would benefit from extracting templates to separate files.

Suggestions

Remove the 'Use this skill when / Do not use this skill when' sections - Claude can infer appropriate usage from the skill description

Extract the markdown templates (spec.md, plan.md, metadata.json, index.md) to a separate TEMPLATES.md file and reference it

Condense the interactive question flows into a more compact format, perhaps as a table or bulleted list rather than verbose code blocks

Dimension	Reasoning	Score
Conciseness	The skill is moderately efficient but includes some redundancy (e.g., repeated template structures, verbose markdown examples). The interactive question flows could be more condensed, and some sections like 'Use this skill when/Do not use' add little value for Claude.	2 / 3
Actionability	Highly actionable with concrete file structures, exact JSON schemas, specific markdown templates, and copy-paste ready content. Commands and file paths are explicit, and the workflow steps are executable.	3 / 3
Workflow Clarity	Excellent multi-step workflow with clear sequencing: pre-flight checks → classification → gathering → spec generation → user review → plan generation → user review → track creation. Includes explicit validation checkpoints (user review gates) and error handling section.	3 / 3
Progressive Disclosure	Content is well-structured with clear sections, but the skill is monolithic (~300 lines) with all templates inline. References to external files (implementation-playbook.md, product.md) exist but the bulk of content could benefit from splitting templates into separate reference files.	2 / 3
	Total	10 / 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

Reviewed: 1 day 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.