run-doctor

Run a read-only health check across environment, database, configuration, provider connectivity, and runtime layers.

277|88|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system --skill run-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-doctor
Source: https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/run-doctor
Command: npx skills add https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system --skill run-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Run-doctor identifies what’s preventing your GTM-OS from working by producing a clear, per-layer health report that shows which environment, database, configuration, provider connectivity, and runtime checks are passing or failing.

Core Features & Use Cases

  • 5-Layer Read-Only Health Check: Verifies environment, SQLite schema, framework + user config, live provider connectivity, and runtime state without modifying files.
  • Actionable Provider Fix Links: Surfaces one-click dashboard routes for failing or warned providers using /keys/connect/<provider> URLs.
  • In-Flight Setup Guardrails: Detects ongoing onboarding and, if needed, asks whether you want to run against in-flight state or resume setup first.

Use case: If you ask “is YALC working?” and some providers fail (e.g., missing DSN or expired keys), you get a structured diagnosis plus direct links to the exact provider connection screen to resolve it.

Quick Start

Ask the assistant to run the run-doctor health check.

Frequently Asked Questions about run-doctor

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

FAQPage Schema
How do I run a read-only health check for GTM-OS provider connectivity?

To run a read-only health check for GTM-OS, execute the diagnostics tool to verify environment, SQLite schema, configuration, provider connectivity, and runtime layers. It groups results by layer using PASS, FAIL, WARN, and SKIP statuses without modifying your files.

What does a YALC diagnostics report show when environment or database checks fail?

A YALC diagnostics report shows a structured per-layer breakdown of environment, SQLite schema, and runtime checks. It flags failing configurations with actionable statuses and surfaces direct dashboard routes to resolve provider connection issues.

Can I validate framework and user configuration without modifying my current setup?

Yes, you can validate framework and user configuration non-invasively. The diagnostic process executes strictly read-only checks across all layers, ensuring your current setup, database, and configuration files remain unmodified during the health verification.

How do I get direct links to fix expired keys or missing DSN issues in YALC?

To get direct links for expired keys or missing DSN issues, run the YALC health diagnostics. It automatically detects provider failures and surfaces one-click dashboard routes using /keys/connect/<provider> URLs for immediate resolution.

What happens if I run health diagnostics during an ongoing GTM-OS onboarding setup?

If you run diagnostics during ongoing GTM-OS onboarding, the tool detects the in-flight setup and asks whether you want to run the health check against the current incomplete state or resume the setup process first.

Why is my YALC setup not working even though my environment configuration seems correct?

Your YALC setup might not work due to hidden failures in SQLite schema, runtime state, or live provider connectivity. A 5-layer health diagnosis identifies the exact failing layer and provides direct links to fix provider-specific issues.