conductor-manage

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

Quality

70%

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

68%Weight 40%Scale 1-5

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

The skill body is lean and well-organized but stays at a high directive level, offloading executable detail to a referenced playbook that does not exist in the bundle. Destructive operations lack an explicit validation feedback loop.

Suggestions

Add explicit validation/verification checkpoints (e.g., verify tracks.md and metadata are consistent after each mutating operation) to lift workflow clarity above the destructive-operation cap.

Include a few concrete, executable commands or step-level details inline so the skill is actionable without the external playbook.

Create the referenced resources/implementation-playbook.md (or correct the path) so the one-level-deep reference resolves to a real file.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with no over-explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	Guidance names concrete files and operations ('Verify conductor/ structure', 'Update tracks.md') but provides no executable commands or specific step-level detail, relying on an external playbook for the executable parts.	3 / 5
Workflow Clarity	Steps are present and destructive actions are flagged, but there is no explicit validate-then-proceed feedback loop or verification checkpoint after delete/cleanup, which caps destructive-operation workflow clarity at 3.	3 / 5
Progressive Disclosure	Good section structure with a one-level-deep reference to resources/implementation-playbook.md, but that referenced file is not present in the bundle, leaving a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

71%Weight 40%Scale 1-5

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 concise and specific about capabilities but omits any explicit 'Use when' trigger guidance, which caps its completeness. Trigger terms are natural but lack synonyms or variations.

Suggestions

Add an explicit 'Use when...' clause listing the natural trigger phrases (e.g., 'Use when archiving, restoring, renaming, or deleting Conductor tracks').

Include common synonyms or variations of trigger terms so users are more likely to match the skill with their phrasing.

Tie the capabilities more tightly to the Conductor-specific context to reduce overlap with generic file-management skills.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions ('archive, restore, delete, rename, and cleanup') giving comprehensive coverage of the track lifecycle, matching the multiple-specific-concrete-actions anchor.	5 / 5
Completeness	It clearly answers 'what' but contains no 'Use when...' trigger clause; per the guideline a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Natural verbs like 'archive', 'restore', 'delete', and 'rename' are present, but it lacks common synonyms, file extensions, or phrasings users might say, so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	'Manage track lifecycle' is a fairly distinct niche, but generic verbs like archive/delete/cleanup carry minor overlap risk with general file-management skills, keeping it just below the clear-niche anchor.	4 / 5
	Total	16 / 20 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: 1f67c44

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