conductor-manage – Other skill for AI agents
Manage track lifecycle: archive, restore, delete, rename, and cleanup
Install the conductor-manage skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/conductor-manage-4ada0.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /conductor-manage – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/conductor-manage-4ada0.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $conductor-manage – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/conductor-manage-4ada0.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /conductor-manage – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/conductor-manage-4ada0.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /conductor-manage – then describe the task you want done.
SKILL.md content
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.mdand 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.mdfor 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.
Related skills
- conductor-new-track – Create a new track with specification and phased implementation plan
- conductor-status – Display project status, active tracks, and next actions
- conductor-validator – Validates Conductor project artifacts for completeness, consistency, and correctness…
- qiskit – Builds, simulates, transpiles, and executes quantum circuits with Qiskit and IBM Quantum…
- context-degradation – Language models exhibit predictable degradation patterns as context length increases…
- saml-sso-attack – Attack SAML SSO via XSW, signature strip, metadata extract.
- rdkit – Cheminformatics toolkit for fine-grained molecular control. SMILES/SDF parsing…
- context-fundamentals – Context is the complete state available to a language model at inference time. It…