What problem does it solve? Copying orchestrator template files (skills, prompts, agents, chains) into other projects by hand is error-prone: customized files get overwritten, there is no record of what changed, and mistakes cannot be undone. This Skill automates the deployment with state tracking, conflict resolution, and backups. ## Core Features & Use Cases - Selectable bundles: Deploy named selections such as grok, chains, loops, scripts, claude, copilot, or github via the --selections flag, with a safe default set. - Conflict policy: When a target file differs from the template, choose skip, overwrite, merge (writes a .merged file with conflict markers), or diff, interactively or non-interactively. - Backup and rollback: Every deploy snapshots changed files to .grok/deploy-backups/<timestamp>/ and can restore them with --rollback, including a specific backup id. - Use Case: You maintain an orchestrator template repo and want to push the latest Grok skills plus Claude and Copilot mirrors into the lightstone project. You dry-run first, deploy with --selections grok,claude,copilot, then roll back if a customized script was affected. ## Quick Start Ask the agent to deploy the orchestrator template to your target project with a dry run first, for example: run orchestrator-deploy against /path/to/target with --dry-run and selections grok,claude,copilot.
