conductor-manage

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

Quality

54%

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 ./.agent/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-sectioned and token-efficient with sensible safety checkpoints for destructive operations, but it provides only high-level direction with no executable detail, and its single reference to detailed content points at a file that does not exist under two inconsistent paths. The skill is structured as an overview of a playbook that is missing from the bundle.

Suggestions

Fix the broken reference: ship the implementation playbook at one consistent path and reference it once, removing the conflicting `resources/` vs `./sub-skills/` duplication and the redundant Resources/Knowledge Modules sections.

Add concrete, executable guidance to the Instructions (e.g. the actual verification commands or the list of required `conductor/` files) so the skill is actionable even before opening the playbook.

Add a post-operation validation step (e.g. re-read `tracks.md` to confirm the track's state transitioned as expected) to close the feedback loop for destructive and batch operations.

Dimension	Reasoning	Score
Conciseness	The body is lean — short bullet sections with no explanations of concepts Claude already knows. It falls short of 5 due to redundancy: the intro sentence repeats the description, and the implementation playbook is referenced three times (Instructions, Resources, Knowledge Modules) with inconsistent paths (`resources/` vs `./sub-skills/`).	4 / 5
Actionability	Instructions are high-level hints ("Verify `conductor/` structure and required files", "Determine the operation mode from arguments or interactive prompts", "Update `tracks.md` and metadata consistently") with no concrete commands or examples — which required files, how to verify, what a consistent update looks like are all unspecified. It is not a 3 because there is no partially-executable guidance; all executable detail is deferred to a playbook that is not present in the bundle.	2 / 5
Workflow Clarity	A sequence exists (verify structure → determine mode → confirm destructive actions → update metadata) and destructive-operation checkpoints are present ("Confirm destructive actions (delete/cleanup) before applying", "Backup track data before delete operations"). However, this destructive/batch skill has no post-operation validation or feedback loop (e.g. verify the track state or `tracks.md` after the change), which caps workflow clarity at 3 per the judging guidelines.	3 / 5
Progressive Disclosure	The section structure is reasonable, but the referenced detail file does not exist in the bundle — neither `resources/implementation-playbook.md` nor `./sub-skills/implementation-playbook.md` is present, and the two conflicting paths plus a duplicated Resources/Knowledge-Modules listing make navigation unreliable. Scoring against the actual (empty) bundle structure, the one-level-deep reference is broken, so the skill cannot actually reach its detailed content.	2 / 5
	Total	11 / 20 Passed

Description

62%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 concise and concrete, listing five specific lifecycle operations in third person. Its main weaknesses are the missing 'Use when...' trigger clause and the absence of the 'Conductor' product name, which limit discoverability and distinctiveness.

Suggestions

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

Include the word 'Conductor' in the description so it is distinguishable from generic track/file management skills and triggers correctly.

Mention the 'list' operation to close the coverage gap against the skill's actual modes (e.g. 'list track status').

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions — "archive, restore, delete, rename, and cleanup" — naming the domain (track lifecycle) with mostly comprehensive coverage. It is not a 5 because the 'list' mode (present in the skill's argument-hint) is omitted, leaving a minor gap in coverage.	4 / 5
Completeness	The 'what' is clear ("Manage track lifecycle: archive, restore, delete, rename, and cleanup"), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' half is concrete and specific rather than vague.	3 / 5
Trigger Term Quality	Natural operation keywords users would actually say are present: "archive", "restore", "delete", "rename", "cleanup", "track". Not a 5 because common synonyms (e.g. "unarchive", "remove", "purge") and the product name "Conductor" itself are missing, so a few natural terms a user might say would not match.	4 / 5
Distinctiveness Conflict Risk	"Manage track lifecycle" is somewhat specific through its operation verbs, but "track" is generic without the "Conductor" qualifier, so it could overlap with other track/file lifecycle management skills. Not a 4 because no product-specific trigger distinguishes it from similar skills.	3 / 5
	Total	14 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
Path: .agent/skills/conductor-manage/SKILL.md
Commit: c4a059b

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