skills.rest
JaCha00
JaCha00COMMUNITY
Explore all skills by this author →
GitHub

omx-setup

Configure oh-my-codex for user and project scopes with advanced flags.

Updated Jul 2, 2026
Search Tags:#integration#cli#configuration#setup#oh-my-codex
One-click install
npx skills add https://github.com/JaCha00/nais2-integration-complete --skill omx-setup-jacha00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omx-setup
Source: https://github.com/JaCha00/nais2-integration-complete/tree/main/.codex/skills/omx-setup
Command: npx skills add https://github.com/JaCha00/nais2-integration-complete --skill omx-setup-jacha00

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of setting up and configuring oh-my-codex for both user-level and project-level directories, providing a robust foundation for using oh-my-codex features.

Core Features & Use Cases

  • Setup and Configuration: Offers comprehensive setup options for oh-my-codex, including user and project scope configuration.
  • Advanced Flags: Provides various flags for specific setup behaviors like force overwrite, merge agents, dry run, and verbose output.
  • Scope Management: Allows users to choose between user-level and project-level setup.
  • Plugin and Legacy Modes: Offers the flexibility to use either plugin or legacy setup delivery modes.
  • Integration Verification: Ensures proper integration with Team CLI API interop markers.

Quick Start

Run the omx setup command to begin the setup process for oh-my-codex.

Frequently Asked Questions about omx-setup

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

FAQPage Schema
How do I configure oh-my-codex for both user and project scopes?▼

Configuring oh-my-codex involves running the `omx setup` command to target both user-level and project-level directories, applying settings with advanced flags like force overwrite, merge agents, and verbose output.

What is the difference between plugin and legacy mode when setting up oh-my-codex?▼

When setting up oh-my-codex, plugin and legacy modes determine the delivery method for configuration files. Plugin mode uses modern integration architecture, whereas legacy mode supports traditional setup delivery for older workflows.

Can I preview oh-my-codex configuration changes before applying them?▼

You can preview changes by running the oh-my-codex setup with the dry run flag. This simulates the configuration process for user and project scopes, showing exactly what will happen without modifying any existing files.

How do I force overwrite existing agents during an oh-my-codex setup?▼

You can force overwrite existing agents during oh-my-codex setup by enabling the force overwrite flag. If you prefer to preserve existing settings, use the merge agents flag to integrate new configurations seamlessly.

Does oh-my-codex setup verify integration with Team CLI API interop markers?▼

Oh-my-codex setup verifies integration with Team CLI API interop markers to ensure proper communication between configured scopes. This verification confirms that your plugin or legacy setup aligns with CLI interoperability requirements.

Related Skills

Explore More Software Engineering Skills→
1molchuan1molchuan
1

oh-my-ccg-init

Verify MCP, Codex, and Gemini endpoints and initialize RPI state.

Community
Intermediate
JustineDevsJustineDevs
2

rcs-setup

Configure the Roblox Creator Skills environment with CLI hooks and project scaffolding.

Community
Advanced
jimmi2051jimmi2051

skill

Manage local skills across user and project scopes via a unified CLI.

Community
Advanced
Devvraj10Devvraj10

post_merge_setup

Execute post-merge scripts and sync workflows automatically.

Community
Advanced