omx-setup

Automate oh-my-codex installation and refresh across project and user directories.

2|1|Updated Oct 8, 2009
One-click install
npx skills add https://github.com/riethmayer/dotfiles --skill omx-setup-riethmayer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omx-setup
Source: https://github.com/riethmayer/dotfiles/tree/main/stow/agents/.agents/skills/omx-setup
Command: npx skills add https://github.com/riethmayer/dotfiles --skill omx-setup-riethmayer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the installation and refresh of oh-my-codex across the current project and user-level directories, simplifying setup and ongoing maintenance.

Core Features & Use Cases

  • Create and persist scoped configurations for OMX setup, including prompts, agent configs, and skill registrations.
  • Merge configuration files (config.toml) according to the resolved scope and verify interop markers in built artifacts.
  • Generate project-root AGENTS.md and write hud-config.json to coordinate runner integrations.

Quick Start

Run omx setup to install or refresh oh-my-codex for the current project and 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 automate oh-my-codex installation and refresh across project directories?

Automating oh-my-codex installation involves running the setup command to apply scoped configurations, create directories, install prompts and agent configs, and generate AGENTS.md and hud-config.json across current project and user directories.

What is scope resolution when setting up OMX configurations?

Scope resolution for OMX configurations determines where setup applies by using the --scope flag or a persisted setup file, allowing targeted installation and updates across either project-level or user-level directories.

How do I merge config.toml files during agent configuration setup?

Merging config.toml files during setup is handled automatically according to the resolved scope, combining project and user-level settings while verifying interop markers in the built artifacts.

Can I use oh-my-codex setup to generate AGENTS.md and hud-config.json?

Yes, oh-my-codex setup generates a project-root AGENTS.md file and writes hud-config.json to coordinate runner integrations, simplifying workflow automation and agent configuration across repositories.

What's the best way to persist scoped configurations for OMX across multiple repositories?

The best way to persist scoped OMX configurations is using a persisted setup file during the installation process, which stores scopes, prompts, agent configs, and skill registrations for ongoing maintenance.