conductor-manage

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

2.23x

Quality

61%

Does it follow best practices?

Impact

96%

2.23x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/conductor-manage/SKILL.md

The canonical home for this skill is conductor-manage in rmyndharis/antigravity-skills

Quality

Content

50%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 body is concise and sensibly sectioned (use/avoid, instructions, safety, resources), but it delegates virtually all executable detail to a playbook file that is absent from the bundle, leaving the instructions as high-level hints. Destructive operations also lack verification steps, capping workflow clarity.

Suggestions

Fix the dangling reference: `resources/implementation-playbook.md` is cited twice but does not exist in the bundle — either ship the file or inline the essential steps (commands, prompts, file formats) into SKILL.md.

Add concrete executable detail to Instructions, e.g. the exact `conductor/` files to verify, the `tracks.md` entry format to update, and example CLI invocations per operation mode.

Add post-operation validation steps for the destructive/batch flows (e.g. re-check track status after delete/cleanup and verify `tracks.md` consistency) so workflow clarity can exceed the destructive-operation cap.

Dimension	Reasoning	Score
Conciseness	The ~30-line body is lean with no explanations of concepts Claude already knows, but the intro sentence "Manage the complete track lifecycle including..." duplicates the frontmatter description and "The task is unrelated to Conductor track management" is vacuous, so minor trimming is possible.	4 / 5
Actionability	The Instructions are high-level hints ("Verify `conductor/` structure and required files", "Update `tracks.md` and metadata consistently") with no commands, file formats, or specific steps; all executable detail is deferred to `resources/implementation-playbook.md`, which is missing from the bundle, so the guidance cannot be executed as written.	2 / 5
Workflow Clarity	A rough sequence exists (verify structure, determine mode, confirm destructive actions, update metadata) and a confirm-destructive checkpoint is present, but the destructive and batch operations (delete, cleanup) have no post-operation verification step, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Sections are well organized and the reference is clearly signaled in both Instructions and Resources, but the sole detailed reference `resources/implementation-playbook.md` does not exist in the bundle, so the one-level-deep disclosure structure the body depends on is broken in practice.	3 / 5
	Total	12 / 20 Passed

Description

55%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 names five concrete operations, giving it decent specificity, but it omits any usage triggers and never mentions Conductor, leaving "track" ambiguous and reducing both completeness and distinctiveness. It reads as a terse capability list rather than a complete description with trigger phrases.

Suggestions

Add a "Use when..." clause with explicit triggers, e.g. "Use when the user asks to archive, restore, rename, or delete Conductor tracks or to clean up orphaned track artifacts."

Mention "Conductor" (and concrete artifacts like `tracks.md`) in the description so trigger matching works when users name the tool, and to distinguish it from audio-track or generic file-management skills.

Include common synonyms users would say — e.g. "backlog", "cleanup", "orphaned artifacts" — to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	"archive, restore, delete, rename, and cleanup" lists several specific actions with good coverage, but the actions all target the undefined abstraction "track lifecycle" without naming what a track is, leaving minor gaps versus the comprehensive anchor.	4 / 5
Completeness	The description has a clear "what" ("Manage track lifecycle: archive, restore, delete, rename, and cleanup") but contains no "Use when..." clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	The verbs "archive", "restore", "delete", and "rename" are natural user phrases, but the tool name "Conductor" and common variations (e.g. "tracks.md", "backlog", "cleanup orphaned tracks") are absent, matching the anchor for relevant keywords that miss common variations.	3 / 5
Distinctiveness Conflict Risk	"track lifecycle" is somewhat domain-specific, but the generic verbs (delete, rename, restore) and the missing "Conductor" qualifier mean it could overlap with audio-track editing or general file-management skills, matching the "somewhat specific but could still overlap" anchor.	3 / 5
	Total	13 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/conductor-manage/SKILL.md
Commit: 64adc55

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