conductor-manage

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

Quality

50%

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

46%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 well-organized and token-efficient with sensible use-when/do-not-use-when scoping, but it operates entirely at the policy level: no concrete commands or per-operation steps, and the single reference that should carry the executable detail points to a file missing from the bundle. For a destructive-operations skill, the absence of post-operation validation compounds the fragility.

Suggestions

Create the missing `resources/implementation-playbook.md` (or remove the references to it) so the bundle matches what SKILL.md promises — currently the reference is dangling.

Inline at least the core concrete mechanics for each mode (e.g., the exact `conductor/` files to verify, how `tracks.md` entries are added/removed for archive vs. delete) rather than deferring all detail to the absent playbook.

Add post-operation validation steps — e.g., re-read `tracks.md` after a delete/cleanup to confirm the track entry and artifacts are gone — to satisfy the feedback-loop requirement for destructive operations.

Dimension	Reasoning	Score
Conciseness	The body is a lean set of short bullets with no explanations of concepts Claude already knows, fitting the 'efficient; minor instances of over-explanation' anchor; it misses 5 because the intro sentence repeats the frontmatter description verbatim and the Limitations section carries generic boilerplate ('Do not treat the output as a substitute for...') that could be trimmed.	4 / 5
Actionability	Instructions are high-level directives — 'Verify `conductor/` structure and required files', 'Update `tracks.md` and metadata consistently' — with no commands, examples, or specific steps, and every operational detail is deferred to `resources/implementation-playbook.md`, which does not exist in the bundle; this matches 'minimal concrete guidance; high-level hints but missing the specific steps to execute', and cannot be 3 because no executable detail survives the broken reference.	2 / 5
Workflow Clarity	The skill covers destructive operations (delete, cleanup) and includes pre-flight checks ('Confirm destructive actions (delete/cleanup) before applying', 'Backup track data before delete operations'), so validation is not absent (ruling out 2), but there is no post-operation verification or feedback loop (e.g., confirming `tracks.md` reflects the change), capping workflow clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Although the reference is clearly signaled in both Instructions and Resources and the body is well-sectioned, `resources/implementation-playbook.md` does not exist anywhere in the bundle, so the promised one-level-deep reference is broken and no detailed material is actually reachable; scored against the actual (empty) bundle structure this leaves effectively minimal working progressive disclosure, fitting anchor 2 rather than 3 where references at least resolve.	2 / 5
	Total	11 / 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 lifecycle operations but reads as a bare capability list: it never mentions Conductor, includes no 'Use when...' trigger clause, and leaves 'track' ambiguous enough to risk mis-triggering. Adding a domain qualifier and an explicit trigger sentence would move it from adequate to strong.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks to archive, restore, delete, rename, or clean up Conductor tracks.'

Name the tool: replace the generic 'track lifecycle' with 'Conductor track lifecycle' so the description is distinctive and matches what users will actually say.

Give the actions objects (e.g., 'archive completed Conductor tracks') so each capability is concrete rather than a bare verb.

Dimension	Reasoning	Score
Specificity	"archive, restore, delete, rename, and cleanup" lists five concrete actions, matching the 'several specific actions; minor gaps' anchor; it falls short of 5 because the actions lack objects and never name the target tool (e.g., 'Conductor tracks'), unlike the level-5 examples such as 'Extract text and tables from PDF files'.	4 / 5
Completeness	It clearly answers 'what' ("Manage track lifecycle: archive, restore, delete, rename, and cleanup") but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines; it is above 2 because the 'what' is concrete, and below 4 because 'when' is entirely absent rather than merely implicit.	3 / 5
Trigger Term Quality	The action verbs (archive, restore, delete, rename, cleanup) are natural trigger terms, but the description omits 'Conductor' — the single keyword users would most naturally say — plus any synonyms or variations, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	"track lifecycle" is somewhat specific but 'track' is a generic word (music tracks, git tracked files, task tracking) and the missing 'Conductor' qualifier leaves overlap risk with other skills, matching the 'somewhat specific but could still overlap' anchor; it does not reach 4 because no distinct domain term narrows the triggers.	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: sickn33/agentic-awesome-skills
Path: skills/conductor-manage/SKILL.md
Commit: 7b534bc

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