conductor-manage

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

2.23x

Quality

32%

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 ./skills/conductor-manage/SKILL.md

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

Quality

Content

22%Scale 1-3

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

This skill is essentially a stub that delegates all meaningful content to an external playbook. It lacks any concrete commands, executable examples, or clear workflows for the five operations it claims to cover. While it's concise and references an external resource, it provides insufficient actionable guidance on its own to be useful.

Suggestions

Add concrete command examples or at minimum a clear step-by-step workflow for each operation mode (archive, restore, delete, rename, cleanup) directly in the SKILL.md.

Include explicit validation/verification steps for destructive operations (delete, cleanup), such as checking backup existence before proceeding and verifying tracks.md consistency after changes.

Provide at least a summary table or quick-reference showing each operation with its key command/action, so the skill is useful without opening the playbook.

Dimension	Reasoning	Score
Conciseness	Reasonably concise but the 'Use this skill when' and 'Do not use this skill when' sections add moderate overhead with somewhat obvious guidance (e.g., 'Conductor is not initialized' or 'task is unrelated'). The core instructions are lean but could be tighter.	2 / 3
Actionability	No concrete commands, code, or executable examples are provided. Instructions are vague directives like 'Verify conductor/ structure' and 'Determine the operation mode' without specifying how. The skill essentially defers all actionable content to an external playbook.	1 / 3
Workflow Clarity	There is no clear sequence of steps for any of the operations (archive, restore, delete, rename, cleanup). Destructive operations like delete and cleanup mention confirmation but lack explicit validation checkpoints or feedback loops. The workflow is essentially 'see the playbook.'	1 / 3
Progressive Disclosure	There is a reference to `resources/implementation-playbook.md` for detailed workflows, which is appropriate one-level-deep disclosure. However, the SKILL.md itself provides almost no useful overview content—it's too thin to serve as a meaningful entry point, making the reference feel like a redirect rather than progressive disclosure.	2 / 3
	Total	6 / 12 Passed

Description

42%Scale 1-3

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 effectively lists specific concrete actions but suffers from ambiguity around the domain ('track' is undefined) and completely lacks explicit trigger guidance. Adding a 'Use when...' clause and clarifying what type of tracks are being managed would significantly improve skill selection accuracy.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user wants to archive, restore, delete, rename, or clean up tracks.'

Clarify what 'track' refers to (e.g., audio tracks, project tracks, music tracks) to reduce ambiguity and conflict risk with other skills.

Include natural user language variations such as 'remove track', 'undo archive', 'tidy up tracks' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: archive, restore, delete, rename, and cleanup. These are clear, actionable verbs tied to a specific domain (track lifecycle management).	3 / 3
Completeness	Describes what the skill does (manage track lifecycle with specific actions) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, but the 'when' is entirely absent, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'archive', 'restore', 'delete', 'rename', and 'cleanup' which users might naturally say, but lacks context about what kind of 'track' (audio track? project track?) and misses common variations or synonyms users might use.	2 / 3
Distinctiveness Conflict Risk	The term 'track' is ambiguous — it could refer to audio tracks, project tracks, issue tracking, etc. While the specific actions (archive, restore, delete, rename, cleanup) help narrow scope, the lack of domain context creates potential overlap with other management skills.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/conductor-manage/SKILL.md
Commit: 0159794

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