setup

Route setup commands to OMC setup, doctor, or MCP flows.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/INNERJOINT/HarnessSkills --skill setup-innerjoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/INNERJOINT/HarnessSkills/tree/main/skills/setup
Command: npx skills add https://github.com/INNERJOINT/HarnessSkills --skill setup-innerjoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates multiple installation and diagnostic entrypoints into a single, predictable command so users don't need to remember multiple setup keywords and routing rules.

Core Features & Use Cases

  • Routes the first argument of the setup invocation to the correct OMC flow so installers and diagnostics run immediately on the intended path.
  • Maps no-argument, wizard, local, global, and --force to the omc-setup wizard, maps doctor to omc-doctor, and maps mcp to mcp-setup while preserving remaining arguments.
  • Maintains backward compatibility with existing /oh-my-claudecode:omc-setup, /oh-my-claudecode:omc-doctor, and /oh-my-claudecode:mcp-setup entrypoints.

Quick Start

Use /oh-my-claudecode:setup mcp github to run the MCP configuration flow targeting GitHub.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I route OMC setup commands to the correct installer flow?

Routing OMC setup commands requires parsing the first argument to direct invocations to the correct installer flow, forwarding remaining arguments unchanged to the target setup wizard.

What's the best way to diagnose MCP server configuration issues?

Diagnosing MCP server configuration issues involves routing the doctor argument to the omc-doctor diagnostic flow, which runs diagnostics immediately on the intended path.

Can I install and configure MCP servers globally using a single command?

Installing and configuring MCP servers globally uses a single command that maps the global argument to the omc-setup wizard, preserving remaining arguments for immediate configuration.

Does the OMC setup router maintain backward compatibility with existing entrypoints?

The OMC setup router maintains backward compatibility with existing entrypoints, allowing direct invocation of omc-setup, omc-doctor, and mcp-setup without routing changes.

How do I force an MCP setup flow to overwrite existing configurations?

Forcing an MCP setup flow to overwrite configurations uses the force argument, which maps to the omc-setup wizard while preserving remaining arguments unchanged.

Why should I use a unified command instead of remembering multiple setup keywords?

Using a unified command consolidates multiple installation and diagnostic entrypoints into a single predictable path, eliminating the need to remember separate setup keywords and routing rules.