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.
Overall
score
78%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 97%
↑ 2.42xAgent success when using this skill
Validation for skill structure
Discovery
75%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 has good structure with an explicit 'Use when' clause and clear domain focus on Conductor tracks. However, it could be stronger by listing more specific concrete actions and including additional natural trigger terms users might use when requesting track-related work.
Suggestions
Add specific concrete actions like 'create spec files, generate implementation plans, initialize new tracks, update track status'
Include more natural trigger terms users might say such as 'new feature', 'start working on', 'planning document', 'track status'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Conductor tracks) and mentions some actions ('creating, managing, or working with') and artifacts (spec.md, plan.md, track lifecycle operations), but doesn't list specific concrete actions like 'create spec files', 'update plans', or 'close tracks'. | 2 / 3 |
Completeness | Explicitly answers both what ('creating, managing, or working with Conductor tracks', 'spec.md, plan.md, and track lifecycle operations') and when ('Use this skill when...') with clear trigger guidance at the start. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Conductor tracks', 'spec.md', 'plan.md', 'features', 'bugs', 'refactors', but missing common variations users might say like 'new feature', 'start a track', 'planning', or 'specification'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on 'Conductor tracks' with specific file types (spec.md, plan.md) that are unlikely to conflict with other skills; the domain-specific terminology creates distinct triggers. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive and actionable skill for track management with excellent workflow clarity and concrete templates. The main weaknesses are verbosity (some conceptual explanations could be trimmed) and the monolithic structure that could benefit from splitting detailed templates into separate reference files.
Suggestions
Move the detailed spec.md, plan.md, and metadata.json templates to separate reference files (e.g., SPEC_TEMPLATE.md, PLAN_TEMPLATE.md) and link to them from the main skill
Trim the 'Track Concept' section - Claude understands what a work unit is; focus on the specific conventions rather than explaining the concept
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundant explanations (e.g., explaining what a track 'is' conceptually when the structure already makes it clear). The extensive template examples and checklists add value but could be more condensed. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready templates for spec.md, plan.md, metadata.json, and tracks.md. Status markers, track ID formats, and phase patterns are all specific and executable. | 3 / 3 |
Workflow Clarity | Clear lifecycle stages (Creation → Implementation → Completion) with explicit numbered steps. Includes verification checkpoints after phases, checkpoint approval gates, and specific operations for reverting tracks. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one monolithic file. The extensive templates (spec.md, plan.md, metadata.json) could be split into separate reference files with links from the main skill. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
69%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (594 lines); consider splitting into references/ and linking | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 11 / 16 Passed | |
- Reviewed
Table of Contents
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.