Stats
Actions
Tags
Verifies plugin installation health: checks versions, hooks, data directory, model config, and reports issues. Run via /cco-doctor or when plugin malfunctions.
How 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.
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 model (e.g. opus-4.8)If everything is pass, confirm "плагин в порядке, текущая версия Х.Y.Z" and stop.
npx claudepluginhub egorfedorov/claude-context-optimizerRuns context-mode diagnostics checking runtimes, hooks, FTS5, plugin registration, npm and marketplace versions. Displays results with [OK]/[FAIL]/[WARN] status prefixes.
Runs health checks on a learning-loop installation, presents issues with severity, and offers per-fix remediation with auto-runnable or manual options. Re-runs each check after fixing to confirm resolution.
Runs comprehensive diagnostics on Claude Code environment: plugins, settings, hooks, MCP servers. Identifies issues, supports --fix and --verbose.