conductor-manage

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

Quality

66%

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

65%

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

The body is concise and well-organized with sensible safety guidance, but it relies on vague procedural instructions and points to a referenced playbook file that is missing from the bundle, weakening actionability and progressive disclosure.

Suggestions

Make the Instructions a numbered workflow with an explicit validate -> fix -> retry loop around destructive delete/cleanup operations.

Add concrete verification details, e.g. what 'conductor/ structure and required files' to check before proceeding.

Either add the missing 'resources/implementation-playbook.md' bundle file or remove the dangling reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with no concept padding or explanation Claude already knows; every section earns its place, matching the lean-and-efficient anchor.	3 / 3
Actionability	It names concrete files and operations ('Verify conductor/ structure', 'Update tracks.md', 'open resources/implementation-playbook.md') but gives no specifics on what to check or how, fitting the incomplete-guidance anchor for score 2 rather than fully executable instruction.	2 / 3
Workflow Clarity	Steps appear as an unordered bullet list with a confirm-before-destructive checkpoint, but there is no explicit sequence or validate-fix-retry feedback loop for the destructive delete/cleanup operations, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	Sections are clearly organized and the playbook reference is well-signaled, but the referenced 'resources/implementation-playbook.md' does not exist as a bundle file, so navigation is undermined and it cannot reach the clear one-level-deep reference anchor.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 well-scoped to a distinct niche, naming five concrete track operations. Its main weakness is the absence of an explicit 'Use when' trigger clause, which limits completeness and trigger-term quality.

Suggestions

Append a 'Use when managing Conductor tracks (archiving, restoring, deleting, renaming, or cleaning up orphaned artifacts)' clause to make the trigger explicit.

Add natural noun variations users might say (e.g. 'tracks', 'archived tracks', 'orphaned artifacts') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description enumerates five concrete actions — 'archive, restore, delete, rename, and cleanup' — matching the anchor for listing multiple specific concrete actions, not vague abstractions like 'Helps with documents'.	3 / 3
Completeness	It clearly answers 'what' (manage track lifecycle with five operations) but lacks any explicit 'when'/'Use when' trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It lists natural action verbs a user might say (archive/restore/delete/rename/cleanup) but offers no noun variations or 'Use when' phrasing, leaving common variations missing per the anchor for score 2.	2 / 3
Distinctiveness Conflict Risk	Tied to a clear niche — Conductor 'track lifecycle' with distinct operations — making it unlikely to trigger for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	10 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/conductor-manage/SKILL.md
Commit: e63f7dd

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