omx-setup

Installs and configures oh-my-codex across user or project scope directories.

Updated Feb 1, 2024
One-click install
npx skills add https://github.com/ogiboy/portfolio-app --skill omx-setup-ogiboy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omx-setup
Source: https://github.com/ogiboy/portfolio-app/tree/main/.codex/skills/omx-setup
Command: npx skills add https://github.com/ogiboy/portfolio-app --skill omx-setup-ogiboy

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about omx-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up oh-my-codex for a project?

Run `omx setup --force --verbose` in the project directory, choosing project scope when prompted or passing `--scope project`. Then verify the installation with `omx doctor`, which reports prompts, skills, AGENTS.md, and config status.

What is the difference between omx setup legacy and plugin mode?

Legacy mode installs OMX prompts, skills, and agents as local files under the Codex home directory. Plugin mode relies on Codex plugin discovery for bundled skills, archives legacy OMX-managed copies, and refreshes native agent TOMLs for agent_type routing.

How do I update AGENTS.md without losing my existing content?

Use `omx setup --merge-agents`, which preserves user-authored content and refreshes only the OMX-managed sections between the OMX:AGENTS:START and OMX:AGENTS:END markers. Non-interactive runs preserve the file by default without this flag.

Why does Codex show duplicate OMX skills after setup?

Duplicates appear when both the legacy `~/.agents/skills` directory and the current `~/.codex/skills` directory exist, since Codex discovers skills from both trees. Archive or remove `~/.agents/skills` as suggested by the setup cleanup hint.

What should I do if the omx-setup skill is missing in Codex?

Run `omx setup --verbose` in the intended scope, then `omx doctor` to check scope, Codex home, and skill root. Confirm SKILL.md exists under `./.codex/skills/omx-setup` for project scope or the user skill root for user scope.