omc-doctor

Diagnose and fix oh-my-claudecode installation issues across customized environments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix oh-my-claudecode installation issues to keep Claude tooling healthy and ready.

Core Features & Use Cases

  • Validates plugin version consistency and detects outdated or missing installations.
  • Detects legacy hooks, bash scripts, CLAUDE.md configurations, and cached plugin data that can cause duplicates or failures.
  • Guides remediation by identifying stale caches and legacy curl-installed content, helping teams restore standard plugin-based workflows.

Quick Start

Run the OMC Doctor to diagnose and fix oh-my-claudecode installation issues.

Frequently Asked Questions about omc-doctor

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

FAQPage Schema
How do I diagnose oh-my-claudecode installation issues caused by legacy hooks?

Diagnose oh-my-claudecode installation issues by checking legacy hooks in settings.json, verifying plugin version presence, and identifying stale bash scripts to determine system health and remediation steps.

What causes duplicate plugin setups and failures in customized Claude environments?

Duplicate plugin setups and failures in customized Claude environments are caused by legacy CLAUDE.md configurations, cached plugin data, and legacy curl-installed content conflicting with standard plugin-based workflows.

Can I fix oh-my-claudecode failures when CLAUDE_CONFIG_DIR is customized?

Yes, you can fix oh-my-claudecode failures in customized CLAUDE_CONFIG_DIR environments by detecting legacy bash scripts, verifying plugin cache status, and removing legacy curl-installed content to restore standard workflows.

How do I detect and remove legacy curl-installed content from my Claude plugin setup?

Detect and remove legacy curl-installed content by running a health check that verifies plugin version consistency, identifies stale caches, and guides remediation to restore standard plugin-based workflows.

Why does my Claude plugin setup fail after upgrading from legacy bash scripts?

Claude plugin setups fail after upgrading from legacy bash scripts because outdated CLAUDE.md configurations and legacy hooks in settings.json cause duplicates or conflicts across plugin installations.