What problem does it solve? Setting up oh-my-codex (OMX) involves many moving parts: choosing an install scope, picking legacy versus plugin skill delivery, merging AGENTS.md content safely, and wiring hooks and config.toml entries. This Skill guides the AI through the current omx setup CLI behavior so installations and refreshes are consistent and non-destructive. ## Core Features & Use Cases - Scoped installation: Installs OMX into user-level (~/.codex, ~/.omx/agents) or project-level (./.codex, ./.omx/agents) directories with persisted scope in ./.omx/setup-scope.json. - Legacy vs plugin delivery: Selects legacy file installation or Codex plugin-based skill delivery, archiving stale prompts/skills and refreshing native agent TOMLs for agent_type routing. - Safe AGENTS.md handling: Uses --merge-agents markers and overwrite guards so existing project guidance is preserved during setup reruns. - Use Case: After pulling a repo that uses OMX, run setup with --force --verbose, then verify with omx doctor that prompts, skills, AGENTS.md, and config are correctly installed before starting Codex. ## Quick Start Ask the assistant to run omx setup with force and verbose flags for this project and then verify the installation with omx doctor.