skills.rest
hotaq
hotaqCOMMUNITY
Explore all skills by this author →
GitHub

omx-setup

Configure oh-my-codex installation scope and skill delivery across CLI sessions.

Updated Apr 20, 2026
Search Tags:#validation#cli#hooks#migration#configuration#setup#installation
One-click install
npx skills add https://github.com/hotaq/Sprite_harmess --skill omx-setup-hotaq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omx-setup
Source: https://github.com/hotaq/Sprite_harmess/tree/main/.codex/skills/omx-setup
Command: npx skills add https://github.com/hotaq/Sprite_harmess --skill omx-setup-hotaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from installing, refreshing, and validating oh-my-codex so the current project and user-level environments stay consistent and ready to use.

Core Features & Use Cases

  • Scope-aware setup: Handles both user and project installation paths, including persisted scope preferences and TTY prompts.
  • Delivery mode management: Chooses between legacy and plugin-based skill delivery, with migration and cleanup behavior for existing installs.
  • Safety and validation: Preserves existing files when appropriate, guards active sessions, and verifies expected CLI, config, and hook markers.
  • Use Case: A developer can run setup on a fresh repo, refresh an existing workspace after a version change, or repair a broken local OMX installation without manually editing configuration files.

Quick Start

Run the omx setup command for your intended scope, then confirm the result 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 configure oh-my-codex installation for user and project environments?▼

To configure oh-my-codex installation, run the setup command for your intended scope. The process handles persisted scope preferences, interactive TTY prompts, and writes the necessary configuration files for both user and project environments.

What is the best way to migrate an existing OMX installation to plugin-based skill delivery?▼

Migrating an existing OMX installation to plugin-based skill delivery is handled automatically during setup. The process includes migration and cleanup behavior for existing installs, switching from legacy delivery while preserving appropriate files and verifying configuration markers.

Can I repair a broken local OMX installation without manually editing configuration files?▼

Yes, you can repair a broken local OMX installation without manual edits by running the setup command. It verifies expected CLI, config, and hook markers, resolving inconsistencies while guarding active sessions against unsafe modifications.

Does oh-my-codex setup work in non-interactive CLI sessions?▼

Oh-my-codex setup works in non-interactive CLI sessions by resolving install-mode and applying configuration without TTY prompts. It performs active-session safety checks and persisted scope handling to ensure environments stay consistent.

Why does refreshing a workspace after a version change require validating CLI and hook markers?▼

Refreshing a workspace requires validating CLI and hook markers because version changes can break existing configurations. Setup verifies these markers using the doctor command to confirm the environment is consistent and ready to use.

Related Skills

Explore More Software Engineering Skills→
ReScienceLabReScienceLab
10

using-git-worktrees

Create an isolated git worktree for a feature branch with automatic project setup.

Official
Advanced
HosungYouHosungYou
5

doctor

Diagnose Diverga plugin health with a 5-layer Check-Report-Fix pattern.

Community
Advanced
koasis89koasis89

omx-setup

Configure the oh-my-codex environment via CLI with scope and mode selection.

Community
Intermediate
wipcomputerwipcomputer
3

wip-file-guard

Block destructive writes and edits on protected AI identity files via Node.js hooks.

Official
Advanced