doctor

Diagnose and resolve common OMX installation issues.

6|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Weihong-Liu/GenericAgent_project --skill doctor-weihong-liu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/Weihong-Liu/GenericAgent_project/tree/main/.codex/skills/doctor
Command: npx skills add https://github.com/Weihong-Liu/GenericAgent_project --skill doctor-weihong-liu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users quickly identify and fix common installation issues in the OMX environment, such as outdated plugins, legacy hooks, and configuration errors.

Core Features & Use Cases

  • Version Control: Checks the installed OMX plugin version against the latest version.
  • Configuration Review: Inspects hook configurations for deprecated practices.
  • Legacy Script Removal: Identifies and removes legacy scripts that may interfere with OMX functionality.
  • AGENTS.md Validation: Ensures the AGENTS.md file is up to date with OMX configuration.
  • Cache Management: Clears outdated plugin caches.
  • Legacy Content Cleanup: Identifies and removes legacy OMX content from previous installations.
  • Use Case: If you encounter a problem with OMX and are unsure of the cause, the Doctor Skill can quickly identify the issue and guide you through fixing it.

Quick Start

Run 'doctor' to begin diagnosing OMX issues.

Frequently Asked Questions about doctor

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

FAQPage Schema
How do I diagnose and fix OMX installation issues like outdated plugins?

To resolve OMX installation issues, run a diagnostic command that checks installed plugin versions against the latest releases and inspects hook configurations. This process identifies outdated components and configuration errors, guiding you through the necessary fixes to restore functionality.

What causes OMX configuration errors and legacy hooks during installation?

OMX configuration errors and legacy hooks are typically caused by outdated plugins or remnants from previous installations. Diagnostic scripts review your AGENTS.md file and hook configurations to detect deprecated practices and legacy content that interfere with proper OMX functionality.

How do I clean up legacy scripts and outdated plugin caches in OMX?

To clean up legacy scripts and outdated plugin caches in OMX, execute a diagnostic command that identifies and removes legacy content from previous installations. This clears outdated caches and eliminates deprecated scripts that interfere with current OMX operations.

Do I need specific access permissions to diagnose OMX environment issues?

Yes, diagnosing OMX environment issues requires access to OMX configuration files and the ability to execute script files within the OMX environment. These permissions are necessary to inspect hook configurations, validate the AGENTS.md file, and clear plugin caches.

Why is my OMX installation not working after an update?

An OMX installation may not work after an update due to outdated plugin caches, legacy hooks, or configuration errors. Run a diagnostic command to inspect your environment, validate the AGENTS.md file, and remove legacy content that conflicts with the new version.

Can I validate the AGENTS.md file against my current OMX configuration?

Yes, you can validate the AGENTS.md file against your current OMX configuration by running a diagnostic command. This checks that the file is up to date with your OMX configuration and identifies any deprecated practices or legacy content that require correction.