track-management

Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.

Quality

42%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/track-management/SKILL.md

The canonical home for this skill is track-management in rmyndharis/antigravity-skills

Quality

Content

22%Scale 1-5

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

This skill is essentially a placeholder that describes what track management is about without providing any actual guidance on how to do it. The instructions are generic boilerplate ('clarify goals', 'apply best practices') that could apply to any skill and teach Claude nothing specific about tracks, spec.md format, plan.md structure, status markers, or the tracks.md registry. Nearly all value is deferred to a referenced resource file that wasn't provided for verification.

Suggestions

Add concrete templates or examples for spec.md and plan.md files showing the expected format, required sections, and metadata fields.

Define the track lifecycle explicitly with states/transitions (e.g., draft → specified → planned → in-progress → complete) and what actions move between them.

Include specific commands or steps for creating a track, registering it in tracks.md, and updating status markers — with actual file path conventions and naming patterns.

Replace the generic Instructions bullets ('Clarify goals', 'Apply relevant best practices') with domain-specific guidance that Claude wouldn't already know.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections add some value but the 'Do not use this skill when' section is essentially vacuous ('task is unrelated' and 'need a different tool'). The Instructions section is generic boilerplate that doesn't teach Claude anything specific about track management.	3 / 5
Actionability	The content is entirely vague and abstract. There are no concrete commands, code examples, file formats, templates, or specific steps for creating tracks, writing spec.md, creating plan.md, or managing lifecycle. Instructions like 'Clarify goals' and 'Apply relevant best practices' are not actionable guidance.	1 / 5
Workflow Clarity	Despite describing a multi-phase lifecycle (specification, planning, implementation), there is no actual workflow sequence, no steps for creating or managing tracks, no validation checkpoints, and no description of the track lifecycle states or transitions.	1 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable one-level-deep reference. However, no bundle files were provided to verify the reference exists, and the SKILL.md itself contains almost no substantive content to serve as a useful overview — it defers nearly everything to the referenced file without providing even a minimal quick-start.	3 / 5
	Total	8 / 20 Passed

Description

62%Scale 1-5

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

The description provides a reasonable overview of the skill's purpose with an explicit 'Use when' clause and domain-specific identifiers (Conductor, spec.md, plan.md). However, it relies on generic verbs ('creating, managing, working with') rather than listing specific concrete actions, and the trigger terms lean toward internal jargon rather than natural user language.

Suggestions

Replace generic verbs with specific actions, e.g., 'Generates spec.md files, breaks down plans into tasks in plan.md, updates track status, and manages track lifecycle from creation to completion.'

Add natural trigger phrases users might say, such as 'Use when the user asks to start a new feature, write a spec, create a plan, track a bug fix, or manage work items in Conductor.'

Dimension	Reasoning	Score
Specificity	Names the domain ('Conductor tracks') and mentions a few concrete artifacts (spec.md, plan.md, track lifecycle operations), but the actions are described generically as 'creating, managing, or working with' rather than listing specific concrete actions like 'generate spec files, break down plans into tasks, update track status'.	3 / 5
Completeness	Has both 'what' (creating/managing Conductor tracks as logical work units for features, bugs, refactors) and 'when' ('Use this skill when creating, managing, or working with Conductor tracks'). The 'when' clause is present and explicit but could be more specific with concrete trigger scenarios.	4 / 5
Trigger Term Quality	Includes some relevant keywords like 'tracks', 'spec.md', 'plan.md', 'features', 'bugs', 'refactors', and 'Conductor'. However, these are mostly domain-specific jargon; it misses natural user phrases like 'create a new feature', 'start a track', 'write a spec', or 'plan out work'.	3 / 5
Distinctiveness Conflict Risk	The mention of 'Conductor tracks' and specific files (spec.md, plan.md) creates a fairly distinct niche. There's minor overlap risk with general project management or documentation skills, but the specific tool name and file references help differentiate it.	4 / 5
	Total	14 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/track-management/SKILL.md
Commit: 7520423

Reviewed: ~10 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.