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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

The body is well-organized, concise, and uses clean one-level-deep progressive disclosure to details.md. Its weaknesses are actionability and workflow clarity, since concrete executable guidance and the sequenced lifecycle workflow with validation checkpoints are not surfaced in SKILL.md itself.

Suggestions

Add a short, concrete worked example in the body (e.g. a minimal spec.md or plan.md snippet, or the track ID format) to lift actionability from descriptive to copy-paste-ready.

Surface a brief version of the track lifecycle sequence (creation -> implementation -> completion) with its key validation checkpoint in SKILL.md, leaving full detail in details.md, so the multi-step workflow is clear without following the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and token-efficient with no padding and no explaining of concepts Claude already knows; every section earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.	3 / 3
Actionability	Best practices give some concrete numeric guidance (e.g. '3-5 tasks maximum', '1-5 days of work') but provide no executable commands, code, or copy-paste-ready examples, fitting 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	The multi-step track lifecycle (creation -> implementation -> completion) and its validation checkpoints live in details.md rather than the body, so the SKILL.md body itself lacks a sequenced workflow with explicit checkpoints, fitting 'steps listed but validation gaps'.	2 / 3
Progressive Disclosure	SKILL.md is a concise overview with a single, clearly signaled one-level-deep reference to references/details.md (verified to exist, with no further nested .md references), matching 'clear overview with well-signaled one-level-deep references'.	3 / 3
	Total	10 / 12 Passed

Description

85%

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 is explicit, concise, and clearly answers both what the skill does and when to use it, with a distinct Conductor-tracks niche. Its main weakness is trigger-term naturalness, leaning on product-specific jargon rather than the plain phrases a user would naturally say.

Suggestions

Add plain-language trigger terms a user would naturally say (e.g. 'create a track', 'track management', 'plan a feature') alongside the Conductor-specific jargon to improve trigger_term_quality.

Consider naming the concrete track artifacts users mention (e.g. 'track registry', 'track status markers') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("creating, managing, or working with" tracks, "track lifecycle operations") and names specific artifacts (spec.md, plan.md), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (creating/managing/working with tracks, lifecycle operations) and when via the "Use this skill when ..." trigger clause, matching the 'clearly answers both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	Relevant terms appear ("Conductor tracks", "features, bugs, and refactors", "spec.md", "plan.md") but "Conductor tracks" is product-specific jargon and common natural variations a user would say are only partially covered, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	Tied to a distinct Conductor-tracks niche with triggers (spec.md, plan.md, track lifecycle) unlikely to fire for unrelated skills, matching 'clear niche with distinct triggers; unlikely to conflict'.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: wshobson/agents
Commit: 5cc2549

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