home / skills / yeachan-heo / oh-my-claudecode / setup

setup skill

safe

This skill guides unified setup, diagnostics, and MCP configuration for Claude Code orchestration, streamlining installation and environment readiness.

npx playbooks add skill yeachan-heo/oh-my-claudecode --skill setup

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.2 KB

---
name: setup
description: Unified setup entrypoint for install, diagnostics, and MCP configuration
---

# Setup

Use `/oh-my-claudecode:setup` as the unified setup/configuration entrypoint.

## Usage

```bash
/oh-my-claudecode:setup                # full setup wizard
/oh-my-claudecode:setup doctor         # installation diagnostics
/oh-my-claudecode:setup mcp            # MCP server configuration
/oh-my-claudecode:setup wizard --local # explicit wizard path
```

## Routing

Route by the first argument:

- No argument, `wizard`, `local`, `global`, or `--force` -> run `/oh-my-claudecode:omc-setup {{ARGUMENTS}}`
- `doctor` -> run `/oh-my-claudecode:omc-doctor {{ARGUMENTS_AFTER_DOCTOR}}`
- `mcp` -> run `/oh-my-claudecode:mcp-setup {{ARGUMENTS_AFTER_MCP}}`

Examples:

```bash
/oh-my-claudecode:omc-setup {{ARGUMENTS}}
/oh-my-claudecode:omc-doctor {{ARGUMENTS_AFTER_DOCTOR}}
/oh-my-claudecode:mcp-setup {{ARGUMENTS_AFTER_MCP}}
```

## Notes

- `/oh-my-claudecode:omc-setup`, `/oh-my-claudecode:omc-doctor`, and `/oh-my-claudecode:mcp-setup` remain valid compatibility entrypoints.
- Prefer `/oh-my-claudecode:setup` in new documentation and user guidance.

Task: {{ARGUMENTS}}

Overview

This skill provides a unified setup entrypoint for installation, diagnostics, and MCP configuration of the Teams-first Multi-agent orchestration for Claude Code. It standardizes how users invoke the setup flow, run health checks, and configure the MCP server across local and global environments. Use this single command to simplify onboarding and troubleshooting.

How this skill works

The skill routes the first CLI argument to one of three internal flows: a full setup wizard, a diagnostic doctor, or an MCP configuration routine. Calling without arguments or with wizard/local/global/--force delegates to the omc-setup flow; doctor and mcp route to omc-doctor and mcp-setup respectively. The routing preserves existing compatibility entrypoints while encouraging the new unified command.

When to use it

Onboarding a new developer or environment to Claude Code orchestration
Running installation diagnostics to detect missing dependencies or misconfiguration
Configuring or reconfiguring the MCP server for multi-agent coordination
Switching between local and global setup modes or forcing a re-run
As the recommended entrypoint in new documentation and scripts

Best practices

Use /oh-my-claudecode:setup as the primary command in docs and scripts to avoid fragmentation
Run doctor before reporting issues to capture environment diagnostics
Prefer explicit flags (wizard, --local, --force) when reproducing setups across machines
Keep legacy entrypoints available for compatibility but migrate references to the unified setup
Automate setup invocation in CI by passing non-interactive arguments where supported

Example use cases

Run a full interactive setup for a fresh developer machine: /oh-my-claudecode:setup
Execute installation diagnostics on a CI agent or developer laptop: /oh-my-claudecode:setup doctor
Configure MCP server for a local development cluster: /oh-my-claudecode:setup mcp
Force a global reconfiguration in a shared environment: /oh-my-claudecode:setup --force
Explicitly launch the local wizard path for reproducible onboarding: /oh-my-claudecode:setup wizard --local

FAQ

Are the old commands still supported?

Yes. /oh-my-claudecode:omc-setup, /oh-my-claudecode:omc-doctor, and /oh-my-claudecode:mcp-setup remain valid for compatibility.

Which argument triggers the MCP configuration flow?

Use the mcp argument: /oh-my-claudecode:setup mcp to route to the MCP setup routine.