skills.rest
shayne-snap
shayne-snapCOMMUNITY
Explore all skills by this author →
Website𝕏@shayne_snapeGitHub

doctor

Diagnose Oh My Antigravity installation and Antigravity CLI plugin lifecycle issues.

3|Updated May 24, 2026
Search Tags:#diagnostics#installation check#runtime verification#workflow lifecycle#hook validation#CLI plugin
One-click install
npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill doctor-shayne-snap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/shayne-snap/oh-my-antigravity/tree/main/plugin/skills/doctor
Command: npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill doctor-shayne-snap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Omagy Doctor helps you quickly identify why the Oh My Antigravity installation or the Antigravity CLI plugin lifecycle is not working as expected.

Core Features & Use Cases

  • Installation & plugin discovery checks: Validates that the omagy CLI and its Antigravity plugin are discoverable by Antigravity CLI.
  • Lifecycle and hook validation: Confirms that required hooks exist and that the hook launcher/stop-hook smoke paths work, treating failures as runtime problems rather than cosmetic metadata issues.
  • Workflow command availability verification: Ensures the workflow surface (omagy workflow status|next|cancel|complete) is available so downstream skills like Ralph and Ultrawork can complete reliably.
  • Use case: When a user asks why a workflow command or in-session skill is missing, Doctor pinpoints whether it’s a PATH/build artifact issue, missing hook wiring, or a broken workflow command runtime.

Quick Start

Run omagy doctor --json from your current workspace to see failing checks first.

Frequently Asked Questions about doctor

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

FAQPage Schema
How do I diagnose why my Antigravity CLI plugin is not discoverable?▼

To diagnose Antigravity CLI plugin discoverability issues, run a diagnostics check that validates whether the omagy CLI and its plugin are properly recognized by the Antigravity CLI environment.

What is CLI plugin lifecycle hook validation and when do I need it?▼

CLI plugin lifecycle hook validation confirms required hooks exist and smoke paths work, needed when a workflow command or in-session skill is missing due to broken hook wiring or runtime failures.

How do I check if a workflow command is available in my current CLI environment?▼

To check workflow command availability, run a diagnostic verification ensuring the workflow surface like status, next, cancel, and complete commands are accessible and functioning in your current workspace.

Why does my workflow command fail even though the CLI is installed?▼

Your workflow command fails after CLI installation due to PATH or build artifact issues, missing hook wiring, or a broken workflow command runtime, classified as runtime failures rather than cosmetic metadata issues.

Can I use diagnostic checks to find missing hook wiring in my CLI installation?▼

Yes, you can use diagnostic checks to find missing hook wiring by confirming required hooks exist and validating the hook launcher and stop-hook smoke paths to treat failures as runtime problems.

What is the best way to troubleshoot an unavailable in-session skill?▼

The best way to troubleshoot an unavailable in-session skill is to run diagnostics that pinpoint whether the cause is a PATH or build artifact issue, missing hook wiring, or a broken workflow command runtime.

Related Skills

Explore More Software Engineering Skills→
shayne-snapshayne-snap
3

install

Install or repair the Omagy Antigravity plugin from a local checkout.

Community
Basic
LAF-USLAF-US

shell

Execute literal shell commands via /shell and report exit status and output.

Official
Basic
shayne-snapshayne-snap
3

cancel

Cancel active Omagy workflows via Antigravity CLI commands.

Community
Basic
trkbt10trkbt10
39

oxen-office

Inspect, build, and verify Office documents using the oxen CLI.

Community
Advanced