setup

Route setup requests to OMC flows by analyzing the first argument.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/jimmi2051/oh-my-copilot --skill setup-jimmi2051
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/jimmi2051/oh-my-copilot/tree/main/plugins/omc-copilot/skills/setup
Command: npx skills add https://github.com/jimmi2051/oh-my-copilot --skill setup-jimmi2051

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically route install/update requests to the correct OMC setup flow (omc-setup, omc-doctor, mcp-setup) to streamline plugin setup and diagnostics.

Core Features & Use Cases

  • Unified entrypoint: use /oh-my-claudecode:setup to access all setup paths.
  • Routing by the first argument to the appropriate sub-flow (setup, doctor, mcp-setup).
  • Compatibility entrypoints for legacy usage.

Quick Start

Run the unified command 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 automate routing for CLI setup requests to different orchestration flows?

Automate CLI setup routing by analyzing the first argument to direct requests to the correct OMC flow, covering plugin installation, configuration, and diagnostics across omc-setup, omc-doctor, and mcp-setup paths.

What is OMC setup routing and when do I need it for plugin orchestration?

OMC setup routing is an automation mechanism that analyzes your initial CLI argument to automatically direct plugin installation and configuration tasks to the appropriate sub-flow, needed when managing multiple setup paths.

Does OMC setup support compatibility entrypoints for legacy CLI usage?

OMC setup supports compatibility entrypoints for legacy usage, allowing existing commands to route correctly to the updated omc-setup, omc-doctor, and mcp-setup flows without breaking previous automation scripts.

Best way to run diagnostics and configuration checks through OMC setup flows?

The best way to run diagnostics is using the unified setup entrypoint, which routes your first argument to the omc-doctor flow to automatically execute configuration checks and plugin diagnostics.

Why does my OMC setup routing fail when I pass multiple arguments to the CLI?

OMC setup routing fails because it enforces a strict first-argument routing rule, analyzing only the initial argument to determine the correct flow, meaning subsequent arguments may not trigger the expected automation path.