mcpField
C
conductor-manage

conductor-manage

github.com/sickn33Agent workflows48.7k326 installsUpdated today
Repository

About conductor-manage

conductor-manage is an agent skill for managing Conductor track lifecycles in initialized repositories. It covers status changes and cleanup, with safeguards for metadata, staged work, and destructive operations.

Key features

  1. 01Archive, restore, rename, and delete tracks
  2. 02List track status
  3. 03Clean orphaned artifacts
  4. 04Preserve metadata and staged work
  5. 05Confirm destructive actions

Use cases

  1. 01Archive or restore a completed track
  2. 02Rename a track while preserving metadata
  3. 03Review track status across lifecycle states
  4. 04Remove orphaned artifacts after confirmation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill conductor-manage

After installing, type/conductor-managein Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

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.

Comments

Markdown supported