setup

Route setup, doctor, and MCP configuration requests to Oh-My-ClaudeCode workflows.

3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/marcmunoz-uno/jailbreak --skill setup-marcmunoz-uno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/marcmunoz-uno/jailbreak/tree/main/skills/setup
Command: npx skills add https://github.com/marcmunoz-uno/jailbreak --skill setup-marcmunoz-uno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates confusion and delays when installing, updating, diagnosing, or configuring MCP servers by routing setup requests to the correct Oh-My-ClaudeCode flow automatically.

Core Features & Use Cases

  • Unified setup entrypoint: Uses /oh-my-claudecode:setup as the single command for setup, doctor, and MCP configuration.
  • First-argument routing: Sends the request to the appropriate flow based strictly on the first argument (e.g., doctor, mcp, or default wizard routing).
  • Compatibility notes: Keeps older entrypoints valid while steering new users toward the unified setup command.

Example use case: A developer runs an install check after updating dependencies and then configures an MCP server without needing to remember multiple command variants.

Quick Start

Ask the system to run setup doctor --json to execute installation diagnostics and return structured output.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I route setup and MCP configuration requests to the correct workflow?

Setup routing directs installation, update, and MCP configuration requests to the correct Oh-My-ClaudeCode workflow by evaluating the first argument. It sends commands deterministically to the setup wizard, doctor diagnostics, or MCP server configuration flows.

What is the best way to run diagnostics after updating dependencies?

Run the doctor diagnostics workflow by passing the doctor argument to the setup command. This routes the request to the diagnostic flow, which checks your installation status and can return structured JSON output for automated processing.

Can I use a single command for setup, diagnostics, and MCP server configuration?

Yes, the unified setup command acts as a single entry point for installation wizards, doctor diagnostic runs, and MCP server configuration. It applies deterministic first-argument routing to direct your request to the appropriate workflow.

How does first-argument routing work for setup commands?

First-argument routing strictly evaluates the initial argument provided, such as doctor or mcp, to determine the target workflow. The remaining arguments are preserved and passed directly to the routed destination like omc-setup or mcp-setup.

Do older entrypoints still work after moving to the unified setup command?

Older entrypoints remain valid and functional for compatibility. The routing system steers new users toward the unified setup command while preserving backward compatibility for existing scripts and automation workflows.

Why is my MCP configuration not routing to the correct setup workflow?

MCP configuration routing depends strictly on the first argument provided. Ensure the command begins with the correct keyword like mcp so the routing logic can deterministically send the request to the mcp-setup workflow with preserved arguments.