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

Content

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 well-structured workflow for creating tracks with clear sequencing, validation gates, and error handling. However, it is significantly over-verbose — full file templates, interactive question scripts, and boilerplate that Claude could easily generate are all spelled out inline, consuming excessive tokens. The content would benefit greatly from extracting templates into referenced files and trusting Claude to fill in standard patterns.

Suggestions

Extract the full markdown templates (spec.md, plan.md, metadata.json, index.md) into separate reference files and link to them from the main skill, reducing inline verbosity by ~50%.

Remove or drastically shorten the interactive question scripts — Claude can formulate appropriate questions from brief bullet-point guidance without needing the exact prompt text spelled out.

Provide the referenced `resources/implementation-playbook.md` as a bundle file, or remove the reference if it doesn't exist.

Condense the track classification section to a simple list rather than a formatted prompt block — Claude knows how to ask users to choose from options.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~250+ lines, with extensive template boilerplate that Claude could generate on its own. The full markdown templates for spec.md, plan.md, metadata.json, and index.md are spelled out in detail when a brief structural description would suffice. The interactive question scripts are also overly detailed for Claude's capabilities.	1 / 3
Actionability	The skill provides highly concrete, executable guidance: exact file paths, directory structures, JSON schemas, markdown templates, specific naming conventions (e.g., `{shortname}_{YYYYMMDD}`), and step-by-step commands. Every step is copy-paste ready with specific formats and examples.	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. It includes explicit validation checkpoints (user review gates after spec and plan), error handling with rollback instructions, and feedback loops for edits.	3 / 3
Progressive Disclosure	There is one reference to `resources/implementation-playbook.md` for detailed examples, but the bulk of the content is monolithic — full templates for spec.md, plan.md, metadata.json, and index.md are all inline. These templates could be split into separate reference files to keep the main skill leaner. No bundle files are provided to support the referenced path.	2 / 3
	Total	9 / 12 Passed

Description

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 belongs to, or when Claude should select this skill. The vague terminology makes it nearly impossible to distinguish from other planning or creation-oriented skills.

Suggestions

Define what 'track' means in this context (e.g., project track, learning track, feature track) and list specific concrete actions like 'define milestones, create task breakdowns, set phase dependencies'.

Add an explicit 'Use when...' clause with natural trigger terms a user would say, such as 'Use when the user asks to plan a new project, create a roadmap, or break work into phases'.

Include domain-specific keywords and file types or artifacts involved to reduce ambiguity and conflict with other 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' guidance or explicit trigger clause. 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 especially ambiguous (music track? project track? race track?) and the other terms are generic project management jargon.	1 / 3
Distinctiveness Conflict Risk	The description is extremely generic and could overlap with project planning, task management, music production, or any number of other skills. 'Track' and 'specification' are too ambiguous to carve out a clear niche.	1 / 3
	Total	4 / 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: 88d1e11

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