conductor-manage

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

2.23x

Quality

62%

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

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

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 body is admirably concise and well-sectioned but provides only high-level, non-executable instructions and relies on a referenced playbook file that is not present in the bundle. As a destructive-operation skill it also lacks explicit post-operation verification steps.

Suggestions

Replace abstract directives with concrete, executable steps or commands (e.g., the exact files/commands to verify the conductor/ structure and to update tracks.md) to raise actionability.

Add an explicit validation/verification step after destructive operations (e.g., confirm the track no longer appears in tracks.md and metadata is consistent) to enable a workflow_clarity score above 3.

Either create the referenced 'resources/implementation-playbook.md' or correct the path to an existing bundle file so the progressive-disclosure reference resolves.

Dimension	Reasoning	Score
Conciseness	The ~30-line body is lean, assumes Claude's competence, and contains no concept-explaining fluff or padding, matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	Guidance is high-level ('Verify conductor/ structure', 'Determine the operation mode', 'Update tracks.md') with no concrete commands, code, or executable steps, fitting 'minimal concrete guidance; missing the specific steps to execute'; not a 3 because even pseudocode/concrete details are absent.	2 / 5
Workflow Clarity	Steps are sequenced and include a confirm-before-destructive checkpoint, but this is a destructive/batch skill (delete, cleanup) lacking post-operation validation or a validate->fix->retry feedback loop, so the destructive-operation cap of 3 applies rather than 4.	3 / 5
Progressive Disclosure	Section structure is reasonable and points one level deep to a playbook, but the referenced 'resources/implementation-playbook.md' does not exist in the bundle (no references/scripts/assets/resources directories present), a broken navigation signal that prevents a 4.	3 / 5
	Total	13 / 20 Passed

Description

67%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 lists comprehensive concrete actions, but omits any explicit 'Use when...' trigger guidance, which caps its completeness and limits trigger-term quality. It is a solid, concise 'what' statement that would benefit from an explicit when-to-use clause.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases (e.g., 'Use when archiving, restoring, renaming, or deleting Conductor tracks, or cleaning up orphaned artifacts') to lift completeness above 3.

Tie distinctiveness to the 'Conductor' product name in the description itself to reduce overlap with generic track-management skills.

Include synonyms or natural phrasings users might say (e.g., 'clean up', 'remove', 'unarchive') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions (archive, restore, delete, rename, cleanup) tied to a named domain, matching the 'comprehensive coverage' anchor rather than the 'minor gaps' anchor at 4.	5 / 5
Completeness	Has a clear 'what' (manage track lifecycle + five actions) but no explicit 'Use when...' trigger clause, which the guidelines cap at 3; not a 4 because 'when' is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	Includes natural verbs users would say (archive, restore, delete, rename, cleanup) but lacks synonyms or file-extension style triggers, fitting 'good keyword coverage; a few natural terms missing' rather than the 3 (missing common variations) or 5 (comprehensive synonyms).	4 / 5
Distinctiveness Conflict Risk	The domain 'track lifecycle' with specific actions is somewhat specific, but 'track' alone is generic enough to overlap with issue/project-tracking skills; fits the 'somewhat specific but could still overlap' anchor.	3 / 5
	Total	15 / 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/skills/conductor-manage/SKILL.md
Commit: 57c135b

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