ctx-doctor
mksglu/context-mode
Diagnose context-mode setup issues with runtime, hooks, FTS5, and plugin checks.
What is ctx-doctor?
ctx-doctor runs server-side diagnostics to verify your context-mode installation health. Use it when you suspect configuration problems, missing dependencies, or version mismatches affecting your context-mode environment.
- Checks runtime availability and compatibility
- Verifies hook registration and FTS5 support
- Validates plugin registration status
- Compares npm and marketplace package versions
- Returns plain-text status report with [OK]/[FAIL]/[WARN] prefixes
- Provides fallback CLI execution if MCP tool unavailable
How to install ctx-doctor
npx skills add https://github.com/mksglu/context-mode --skill ctx-doctorHow to use ctx-doctor
- 1.Invoke the skill with /context-mode:ctx-doctor or call the ctx_doctor MCP tool
- 2.Review the returned status report with [OK], [FAIL], and [WARN] indicators
- 3.Address any [FAIL] items by checking the referenced component (runtime, hooks, FTS5, plugins, or versions)
- 4.If MCP tool fails, the skill automatically falls back to CLI execution via node CLI.bundle.mjs or build/cli.js
Use cases
- Troubleshoot context-mode startup failures or unexpected behavior
- Verify all dependencies are correctly installed before running workflows
- Check for version conflicts between local and marketplace packages
- Validate FTS5 and hook support in your environment
- Debug plugin registration issues
- context-mode users troubleshooting setup problems
- DevOps engineers verifying deployment configurations
- Developers integrating context-mode into CI/CD pipelines
- System administrators managing context-mode installations
ctx-doctor FAQ
[OK] indicates a passing check, [FAIL] indicates a critical failure requiring attention, and [WARN] indicates a potential issue that may not block operation.
Network issues, server unavailability, or misconfigured MCP setup. The skill automatically falls back to direct CLI execution.
Compare npm version (local) with marketplace version (published). Mismatches may indicate stale installations or pending updates.
Yes—if you have the plugin root, you can run `node <PLUGIN_ROOT>/cli.bundle.mjs doctor` or `node <PLUGIN_ROOT>/build/cli.js doctor` directly.
Full instructions (SKILL.md)
Source of truth, from mksglu/context-mode.
name: ctx-doctor description: | Run context-mode diagnostics. Checks runtimes, hooks, FTS5, plugin registration, npm and marketplace versions. Trigger: /context-mode:ctx-doctor user-invocable: true
Context Mode Doctor
Run diagnostics and display results directly in the conversation.
Instructions
- Call the
ctx_doctorMCP tool directly. It runs all checks server-side and returns a plain-text status report. - Display the results verbatim — they are already formatted with plain-text status prefixes:
[OK]PASS,[FAIL]FAIL,[WARN]WARN. Renderer-safe (no markdown task-list syntax) for cross-client compatibility (e.g., Z.ai GLM). - Fallback (only if MCP tool call fails): Derive the plugin root from this skill's base directory (go up 2 levels — remove
/skills/ctx-doctor), then run with Bash:
Re-display results verbatim with the sameCLI="<PLUGIN_ROOT>/cli.bundle.mjs"; [ ! -f "$CLI" ] && CLI="<PLUGIN_ROOT>/build/cli.js"; node "$CLI" doctor[OK]/[FAIL]/[WARN]prefixes.
Related skills
More from mksglu/context-mode and the wider catalog.


