conductor-manage
Manage track lifecycle: archive, restore, delete, rename, and cleanup
33
28%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/conductor-manage/SKILL.mdQuality
Discovery
42%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 effectively lists concrete actions but suffers from ambiguity around the domain term 'track' and completely lacks explicit trigger guidance ('Use when...'). Without knowing what kind of 'track' is being managed and when this skill should be selected, Claude would struggle to reliably choose it from a large skill set.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user wants to archive, restore, delete, rename, or clean up tracks in their project.'
Clarify what 'track' refers to (e.g., audio track, project track, Linear track) to reduce ambiguity and improve distinctiveness.
Include natural user phrasing variations such as 'remove track', 'rename track', 'clean up old tracks' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: archive, restore, delete, rename, and cleanup. These are clear, actionable verbs describing what the skill does. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also somewhat unclear due to the ambiguous 'track' term, so this falls to 1. | 1 / 3 |
Trigger Term Quality | Includes relevant action keywords like 'archive', 'restore', 'delete', 'rename', and 'cleanup', but the domain term 'track' is ambiguous (music track? project track? issue track?) and lacks natural user phrasing variations or file type references. | 2 / 3 |
Distinctiveness Conflict Risk | The specific action verbs (archive, restore, delete, rename, cleanup) help distinguish it, but 'track' is ambiguous and 'lifecycle' is generic. Could overlap with general file management or project management skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a thin wrapper that defers nearly all actionable content to a referenced resource file that doesn't exist in the bundle. The body lacks concrete commands, code examples, file format specifications, or step-by-step workflows for any of the five operations it claims to support. It reads more like a table of contents or abstract than an executable skill.
Suggestions
Add concrete, executable steps for at least the core operations (archive, restore, delete) including specific commands, file paths, and expected file format changes to tracks.md.
Include validation checkpoints and feedback loops for destructive operations (delete, cleanup), e.g., 'verify backup exists before proceeding' with specific checks.
Either provide the referenced `resources/implementation-playbook.md` as a bundle file or inline the essential workflow details directly in the SKILL.md body.
Remove generic boilerplate in the Limitations section and replace with skill-specific constraints (e.g., what happens if tracks.md is malformed, what states are valid transitions).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is relatively brief but includes some unnecessary sections like 'Use this skill when' / 'Do not use this skill when' that are somewhat redundant with the description. The 'Limitations' section contains generic boilerplate that doesn't add value specific to this skill. | 2 / 3 |
Actionability | The instructions are vague and abstract — 'Verify conductor/ structure,' 'Determine the operation mode,' 'Update tracks.md and metadata consistently' — without any concrete commands, code examples, file formats, or specific steps. It describes what to do rather than showing how to do it, and defers all real detail to a resource file that isn't provided. | 1 / 3 |
Workflow Clarity | There is no clear sequencing of steps for any of the multiple operations (archive, restore, delete, rename, cleanup). The instructions are a loose list of considerations rather than a workflow. Destructive operations like delete mention 'confirm' and 'backup' but provide no validation checkpoints or feedback loops. | 1 / 3 |
Progressive Disclosure | The skill references `resources/implementation-playbook.md` for all substantive detail, but no bundle files are provided, meaning the reference is unverifiable and the skill body itself contains almost no actionable content. The SKILL.md is essentially an empty shell pointing to a missing file. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%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
- sickn33/antigravity-awesome-skills
- Commit
f5dc9e3
- 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.