setup

Route setup commands to omg-setup, omg-doctor, or mcp-setup entry points.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/oneforce/oh-my-gemini-cli --skill setup-oneforce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/oneforce/oh-my-gemini-cli/tree/main/skills/setup
Command: npx skills add https://github.com/oneforce/oh-my-gemini-cli --skill setup-oneforce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified setup entrypoint for install, diagnostics, and MCP configuration streamlines initial configuration and reduces confusion across environments.

Core Features & Use Cases

  • Unified setup entrypoint for install, diagnostics, and MCP configuration.
  • Route commands to the unified setup entrypoint and the legacy compatibility entrypoints (omg-setup, omg-doctor, mcp-setup) as needed.
  • Maintains backward compatibility and explicit argument routing to support different setup tasks.

Quick Start

Invoke the unified command /oh-my-gemini-cli:setup to launch the full setup wizard.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I run CLI installation, diagnostics, and MCP configuration in one workflow?

A unified setup command routes your arguments to the respective omg-setup, omg-doctor, or mcp-setup entry points, streamlining initial configuration and health checks into a single CLI workflow.

What is the best way to unify MCP server configuration and health checks?

Using a single setup wizard applies routing logic to map commands to diagnostics and mcp-setup entry points, unifying MCP server configuration and health checks for both fresh installations and maintenance.

Does the setup routing preserve backward compatibility with legacy omg-doctor commands?

Yes, the setup routing preserves backward compatibility with legacy omg-doctor commands by mapping them to their original entry points while supporting explicit argument handling for unified setup tasks.

Can I use the unified setup entrypoint for routine maintenance diagnostics?

Yes, you can use the unified setup entrypoint for routine maintenance diagnostics, as it guides users through health checks and configuration updates depending on the invoked route.

Why does explicit argument routing matter for CLI installation and MCP setup?

Explicit argument routing matters for CLI installation and MCP setup because it preserves backward compatibility and ensures commands map to the correct omg-setup or mcp-setup entry points without configuration conflicts.