conductor-manage

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

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/conductor-manage/SKILL.md

Quality

Content

50%

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-structured and reasonably lean for an instruction-only skill, but its guidance defers most operational detail to a missing playbook, the workflow is unsequenced with no error-recovery loop, and the primary external reference is a broken path.

Suggestions

Provide the missing resources/implementation-playbook.md (or inline the key modes/steps) so the referenced detailed guidance is actually available.

Reorder the Instructions into a numbered sequence with explicit validation checkpoints and a validate-fix-retry loop around destructive delete/cleanup operations.

Replace vague directives like "Update tracks.md and metadata consistently" with concrete, specific steps the model can execute directly.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with clear sections, but the opening line restates the description and the Limitations section repeats scope already covered by the Use/Do-not-use sections, so it could be tightened.	2 / 3
Actionability	Concrete file paths (conductor/, tracks.md) give some specificity, but guidance like "Update tracks.md and metadata consistently" is vague and the actual operational detail is deferred entirely to the external playbook.	2 / 3
Workflow Clarity	Instructions are a bulleted list rather than a sequenced workflow, and destructive operations (delete/cleanup) lack an explicit validate-fix-retry feedback loop, which the rubric caps at 2.	2 / 3
Progressive Disclosure	Content is well-organized into signaled sections with a one-level-deep reference to the playbook, but the referenced resources/implementation-playbook.md file does not exist in the bundle, so navigation is broken.	2 / 3
	Total	8 / 12 Passed

Description

60%

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 specific and concrete about actions but lacks an explicit "Use when" trigger clause and the "Conductor" domain keyword, which together limit trigger quality, completeness, and distinctiveness.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke the skill, e.g. 'Use when managing Conductor tracks — archiving, restoring, deleting, renaming, or cleaning up orphaned artifacts.'

Include the "Conductor" keyword in the description to improve trigger-term coverage and reduce conflict with unrelated track-management skills.

Add natural user phrasings such as 'archive a track' or 'clean up orphaned tracks' to broaden trigger-term match coverage.

Dimension	Reasoning	Score
Specificity	The description enumerates five concrete actions ("archive, restore, delete, rename, and cleanup"), matching the level-3 anchor of listing multiple specific actions rather than vague language.	3 / 3
Completeness	It clearly answers "what" with concrete actions but provides no "Use when..." clause or equivalent explicit trigger guidance, which the rubric guidelines cap at 2.	2 / 3
Trigger Term Quality	The verbs (archive, restore, delete, rename, cleanup) are natural terms a user might say, but the description omits the "Conductor" keyword and common phrasings like "delete a track", so coverage of natural variations is incomplete.	2 / 3
Distinctiveness Conflict Risk	Without "Conductor" in the description, "track lifecycle" is ambiguous (could be music or project tracks) and the listed verbs are generic operations that could overlap with other management skills.	2 / 3
	Total	9 / 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: sickn33/antigravity-awesome-skills
Path: skills/conductor-manage/SKILL.md
Commit: a3068b7

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