omx-setup

Install and configure oh-my-codex for project and user environments.

Updated Jul 3, 2025
One-click install
npx skills add https://github.com/andrew-t-james/dotfiles --skill omx-setup-andrew-t-james
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omx-setup
Source: https://github.com/andrew-t-james/dotfiles/tree/main/dot_codex/skills/omx-setup
Command: npx skills add https://github.com/andrew-t-james/dotfiles --skill omx-setup-andrew-t-james

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OMX Setup automates installing and refreshing oh-my-codex for the current project plus user-level OMX directories, removing manual configuration steps.

Core Features & Use Cases

  • Resolve and persist the effective installation scope (user or project) to ensure consistent environments across runs.
  • Install prompts, native agent configs, and skills, and merge config.toml for a unified configuration surface.
  • Generate the project root AGENTS.md and validate OMX state indicators to support CI and local workflows.

Quick Start

Run omx setup to install or refresh OMX in the current project or user directories.

Frequently Asked Questions about omx-setup

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

FAQPage Schema
How do I install and configure OMX for a specific project?

To install OMX for a project, run the setup CLI command. This automates scope resolution, agent config creation, and config.toml merging to establish a unified project-level configuration surface.

What is oh-my-codex setup and when do I need to run it?

Oh-my-codex setup installs prompts, native agent configs, and skills while generating AGENTS.md. You need it to remove manual configuration steps and ensure consistent environments across CI and local workflows.

Does OMX setup support both user-level and project-scoped installations?

Yes, OMX setup resolves and persists the effective installation scope for both user and project directories. This ensures safe CLI-driven installation with predictable behavior across different target environments.

How do I refresh an existing OMX configuration without breaking my current setup?

Refreshing OMX configuration involves running the setup command, which validates OMX state indicators and merges config.toml safely. This ensures predictable behavior without overwriting existing project configurations.

What files does the OMX setup process generate or modify?

The OMX setup process generates the project root AGENTS.md, creates native agent configs, and merges config.toml. It also installs prompts and skills while persisting scope resolution across targets.

Are there limitations to using CLI-driven OMX installation for CI workflows?

CLI-driven OMX installation validates OMX state indicators to support CI workflows, but requires accurate scope resolution. You must ensure project and user directories are correctly targeted to avoid configuration merge conflicts.