conductor-new-track

Create a new track with specification and phased implementation plan

1.92x

Quality

27%

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

55%

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

The skill provides a thorough, well-sequenced workflow with strong actionability and clear validation checkpoints, but it is severely bloated. Templates, question scripts, and boilerplate that Claude could generate from brief instructions are spelled out in full, consuming excessive tokens. The content would benefit enormously from splitting templates into referenced files and trusting Claude's existing knowledge of concepts like user stories and acceptance criteria.

Suggestions

Extract the spec.md, plan.md, metadata.json, and index.md templates into separate reference files (e.g., `resources/templates/`) and reference them from the main skill to dramatically reduce token usage.

Remove the verbose interactive question scripts (Q1-Q6 for each track type) and replace with a concise table or bullet list of what information to gather per track type — Claude knows how to ask questions.

Eliminate explanations of concepts Claude already knows (e.g., what user stories are, what acceptance criteria means, what phases are) and focus only on project-specific conventions and constraints.

Consolidate the completion message and error handling sections into a brief checklist rather than full prose blocks.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~250+ lines. It includes extensive template boilerplate that Claude could generate from minimal instructions. The interactive question scripts, markdown templates for spec.md/plan.md/metadata.json/index.md, and completion messages are all spelled out in full when brief structural guidance would suffice. Much of this content (how to write user stories, what acceptance criteria are, how to structure phases) is knowledge Claude already possesses.	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 procedures for every phase. The commands and file contents are 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/review checkpoints (user review of spec, user review of plan), and error handling with rollback guidance is included at the end.	3 / 3
Progressive Disclosure	The skill is a monolithic wall of text with all templates, question scripts, and detailed procedures inline. There is one reference to `resources/implementation-playbook.md` but no bundle files are provided. The extensive markdown templates for spec.md, plan.md, metadata.json, and index.md could easily be split into separate reference files, dramatically reducing the main skill's length.	1 / 3
	Total	8 / 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 a 'track' is, what domain it applies to, what concrete actions are performed, and when the skill should be selected. Without context, 'track' is ambiguous and the remaining terms are generic project management language that would conflict with many other skills.

Suggestions

Define what a 'track' means in this context (e.g., 'a development workstream', 'a music track', 'a learning track') and list specific concrete actions the skill performs.

Add a 'Use when...' clause with natural trigger terms a user would say, such as specific keywords or phrases that uniquely identify when this skill should be selected.

Include domain-specific terminology and file types or artifacts involved to distinguish this skill from generic project planning or specification-writing skills.

Dimension	Reasoning	Score
Specificity	The description uses vague language — 'track', 'specification', and 'phased implementation plan' are abstract concepts 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? racing track?) and the other terms are generic project management jargon.	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-specific 'track' creation. The ambiguity of 'track' makes it especially prone to false matches.	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: 6042393

Reviewed: about 3 hours 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.