conductor-manage

Manage track lifecycle: archive, restore, delete, rename, and cleanup

Install with Tessl CLI

npx tessl i github:sickn33/antigravity-awesome-skills --skill conductor-manage

What are skills?

2.23x

Quality

42%

Does it follow best practices?

Impact

96%

2.23x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/conductor-manage/SKILL.md

SKILL.md

Review

Evals

Discovery

35%

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 lists specific actions clearly but suffers from critical ambiguity around what 'track' means in this context. The complete absence of a 'Use when...' clause and the generic term 'track' make it difficult for Claude to know when to select this skill over others, creating high conflict risk with unrelated skills.

Suggestions

Clarify what 'track' refers to (e.g., 'audio track', 'project track', 'git branch') to establish clear domain context

Add a 'Use when...' clause with explicit trigger terms, e.g., 'Use when the user wants to manage, archive, or clean up [specific type of] tracks'

Include natural keywords users would say when needing this functionality, such as file extensions or domain-specific terminology

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.	1 / 3
Trigger Term Quality	Contains relevant keywords like 'archive', 'restore', 'delete', 'rename', 'cleanup', and 'track', but 'track' is ambiguous (could be music track, project track, etc.) and missing common variations users might say.	2 / 3
Distinctiveness Conflict Risk	'Track' is highly ambiguous and could conflict with music/audio skills, project management skills, or version control skills. Without context, it's unclear what domain this applies to.	1 / 3
	Total	7 / 12 Passed

Implementation

50%

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

The skill is concise but sacrifices actionability by deferring nearly all concrete guidance to an external resource. It reads more like a table of contents than a functional skill, providing no executable commands, code examples, or specific workflows that Claude could immediately act upon.

Suggestions

Add concrete command examples or code snippets for each operation mode (archive, restore, delete, rename, cleanup) directly in the skill

Include a specific workflow with validation steps for destructive operations (e.g., 'Run X to verify, then Y to backup, then Z to delete')

Provide at least one complete example showing input and expected output for a common operation like archiving a track

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding unnecessary explanations. Every section serves a clear purpose without padding or explaining concepts Claude would already understand.	3 / 3
Actionability	The skill provides only vague, abstract guidance with no concrete commands, code examples, or specific steps. Instructions like 'Verify conductor/ structure' and 'Determine the operation mode' lack any executable detail.	1 / 3
Workflow Clarity	Steps are listed but lack specific validation checkpoints and concrete sequences. The instruction to 'Confirm destructive actions' is mentioned but no explicit feedback loop or verification process is defined for risky operations like delete/cleanup.	2 / 3
Progressive Disclosure	References to external resources exist (implementation-playbook.md), but the skill itself is too sparse - it defers almost all actionable content to the external file rather than providing a useful quick-start overview.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 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

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