conductor-new-track

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

Create a new track with specification and phased implementation plan

55%

Overall

Validation — 81%

Implementation — 77%

Activation — 0%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata.version' is missing	Warning
license_field	'license' field is missing	Warning

	Total	13 / 16 Passed

Implementation

77%

This is a well-structured, highly actionable skill with excellent workflow clarity and explicit validation checkpoints at each major stage. The main weakness is verbosity - the inline templates and repeated patterns inflate the token count, and some content could be externalized to referenced files for better progressive disclosure.

Suggestions

Consider moving the full file templates (spec.md, plan.md, metadata.json) to a referenced templates file, keeping only brief descriptions inline

Consolidate the similar question patterns across track types into a more compact format, perhaps a table showing which questions apply to which track type

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some redundancy (e.g., repeated confirmation patterns, verbose template structures). The question flows and templates could be more condensed while preserving clarity.	2 / 3
Actionability	Provides fully concrete, copy-paste ready templates for all generated files (spec.md, plan.md, metadata.json, index.md), specific directory structures, and exact question sequences to follow.	3 / 3
Workflow Clarity	Excellent multi-step workflow with clear sequence: pre-flight checks → classification → interactive 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	References `resources/implementation-playbook.md` for detailed examples, but the skill itself is quite long (~300 lines) with all templates inline. The question sets for different track types could potentially be externalized for better organization.	2 / 3
	Total	10 / 12 Passed

Activation

This description is critically underdeveloped. It fails to explain what type 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', 'feature track') and list specific actions like 'define milestones, create task breakdowns, set dependencies'

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

Include domain-specific keywords that distinguish this from generic planning skills, such as file types, specific deliverables, or the system/context where tracks are used

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 phases involve. 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 'Use when...' clause. Both components are very weak.	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 implementation planning tools. 'Track' is undefined and could mean many things.	1 / 3
	Total	4 / 12 Passed

Reviewed

17 days ago

Table of Contents

Validation Implementation Activation

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.