doctor

Featured

OrchestKit doctor for health diagnostics across manifest integrity, hook configuration, skill validation, agent frontmatter, MCP server connectivity, CC version compatibility, and permission rules. Reports issues with severity levels and auto-remediation suggestions. Validates component counts, detects orphaned entries, and checks CC version matrix compliance. Use when diagnosing plugin health, troubleshooting configuration issues, or running pre-release checks.

AI & Automation 229 stars 25 forks Updated today MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
79
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# OrchestKit Health Diagnostics Host-neutral workflow. Invoke by skill name (`doctor`). Claude Code slash routing, YAML hook loaders, and `.claude/chain` live in `references/claude-code.md`. ## Argument Resolution ```python FLAGS = "$ARGUMENTS" # Full argument string, e.g., "--verbose" or "--json" FLAG = "$ARGUMENTS[0]" # First token: -v, --verbose, --json, --category=X # $ARGUMENTS[0], $ARGUMENTS[1] for indexed access (CC 2.1.59) ``` ## STEP 0: Choose Scope (AskUserQuestion — M118 #1464) A full doctor run takes ~20s. Most invocations only need one slice. Ask the user up-front so voice-flow shortcuts ("just the MCPs") map cleanly: ```python # Skip the prompt when an explicit scope arg or env override is present: # doctor cc → skip, use cc-only # doctor mcp → skip, use mcp-only # doctor plugin → skip, use plugin-only # ORK_DOCTOR_SCOPE=all (or any of the above) → skip, use the env value # # Otherwise, ask: AskUserQuestion(questions=[{ "question": "What should doctor check?", "header": "Scope", "options": [ {"label": "Everything (default)", "description": "Full system health — ~20s; runs all 15 categories"}, {"label": "CC version & features only", "description": "Categories 10 + 13 + 14; ~3s — for 'is my CC up to date?'"}, {"label": "MCP servers only", "description": "Category 12 (incl. pinning sub-check); ~5s — for 'are MCPs working?'"}, {"label": "Plugin health only", "description": "Categories 0-3 + 5 (skills, agent...

Details

Author
yonatangross
Repository
yonatangross/orchestkit
Created
8 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

doctor

Use when diagnosing CLI environment health, node setup, permissions, or configuration drift

4 Updated today
imMamdouhaboammar
AI & Automation Featured

doctor

Health-check the user's Claude Code setup and fix issues: diagnose installation health — what the `claude doctor` terminal diagnostics cover — from local data (duplicate or leftover installs, PATH, unparseable settings files, broken or colliding agent definitions, skills whose frontmatter fails to parse); find unused skills, MCP servers, and plugins versus their context cost and disable dead weight; deduplicate local CLAUDE.md files against checked-in ones; trim checked-in CLAUDE.md files by cutting content a session could derive from the codebase (directory layouts, tech-stack lists, architecture overviews) while keeping gotchas, rationale, and non-standard conventions; migrate always-loaded CLAUDE.md guidance into lazy skills and nested CLAUDE.md files; flag slow hooks and context-heavy extensions; check the installed version is current; make auto mode the default permission mode; and pre-approve frequently denied read-only commands. Use when the user asks for a doctor run, checkup, audit, tune-up, or clean

64,796 Updated yesterday
asgeirtj
AI & Automation Solid

doctor

Run diagnostic checks on the agent workspace. Triggers on /agent:doctor, "diagnóstico", "diagnostico", "doctor", "health check", "agent health", "checkup", "revisar agente", "agent broken", "fix agent", "revisa el agente".

62 Updated today
crisandrews