omx-setup

Automate OMX installation and refresh across project and user directories.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/eszxcvfd/ANIZAKI --skill omx-setup-eszxcvfd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omx-setup
Source: https://github.com/eszxcvfd/ANIZAKI/tree/main/.agents/skills/omx-setup
Command: npx skills add https://github.com/eszxcvfd/ANIZAKI --skill omx-setup-eszxcvfd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the installation and refresh of OMX across both the current project and user-level directories, ensuring consistent setup and easy maintenance.

Core Features & Use Cases

  • Resolve scope with explicit flag, persisted state, or interactive prompts to determine target directories.
  • Create and persist effective scope, organize project and user paths for OMX assets.
  • Install prompts, native agent configs, skills, and merge configuration files across scopes.
  • Verify interop markers exist in built artifacts (e.g., dist/cli/team.js) to ensure runtime readiness.
  • Generate project-root AGENTS.md from templates, updating placeholders as needed.
  • Configure notify hooks and HUD references under .omx to centralize runtime configuration.

Quick Start

Run omx setup --force --verbose to install or refresh OMX for the current project and all 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 OMX installation and configuration refresh across project and user directories?

To automate OMX installation and configuration refresh, run omx setup --force --verbose to install prompts, native agent configs, and skills across both project and user scopes while verifying runtime readiness.

What is scope resolution when setting up OMX for a project?

Scope resolution determines target directories for OMX assets by checking explicit flags, persisted state, or interactive prompts, ensuring configuration merges apply to the correct project or user-level paths.

Do I need the local OMX CLI to install prompts and generate project configuration files?

Yes, you need the local OMX CLI installed, access to the project tree, and write permissions to generate artifacts like AGENTS.md and merge configuration files under the .omx directory.

How does OMX verify runtime readiness after configuration merges?

OMX verifies runtime readiness by checking for interop markers in built artifacts, such as dist/cli/team.js, ensuring the generated configurations and skills are properly linked for execution.

What is the best way to configure notify hooks and HUD references for OMX?

The best way to configure notify hooks and HUD references is to run the setup process, which centralizes these runtime configurations under the .omx directory within your project paths.

Why does my OMX setup fail to update placeholders in the AGENTS.md template?

OMX setup fails to update placeholders when it lacks write permissions for the project tree, preventing it from generating the project-root AGENTS.md file and organizing OMX asset paths correctly.