setup

Route setup, diagnostics, and MCP requests to Oh-My-Claudecode flows.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Pryma-Tech/iris --skill setup-pryma-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/Pryma-Tech/iris/tree/main/cli/skills/setup
Command: npx skills add https://github.com/Pryma-Tech/iris --skill setup-pryma-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and streamlines environment setup for Oh-My-Claudecode by routing setup, diagnostics, and MCP tasks to the correct flows.

Core Features & Use Cases

  • Unified setup entrypoint that simplifies configuration across multiple flows.
  • Intelligent routing for doctor (diagnostics) and mcp (server configuration) commands with compatibility for legacy endpoints.
  • Clear user guidance and fallbacks to ensure safe, predictable setup outcomes.

Quick Start

Run the unified setup wizard with /oh-my-claudecode:setup to configure or diagnose your environment.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I run diagnostics and setup for Oh-My-Claudecode?

Run the unified setup wizard using /oh-my-claudecode:setup to configure or diagnose your environment, which routes your commands to the correct flows.

What is the best way to route MCP configuration commands in a Claudecode environment?

Use the unified setup entrypoint to route MCP server configuration commands, as it intelligently directs mcp tasks to the correct mcp-setup flow.

Can I use the setup wizard for both local and remote environments?

Yes, the setup wizard is applicable to both local and remote environments, handling routing for setup and diagnostics requests safely and predictably.

Does the setup routing support legacy endpoints for diagnostics?

Yes, the routing provides compatibility for legacy endpoints, ensuring that doctor diagnostics commands are successfully directed to the omc-doctor flow.

Why does my setup command not route to the correct diagnostic flow?

The setup skill implements first-argument routing, so ensuring the correct command syntax like doctor or mcp is used will route it to the appropriate flow.

Do I need a separate command to check environment compatibility?

No, the unified setup wizard provides clear user guidance and fallbacks to ensure safe configuration and check compatibility across multiple flows.