setup

Route setup, doctor, and MCP configuration requests by first argument token.

Updated Apr 29, 2026

Search Tags:#routing #compatibility #configuration #diagnostics #mcp server #setup wizard #command parsing

Ready to run

npx skills add https://github.com/nichobbs/lyric-lang --skill setup-nichobbs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/nichobbs/lyric-lang/tree/main/.claude/skills/setup
Command: npx skills add https://github.com/nichobbs/lyric-lang --skill setup-nichobbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents users from getting sent to the wrong setup flow by unifying multiple setup-related entrypoints under a single command and routing based on the first argument.

Core Features & Use Cases

Unified setup entrypoint: Use /oh-my-claudecode:setup for full setup wizard, installation diagnostics, and MCP server configuration.
First-argument routing: Decide the destination flow immediately using only the first token after setup (or a direct compatibility mapping).
Compatibility preservation: Keep /oh-my-claudecode:omc-setup, /oh-my-claudecode:omc-doctor, and /oh-my-claudecode:mcp-setup working while steering new guidance toward /oh-my-claudecode:setup.

Quick Start

Tell the AI: /oh-my-claudecode:setup doctor --json to route to the doctor flow and pass through the remaining arguments.

Frequently Asked Questions about setup

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

FAQPage Schema

How do I route MCP server configuration requests to the correct backend flow?▼

MCP server configuration requests are routed to the correct backend flow by parsing the first argument token after the setup command, deterministically directing empty/default, doctor, and mcp tokens to their respective workflows while preserving remaining arguments.

What is the best way to unify multiple setup entrypoints into a single command?▼

Unifying multiple setup entrypoints requires routing based on the first argument token, applying compatibility mappings for direct commands like omc-setup, omc-doctor, and mcp-setup while steering new guidance toward a single unified setup entrypoint.

Can I preserve remaining arguments when routing setup commands to different flows?▼

Remaining arguments are preserved during command routing by extracting only the first token for flow determination, allowing subsequent flags and parameters to pass through to the destination backend flow without ambiguity.

Why do I get sent to the wrong setup flow when using compatibility commands?▼

Getting sent to the wrong setup flow occurs when first-argument token mappings lack deterministic routing; applying unambiguous token mappings for empty/default, doctor, and mcp ensures requests reach the correct backend flow every time.

Do I need separate commands for installation diagnostics and MCP server configuration?▼

Separate commands are not required; a unified setup entrypoint handles installation wizards, diagnostics, and MCP server configuration by routing based on the first argument token, though compatibility mappings preserve legacy direct commands.