omni-doctor

Diagnose and resolve copilot-omni installation and operational issues.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Jurel89/copilot-omni --skill omni-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omni-doctor
Source: https://github.com/Jurel89/copilot-omni/tree/main/skills/omni-doctor
Command: npx skills add https://github.com/Jurel89/copilot-omni --skill omni-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill is designed to quickly diagnose and address common installation and operational issues with copilot-omni, streamlining the troubleshooting process for users.

Core Features & Use Cases

  • Plugin Version Checking: Determines if the installed version is up-to-date or outdated.
  • Plugin Manifest Verification: Validates the plugin manifest for correctness and completeness.
  • Legacy State Directory Detection: Identifies and advises on migrating from old v1.x state directories.
  • Configuration and Directory Checks: Inspects the .omni directory structure and .omni/config.json for proper setup.
  • Legacy Content Identification: Identifies legacy curl-installed content that may conflict with the plugin system.
  • Active Session Management: Lists and analyzes active sessions of autopilot, ralph, ultrawork, and ultraqa, providing insights and warnings if needed.

Quick Start

Run the omni-doctor skill to check and resolve issues in your copilot-omni setup.

Frequently Asked Questions about omni-doctor

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

FAQPage Schema
How do I troubleshoot copilot-omni installation and operational issues?

To troubleshoot copilot-omni installation issues, run a diagnostic check that performs version verification, validates the plugin manifest, and inspects the directory structure integrity to identify and resolve setup conflicts.

Why is my copilot-omni plugin failing after a recent update?

Copilot-omni plugin failures often stem from outdated versions or invalid manifests. Running a diagnostic check verifies the installed version, validates manifest correctness, and detects legacy curl-installed content causing conflicts.

How do I detect and migrate legacy v1.x state directories in copilot-omni?

To detect legacy v1.x state directories in copilot-omni, run a directory integrity validation that identifies old state paths and advises on the necessary migration steps to prevent operational conflicts.

How can I check active autopilot and ultrawork sessions in copilot-omni?

You can check active autopilot, ralph, ultrawork, and ultraqa sessions by running a session analysis that lists active processes, provides operational insights, and generates warnings for potential session conflicts.

What is the best way to validate the copilot-omni configuration file setup?

The best way to validate the copilot-omni configuration is to inspect the .omni directory structure and .omni/config.json file, checking for proper setup, completeness, and structural integrity.

Does copilot-omni doctor work without dependencies to resolve plugin issues?

Yes, the copilot-omni diagnostic operates without external dependencies, using scripts to independently perform version checks, manifest verification, and directory integrity validation to resolve plugin issues.