conductor-manage

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

Quality

64%

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

57%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 commendably concise and safety-aware, but it offers little executable guidance and leans on a referenced playbook file that is not actually present in the bundle.

Suggestions

Add at least one concrete, executable example or command per operation mode (archive/restore/delete/rename/cleanup) so Claude can act without opening the playbook.

Restructure the Instructions as a numbered, sequenced workflow with explicit validation checkpoints and a verify-fix-retry feedback loop for destructive operations.

Either provide the referenced resources/implementation-playbook.md bundle file or remove the dangling reference so progressive-disclosure navigation is intact.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with no padding or over-explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	Guidance is high-level directives ('Verify conductor/ structure', 'Determine the operation mode') with no concrete commands, code, or executable steps, deferring all specifics to an external file.	2 / 5
Workflow Clarity	Validation awareness exists (verify structure, confirm destructive actions, backup), but steps are an unordered checklist rather than a sequenced workflow with explicit checkpoints or a verify-fix-retry feedback loop.	3 / 5
Progressive Disclosure	Sections are well-organized and a one-level reference to resources/implementation-playbook.md is signaled, but no resources/ bundle directory exists, so the referenced file is missing and navigation breaks.	3 / 5
	Total	13 / 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 specific and action-dense with a clear niche, but it omits an explicit 'when to use' trigger clause and lacks synonym/variation coverage in its trigger terms.

Suggestions

Add an explicit 'Use when ...' clause naming concrete trigger phrases (e.g., archiving, restoring, or deleting Conductor tracks) to raise completeness.

Include synonyms and common variations of the trigger terms (e.g., 'unarchive', 'purge', 'list tracks') to broaden natural-language matching.

Reference Conductor explicitly in the description text itself, not only in the skill name, to strengthen distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain ('track lifecycle') and lists five concrete actions — archive, restore, delete, rename, and cleanup — matching the comprehensive-coverage anchor.	5 / 5
Completeness	The 'what' is clear, but there is no explicit 'Use when...' trigger clause, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural action verbs (archive, restore, delete, rename, cleanup) give good keyword coverage, but synonyms, common variations, and file/identifier extensions are absent.	4 / 5
Distinctiveness Conflict Risk	The track-lifecycle operation cluster (archive/restore/delete/rename/cleanup) is a fairly distinct niche with only minor overlap risk against related management skills.	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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

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

Reviewed: 1 day 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.