mcpbeat

Conductor Manage

dokhacgiakhoa/conductor-manage

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

8k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill conductor-manage

What comes with it

28 721 bytes besides the instruction
sub-skills/implementation-playbook.md

The instruction itself

8 sections, as written by the author

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

  • 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.

🧠 Knowledge Modules (Fractal Skills)

1. implementation-playbook

How to use it

Copy the folder

Take dokhacgiakhoa/conductor-manage from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.