OrchestKit doctor for health diagnostics. Use when running checks on plugin health, diagnosing problems, or troubleshooting issues.
Diagnoses OrchestKit plugin health across 12 categories including skills, agents, hooks, and memory systems.
/plugin marketplace add yonatangross/orchestkit/plugin install orkl@orchestkitThis skill is limited to using the following tools:
references/agents-validation.mdreferences/health-check-outputs.mdreferences/hook-validation.mdreferences/memory-health.mdreferences/permission-rules.mdreferences/remediation-guide.mdreferences/report-format.mdreferences/schema-validation.mdreferences/skills-validation.mdreferences/version-compatibility.mdrules/_sections.mdrules/diagnostic-checks.mdrules/mcp-status-checks.mdscripts/check-plugin-health.shThe /ork:doctor command performs comprehensive health checks on your OrchestKit installation. It auto-detects installed plugins and validates 12 categories:
npm run build/ork:doctor # Standard health check
/ork:doctor -v # Verbose output
/ork:doctor --json # Machine-readable for CI
| Flag | Description |
|---|---|
-v, --verbose | Detailed output per check |
--json | JSON output for CI integration |
--category=X | Run only specific category |
Detailed check procedures: See rules/diagnostic-checks.md for bash commands and validation logic per category.
MCP-specific checks: See rules/mcp-status-checks.md for credential validation and misconfiguration detection.
Output examples: See references/health-check-outputs.md for sample output per category.
| Category | What It Checks | Reference |
|---|---|---|
| 0. Installed Plugins | Auto-detects orkl or ork, counts skills/agents | diagnostic-checks |
| 1. Skills | Frontmatter, context field, token budget, links | skills-validation |
| 2. Agents | Frontmatter, model, skill refs, tool refs | agents-validation |
| 3. Hooks | hooks.json schema, bundles, async patterns | hook-validation |
| Category | What It Checks | Reference |
|---|---|---|
| 4. Memory | .claude/memory/ exists, decisions.jsonl integrity, queue depth | memory-health |
| 5. Build | plugins/ sync with src/, manifest counts, orphans | diagnostic-checks |
| Category | What It Checks |
|---|---|
| 6. Permission Rules | Unreachable rules detection (CC 2.1.3) |
| 7. Schema Compliance | JSON files against schemas |
| 8. Coordination | Multi-worktree lock health, stale locks |
| 9. Context Budget | Token usage against budget |
| Category | What It Checks | Reference |
|---|---|---|
| 10. CC Version | Runtime version against minimum required | version-compatibility |
| 11. External Deps | Optional tools (agent-browser) | diagnostic-checks |
| 12. MCP Status | Enabled/disabled state, credential checks | mcp-status-checks |
See references/report-format.md for ASCII report templates (ork and orkl), JSON CI output schema, and exit codes.
See references/remediation-guide.md for the full results interpretation table and troubleshooting steps for common failures (skills validation, build sync, memory).
ork:configure - Configure plugin settingsork:quality-gates - CI/CD integrationsecurity-scanning - Comprehensive auditsSearch, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.