conductor-manage — Claude Code skill: Conductor track lifecycle
conductor-manage — a skill that keeps Conductor tracks tidy: finished work gets archived, archived tracks come back, others are renamed or deleted, and leftover artifacts get swept.
MIT 1 installs ★ 50,109 updated 2026-10-29
npx skills add sickn33/agentic-awesome-skills --skill conductor-manage -a claude-codeWhat conductor-manage does
Tracks move between active, completed and archived states, with tracks.md kept in step with the metadata. Nothing is touched until the skill confirms conductor/ and the files it expects are there. Which operation to run comes from your arguments, or from a prompt if you gave none.
Deletes and cleanups are destructive, so the skill lists the exact paths involved and stops for your confirmation. Track status and metadata fields it does not recognise are carried over untouched. A multi-file step that fails halfway leaves the changes half-applied, because no rollback is assumed. Track data gets backed up before a delete, and archived tracks will not be dropped without an explicit go-ahead.
It applies where Conductor is already set up in the repo and you are allowed to change track files. Longer modes and prompts live in resources/implementation-playbook.md, which the skill opens once the job needs more than a couple of steps.
What it helps with
- archive a finished track without losing its metadata
- pull a track back out of the archive
- delete a track after taking a backup
- rename a track and keep
tracks.mdconsistent - sweep up artifacts orphaned by removed tracks
Example prompts for the agent
- Archive the
auth-refactortrack and updatetracks.md. - Show me the paths first, back up, then delete the completed tracks.
- List every track under
conductor/and flag orphaned artifacts.
How to install conductor-manage
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill conductor-manage -a claude-code2Manually: put the files in place
~/.claude/skills/conductor-manage/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/conductor-manage/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill conductor-manage -a codex2Manually: put the files in place
.agents/skills/conductor-manage/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill conductor-manage -a cursor2Manually: put the files in place
.cursor/skills/conductor-manage/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills skills/conductor-manage2Manually: put the files in place
.github/skills/conductor-manage/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill conductor-manage -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/conductor-manageManually: put the files in place
.devin/skills/conductor-manage/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill conductor-manage -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about conductor-manage
How do I install conductor-manage in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill conductor-manage -a claude-code. The skill lands at ~/.claude/skills/conductor-manage/SKILL.md.
What does conductor-manage do?
It handles the whole track lifecycle in Conductor: archiving, restoring, renaming, deleting, plus cleanup of artifacts whose track is gone. tracks.md and the metadata stay consistent with each change.
What does it need before it can run?
Conductor initialised in the repository and permission to modify track files. Deletes and cleanups wait for confirmation, and a backup is taken before anything is removed.
Source text
SKILL.md · MIT
--- name: conductor-manage description: "Manage track lifecycle: archive, restore, delete, rename, and cleanup" risk: critical source: community date_added: "2026-02-27" --- # Track Manager Manage the complete track lifecycle including archiving, restoring, deleting, renaming, and cleaning up orphaned artifacts. ## Use this skill when - Archiving, restoring, renaming, or deleting Conductor tracks - Listing track status or cleaning orphaned artifacts - Managing the track lifecycle across active, completed, and archived states ## Do not use this skill when - Conductor is not initialized in the repository - You lack permission to modify track metadata or files - The task is unrelated to Conductor track management ## Instructions - Detailed path/transaction safeguards in the playbook apply to every mutation. Preserve prior status and unknown metadata fields; restoration must not falsely complete an abandoned track. - Preview the exact affected paths and preserve unrelated staged work; do not use broad staging or assume a failed multi-file operation rolled back. - Verify `conductor/` structure and required files before proceeding. - Determine the operation mode from arguments or interactive prompts. - Confirm destructive actions (delete/cleanup) before applying. - Update `tracks.md` and metadata consistently. - If detailed steps are required, open `resources/implementation-playbook.md`. ## Safety - Backup track data before delete operations. - Avoid removing archived tracks without explicit approval. ## Resources - `resources/implementation-playbook.md` for detailed modes, prompts, and workflows. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
© sickn33 · MIT · sickn33/agentic-awesome-skills