Help us improve
Share bugs, ideas, or general feedback.
Runs health checks for context-optimizer plugin: verifies versions, hooks, data dir, model config, Node version, and reports fixes. Use via /cco-doctor when plugin issues arise.
npx claudepluginhub egorfedorov/claude-context-optimizerHow this skill is triggered — by the user, by Claude, or both
Slash command
/claude-context-optimizer:cco-doctorThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
When the user runs `/cco-doctor` or reports the plugin "isn't working", run a quick health check.
Runs context-mode diagnostics checking runtimes, hooks, FTS5, plugin registration, npm and marketplace versions. Invoke via /context-mode:ctx-doctor for plugin troubleshooting.
Runs health diagnostics on OrchestKit installation, validating plugins, skills, agents, hooks, permissions, schemas, coordination, memory, MCP status, and Claude Code version. Use for troubleshooting plugin issues.
Audits .claude/ structure, naming, hooks, and plugin versions. Runs hygiene and sync checks, outputs health report with fix commands.
Share bugs, ideas, or general feedback.
When the user runs /cco-doctor or reports the plugin "isn't working", run a quick health check.
Standard run (fast — under 1s):
node ${CLAUDE_PLUGIN_ROOT}/src/doctor.js
With test suite (slower — runs all unit tests):
node ${CLAUDE_PLUGIN_ROOT}/src/doctor.js --tests
package.json existplugin.json and package.json)hooks.json is valid JSON with all expected event typessrc/~/.claude-context-optimizer/ is writablepatterns.json size is reasonableTranslate the doctor output into plain language. If anything is fail, walk the user through the fix:
npm run sync-version/cco-clean/cco-budget set <smaller> or pick a 1M-context modelIf everything is pass, confirm "плагин в порядке, текущая версия Х.Y.Z" and stop.