conductor-new-track

Create a new track with specification and phased implementation plan

1.92x

Quality

31%

Does it follow best practices?

Impact

98%

1.92x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

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 underspecified. It fails to define what kind of 'track' is being created, what domain it applies to, and when Claude should select this skill. The vague terminology makes it nearly impossible to distinguish from other planning or specification-related skills.

Suggestions

Define what 'track' means in this context (e.g., project track, music track, curriculum track) and list specific concrete actions the skill performs.

Add a 'Use when...' clause with explicit trigger terms that a user would naturally say, such as specific file types, domain keywords, or task descriptions.

Include domain-specific terminology and distinguishing details to prevent overlap with other planning or specification skills.

Dimension	Reasoning	Score
Specificity	The description uses vague language — 'track', 'specification', and 'phased implementation plan' are abstract terms without concrete actions. It doesn't specify what kind of track, what the specification entails, or what the implementation plan involves.	1 / 3
Completeness	The description only vaguely addresses 'what' (create a track with spec and plan) and completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent.	1 / 3
Trigger Term Quality	The terms 'track', 'specification', and 'phased implementation plan' are not natural keywords a user would typically say. 'Track' is ambiguous (music track? project track? race track?) and the other terms are generic project management jargon without domain specificity.	1 / 3
Distinctiveness Conflict Risk	The description is extremely generic and could conflict with many skills related to project planning, specification writing, implementation planning, or any domain that uses 'tracks'. The ambiguity of 'track' makes it especially prone to false triggers.	1 / 3
	Total	4 / 12 Passed

Implementation

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides an extremely thorough and actionable workflow for creating tracks with clear sequencing, validation checkpoints, and error handling. However, it is significantly over-verbose—embedding full file templates, question scripts, and boilerplate that Claude could generate from brief instructions. The inline templates and repetitive structure would benefit greatly from being extracted into referenced files to improve token efficiency.

Suggestions

Extract the spec.md, plan.md, metadata.json, and index.md templates into a separate reference file (e.g., `resources/track-templates.md`) and reference it from the skill to dramatically reduce token count.

Condense the interactive question flows into a compact table or brief list per track type rather than full verbatim prompt blocks—Claude can generate conversational prompts from concise specifications.

Remove the 'Use this skill when' and 'Do not use this skill when' sections, which are generic filler that adds no actionable value.

Summarize the phase guidelines and plan structure in 3-4 bullet points instead of a full markdown template with placeholder text.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~250+ lines. It includes extensive template boilerplate, question scripts that Claude could generate dynamically, and detailed markdown templates for spec.md, plan.md, metadata.json, and index.md that inflate token count significantly. Much of this (like how to format markdown files or JSON metadata) is knowledge Claude already has.	1 / 3
Actionability	The skill provides highly concrete, executable guidance: exact file paths, directory structures, JSON schemas, markdown templates, specific question flows per track type, ID generation format with collision handling, and step-by-step creation procedures. Everything is copy-paste ready.	3 / 3
Workflow Clarity	The workflow is clearly sequenced: pre-flight checks → classification → interactive gathering → spec generation → user review → plan generation → user review → track creation → completion message. Each major step has explicit validation (user review gates before proceeding), and error handling with rollback instructions is included at the end.	3 / 3
Progressive Disclosure	There is one reference to `resources/implementation-playbook.md` for detailed examples, which is good. However, the massive amount of inline template content (spec.md template, plan.md template, metadata.json, index.md) could be split into separate reference files. The skill is essentially monolithic with all templates embedded inline.	2 / 3
	Total	9 / 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

Repository: sickn33/antigravity-awesome-skills
Commit: 93c57b2

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