One-click install
npx skills add https://github.com/Leap0920/Clean-Portfolio --skill setup-leap0920
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/Leap0920/Clean-Portfolio/tree/main/%25USERPROFILE%25/.openclaude/plugins/cache/omc/oh-my-claudecode/4.14.0/skills/setup
Command: npx skills add https://github.com/Leap0920/Clean-Portfolio --skill setup-leap0920

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents setup-related commands from going to the wrong workflow by ensuring the request is routed based on the first argument.

Core Features & Use Cases

  • Unified setup entrypoint: Use /oh-my-claudecode:setup to handle full setup, diagnostics, and MCP configuration.
  • First-argument routing: Routes immediately to the correct flow when the first token is wizard/local/global/--force, doctor, or mcp.
  • Compatibility safeguards: Keeps older entrypoints valid while steering new guidance toward /oh-my-claudecode:setup.

Quick Start

Use /oh-my-claudecode:setup doctor to run installation diagnostics and forward any extra options to the doctor flow.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I route CLI setup commands to the correct installation workflow?

CLI setup commands are routed by parsing the first argument token, directing requests immediately to the correct installation, diagnostic, or MCP configuration flow based on matched keywords.

What is first-argument routing for command-line setup entrypoints?

First-argument routing evaluates the initial command token like doctor or mcp, steering the request to the matching setup flow while passing any additional flags directly through to the target process.

How do I run installation diagnostics and pass extra flags through the setup wizard?

Run the setup command with doctor as the first argument to route to the diagnostic flow; any additional command-line flags provided after the doctor token are forwarded directly to the diagnostic process.

Can I use older omc-doctor and mcp-setup entrypoints instead of the unified setup command?

Older entrypoints remain valid through compatibility safeguards, but new guidance steers users toward a unified setup command that handles full setup, diagnostics, and MCP configuration in one place.

Why do my setup commands go to the wrong workflow when using command-line flags?

Commands route incorrectly when first-argument parsing rules are not applied; matching the initial token to wizard, doctor, or mcp ensures the request enters the correct setup flow before processing additional flags.

Does the setup routing support MCP configuration requests with additional arguments?

MCP configuration requests route correctly when mcp is the first argument, with argument passthrough ensuring any subsequent flags are forwarded to the MCP setup flow without being lost.