doctor

Validate OrchestKit installations and diagnose plugin, skill, and configuration issues.

217|20|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/yonatangross/orchestkit --skill doctor-yonatangross
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/yonatangross/orchestkit/tree/main/plugins/ork/skills/doctor
Command: npx skills add https://github.com/yonatangross/orchestkit --skill doctor-yonatangross

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides comprehensive health checks for your OrchestKit installation, identifying potential issues with plugins, skills, agents, hooks, and system configurations.

Core Features & Use Cases

  • System Diagnostics: Automatically detects installed plugins and validates their components (skills, agents, hooks).
  • Configuration Validation: Checks for permission rule reachability, schema compliance, and context budget.
  • Troubleshooting: Identifies issues with memory systems, Claude Code version compatibility, and external dependencies.
  • Use Case: After updating OrchestKit or encountering unexpected behavior, run /ork:doctor to get a detailed report of your system's health and specific recommendations for fixing any detected problems.

Quick Start

Run the doctor skill to perform a standard health check on your OrchestKit installation.

Frequently Asked Questions about doctor

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

FAQPage Schema
How do I run a health check on my OrchestKit installation?

Run a health check on your OrchestKit installation by executing the doctor command, which automatically detects installed plugins and validates their components, skills, agents, and hooks to provide a detailed diagnostics report.

What does OrchestKit plugin validation check for during system diagnostics?

OrchestKit plugin validation checks for permission rule reachability, schema compliance, context budget limits, memory system integrity, Claude Code version compatibility, and external dependencies to ensure system integrity.

Why does my OrchestKit system status show unexpected behavior after an update?

Unexpected behavior after an OrchestKit update often stems from configuration validation issues, deprecated schemas, or incompatible external dependencies, which the doctor diagnostics tool identifies and provides specific recommendations to fix.

Can I troubleshoot Claude Code version compatibility issues within OrchestKit?

Yes, you can troubleshoot Claude Code version compatibility by running the doctor health check, which validates your current version against installed plugins, hooks, and system configurations to detect and report compatibility conflicts.

How do I diagnose permission rule reachability and context budget limits in OrchestKit?

Diagnose permission rule reachability and context budget limits by running the doctor skill, which performs comprehensive configuration validation across your OrchestKit installation and reports any detected schema or permission issues.

When should I use a diagnostics tool for troubleshooting OrchestKit plugins and hooks?

Use a diagnostics tool for troubleshooting OrchestKit plugins and hooks when you encounter unexpected system behavior, after updating your installation, or when you need to validate external dependencies and ensure overall system health and integrity.