skills.rest
YeaChan05
YeaChan05COMMUNITY
Explore all skills by this author →
GitHub

doctor

Diagnose OMX installation issues and guide fixes for Codex users.

Updated Jan 4, 2026
Search Tags:#hooks#codex#diagnostics#installation#omx#plugin-cache#legacy-scripts
One-click install
npx skills add https://github.com/YeaChan05/Remittance --skill doctor-yeachan05
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/YeaChan05/Remittance/tree/main/.codex/skills/doctor
Command: npx skills add https://github.com/YeaChan05/Remittance --skill doctor-yeachan05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses OMX installation issues and guides fixes for Codex users.

Core Features & Use Cases

  • Comprehensive checks across plugin cache, hook configurations, legacy Bash scripts, AGENTS.md presence, and legacy curl-installed content.
  • Generates structured reports with actionable remediation steps and clear priorities for resolving installation problems.
  • Use Case: When OMX reports duplicates from legacy paths or missing configuration, run the doctor to identify the root cause and apply recommended fixes.

Quick Start

Run the OMX Doctor to diagnose your Codex installation and follow the guided fixes.

Frequently Asked Questions about doctor

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

FAQPage Schema
Why does OMX report duplicates from legacy paths or missing configuration?▼

OMX reports duplicates when legacy curl-installed content or outdated hook scripts conflict with active plugin cache paths. The doctor identifies these legacy directories and config mismatches across user and project scopes to provide structured remediation.

How do I diagnose OMX installation issues in Codex?▼

Run the OMX doctor to diagnose Codex installation issues. It executes comprehensive checks across plugin cache, config.toml, settings.json, hook scripts, AGENTS.md, and legacy directories to generate a structured report with actionable fixes.

What does the OMX doctor check for in plugin cache and hook configuration?▼

The OMX doctor validates plugin cache integrity, verifies hook configuration in config.toml and settings.json, detects legacy Bash scripts, checks AGENTS.md presence, and scans for legacy curl-installed content across both user and project scopes.

Can I automatically fix legacy script and hook configuration conflicts in OMX?▼

Yes, the OMX doctor provides optional auto-fix steps for legacy script and hook configuration conflicts. It generates structured reporting with clear priorities and actionable remediation steps to resolve detected installation problems.

Does the OMX doctor validate AGENTS.md presence across user and project scopes?▼

Yes, the OMX doctor checks for AGENTS.md presence and validates configurations across both user and project scopes. It detects missing files and legacy curl-installed content to ensure complete Codex installation integrity.

What are the limitations of using the OMX doctor for Codex installation diagnostics?▼

The OMX doctor focuses on diagnosing plugin cache, hook configuration, legacy scripts, and AGENTS.md presence but does not modify configurations without optional auto-fix steps. Users must review structured reports before applying recommended remediation.

Related Skills

Explore More Software Engineering Skills→
wmasfoewmasfoe

doctor

Diagnose OMX installation issues and restore a healthy Codex environment.

Community
Advanced
Weihong-LiuWeihong-Liu
6

doctor

Diagnose and resolve common OMX installation issues.

Community
Intermediate
prthikprthik
1

doctor

Diagnose oh-my-codex installation issues across plugin versions, hooks, and legacy content.

Community
Intermediate
JaCha00JaCha00

doctor

Diagnose and resolve OMX installation issues with Bash scripts.

Community
Advanced