setup

Route OMC setup commands to omc-setup, omc-doctor, or mcp-setup flows.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Hyeonjun0527/yeon --skill setup-hyeonjun0527
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/Hyeonjun0527/yeon/tree/main/.codex/skills/setup
Command: npx skills add https://github.com/Hyeonjun0527/yeon --skill setup-hyeonjun0527

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes and simplifies the initial configuration flow by routing setup requests to the appropriate OMC setup path, reducing confusion and errors during install and update.

Core Features & Use Cases

  • Route bare setup calls to the correct OMC flows (omc-setup, omc-doctor, mcp-setup) based on the first argument.
  • Provide a single entrypoint (/oh-my-claudecode:setup) that preserves compatibility with legacy entrypoints.
  • Support common invocation patterns like wizard, doctor, and mcp with minimal user input.

Quick Start

Run /oh-my-claudecode:setup to start the full setup wizard

Frequently Asked Questions about setup

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

FAQPage Schema
How do I route OMC setup and configuration flows to the correct subsystem?

OMC setup routing is handled by interpreting the initial command argument, such as doctor or mcp, and delegating to the correct subsystem like omc-setup or mcp-setup with minimal user input.

What's the best way to run the omc-setup wizard for installation?

Running the unified setup entrypoint starts the full setup wizard, which routes bare setup calls to the correct OMC installation and configuration flows based on your first argument.

Does the OMC setup entrypoint preserve compatibility with legacy routing?

Compatibility entrypoints are preserved by providing a single unified routing path that routes requests to legacy OMC setup flows without breaking existing installation and configuration commands.

Can I use the setup command for both omc-doctor and mcp-setup contexts?

The setup command supports common invocation patterns including doctor and mcp, applying deterministic routing rules to delegate to omc-doctor and mcp-setup contexts during configuration.

Why does my bare setup call route to the wrong OMC configuration flow?

Bare setup calls follow a deterministic routing rule based on the first argument, so incorrect arguments will route to the wrong OMC configuration subsystem instead of the intended setup path.