conductor-manage
Manage track lifecycle: archive, restore, delete, rename, and cleanup
45
32%
Does it follow best practices?
Impact
Pending
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 specific concrete actions (archive, restore, delete, rename, cleanup) which is a strength. However, it suffers from ambiguity around what 'track' means and completely lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill over others. Adding domain context and explicit trigger conditions would significantly improve its utility.
Suggestions
Add a 'Use when...' clause specifying trigger conditions, 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, music track, project track) to reduce ambiguity and conflict risk with other skills.
Include natural user-facing synonyms like 'remove track', 'bring back track', 'organize 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 tied to a specific domain (track lifecycle management). | 3 / 3 |
Completeness | Describes what the skill does (manage track lifecycle with specific actions) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when...' caps completeness at 2, and the ambiguity of 'track' further weakens it. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'archive', 'restore', 'delete', 'rename', and 'cleanup' which users might naturally say, but lacks context about what kind of 'track' (audio track? project track?) and misses common variations or synonyms users might use (e.g., 'remove', 'undo delete', 'organize tracks'). | 2 / 3 |
Distinctiveness Conflict Risk | The term 'track' is ambiguous — it could refer to audio tracks, project tracks, issue tracking, etc. While the specific actions (archive, restore, delete, rename, cleanup) help narrow the scope somewhat, the lack of domain context creates potential overlap with other management-related skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
22%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 stub that delegates all meaningful content to an external playbook. While it correctly identifies scope and references a detailed resource, the SKILL.md body itself provides no concrete, executable guidance for any of the five operations it claims to cover. The lack of any workflow steps, commands, or examples makes it nearly unusable without the external file.
Suggestions
Add at least a brief concrete workflow for each operation (archive, restore, delete, rename, cleanup) with specific commands or file paths, even if abbreviated, so the skill is actionable without opening the playbook.
Include explicit validation/verification steps for destructive operations (delete, cleanup), such as checking backup existence or confirming track state before proceeding.
Provide a concrete example of what the `conductor/` directory structure looks like and what `tracks.md` entries contain, so Claude can verify state before acting.
Remove generic boilerplate sections ('Do not use this skill when Conductor is not initialized', 'Limitations' with generic disclaimers) that don't add actionable information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably concise but includes some boilerplate sections ('Do not use this skill when', 'Limitations') that are generic and don't add much value. The actual instructions are thin, which is efficient but borders on lacking substance. | 2 / 3 |
Actionability | No concrete commands, code examples, or specific steps are provided. Instructions are vague directives like 'Verify conductor/ structure' and 'Determine the operation mode' without showing how. The real content is deferred entirely to an external playbook. | 1 / 3 |
Workflow Clarity | There is no clear sequence of steps for any of the operations (archive, restore, delete, rename, cleanup). The instructions are bullet points of general guidance with no validation checkpoints, and destructive operations like delete lack explicit feedback loops beyond 'confirm before applying'. | 1 / 3 |
Progressive Disclosure | There is a reference to `resources/implementation-playbook.md` for detailed workflows, which is appropriate progressive disclosure. However, the SKILL.md itself provides almost no actionable overview content—it's essentially an empty shell pointing elsewhere, making the top-level document too thin to be useful on its own. | 2 / 3 |
Total | 6 / 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
93c57b2
- 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.