One-click install
npx skills add https://github.com/realsigridjin/oh-my-codex --skill doctor-realsigridjin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/realsigridjin/oh-my-codex/tree/main/skills/doctor
Command: npx skills add https://github.com/realsigridjin/oh-my-codex --skill doctor-realsigridjin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies installation, configuration, versioning, cache, and legacy-content issues that can prevent oh-my-codex from working correctly.

Core Features & Use Cases

  • Installation Diagnostics: Check the installed plugin version, latest npm release, cached versions, and required CODEX.md configuration.
  • Legacy Cleanup Guidance: Detect outdated hooks, scripts, agents, commands, and skills that may cause duplicate or conflicting behavior.
  • Safe Remediation: Generate a structured health report and apply cleanup or configuration fixes only after the user confirms.
  • Use Case: Run this Skill when oh-my-codex behaves unexpectedly after an upgrade or when migrating from a curl-based installation to the plugin system.

Quick Start

Ask the doctor skill to diagnose the current oh-my-codex installation and provide a report with recommended fixes.

Frequently Asked Questions about doctor

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

FAQPage Schema
How do I diagnose oh-my-codex installation problems after an upgrade?

Diagnosing oh-my-codex installation problems involves checking the installed plugin version, latest npm release, cached versions, and required CODEX.md configuration. This generates a structured health report with recommended fixes.

Why does oh-my-codex behave unexpectedly after migrating from a curl-based installation?

Unexpected behavior after migrating from a curl-based installation usually stems from legacy hooks, scripts, agents, commands, and skills causing duplicate or conflicting behavior. Detecting and removing this outdated content resolves the conflicts.

What is the best way to clean up stale caches and legacy files in oh-my-codex?

The best way to clean up stale caches and legacy files in oh-my-codex is to run a diagnostic that detects outdated hooks and scripts, then apply safe remediation fixes only after user confirmation to prevent destructive data loss.

Do I need access to local Codex configuration directories to repair plugin version mismatches?

Yes, repairing plugin version mismatches requires access to local Codex configuration directories and npm metadata to evaluate the installed version against the latest release and apply configuration repair safely.

Can I automatically apply configuration fixes for missing CODEX.md files?

You cannot automatically apply configuration fixes for missing CODEX.md files because the diagnostic tool requires explicit user confirmation before applying any destructive remediation or cleanup actions to your local environment.

Does oh-my-codex plugin troubleshooting detect outdated hooks and scripts?

Yes, oh-my-codex plugin troubleshooting detects outdated legacy hooks, scripts, agents, commands, and skills that may cause duplicate or conflicting behavior, providing guidance for complete migration cleanup.