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

51%

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

Quality

Content

32%Weight 40%Scale 1-5

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

The skill body is a lean, well-structured overview that points to a single detail file, but it provides almost no actionable or sequenced guidance for the track lifecycle, relying on generic boilerplate. The referenced resources/implementation-playbook.md is not present in the bundle, weakening the progressive disclosure it depends on.

Suggestions

Replace generic Instructions ('Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') with concrete, executable steps for track operations such as creating a track, writing spec.md, and updating tracks.md.

Add an explicit sequenced workflow with validation checkpoints for the track lifecycle (e.g., create -> spec -> plan -> implement -> mark complete), since lifecycle changes are effectively batch/state operations that need verification steps.

Either bundle the referenced resources/implementation-playbook.md or remove the reference, so the progressive-disclosure pointer resolves to a real file.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concept explanations Claude already knows, but generic filler lines such as 'Apply relevant best practices and validate outcomes' and 'Provide actionable steps and verification' add no information, leaving it mostly efficient with some unnecessary boilerplate.	3 / 5
Actionability	The Instructions offer only abstract direction ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') with no concrete code, commands, or specific steps for track operations, matching the anchor for entirely vague guidance that describes rather than instructs.	1 / 5
Workflow Clarity	A multi-step domain (create, spec, plan, implement, complete) is reduced to generic bullet hints with no real sequence and no validation checkpoints for lifecycle/registry operations, matching the anchor for a rough, poorly defined sequence with validation absent.	2 / 5
Progressive Disclosure	The short overview cleanly points to a single one-level-deep reference (resources/implementation-playbook.md) signaled in both Instructions and Resources, giving good structure; it is not a 5 because the referenced file is not actually bundled and the navigation could be tighter.	4 / 5
	Total	10 / 20 Passed

Description

70%Weight 40%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 clearly identifies a specific niche (Conductor tracks) with an explicit 'Use this skill when' clause and concrete artifact references, giving it solid trigger coverage and distinctiveness. Weaknesses are generic action verbs and slightly incomplete trigger synonyms, keeping it just below the top anchors.

Dimension	Reasoning	Score
Specificity	Names the Conductor tracks domain plus concrete artifacts (spec.md, plan.md, track lifecycle), but the verbs 'creating, managing, or working with' are generic rather than distinct concrete capabilities, matching the anchor that lists domain plus 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Provides both a 'what' (creating/managing Conductor tracks as logical work units) and an explicit 'when' ('Use this skill when...'), with the 'when' reasonably explicit via the enumerated file types and lifecycle operations; not quite at the fully concrete trigger-phrase anchor of 5.	4 / 5
Trigger Term Quality	Includes natural domain terms a Conductor user would say ('Conductor tracks', 'spec.md', 'plan.md', 'track lifecycle') with an explicit 'Use this skill when' trigger, though a few common synonyms or variations are missing.	4 / 5
Distinctiveness Conflict Risk	The 'Conductor tracks' niche with spec.md/plan.md/lifecycle triggers is mostly distinct with minimal conflict risk, though the broad 'creating, managing, or working with' phrasing leaves minor overlap with adjacent project-management skills.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/track-management/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.