How do I trigger the diagnostics?

Use the trigger /context-mode:ctx-doctor. The skill then calls the ctx_doctor MCP tool and displays the report.

What do the status prefixes mean?

The report uses [OK] for PASS, [FAIL] for FAIL, and [WARN] for WARN. Results are shown verbatim in plain text.

What happens if the MCP tool call fails?

The skill falls back to running the plugin's command-line doctor. It derives the plugin root from the skill's base directory and runs the CLI doctor command.

Context Mode Doctor

SkillDev tools

The ctx-doctor skill runs context-mode diagnostics for the context-mode plugin. It calls the ctx_doctor MCP tool, which checks runtimes, hooks, FTS5, plugin registration, and npm and marketplace versions, then shows a plain-text report with OK, FAIL, and WARN statuses. If the tool call fails, the skill falls back to running the plugin's command-line doctor.

Connect your AI Use it in a pipeline

Then ask your AI: use the Context Mode Doctor skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.

No other account needed.

Have the context-mode plugin installed and registered so its MCP tool is available.

What your AI can do with it

Run the ctx_doctor MCP tool to perform all context-mode checks server-side
Check runtimes, hooks, FTS5, plugin registration, and npm and marketplace versions
Display a plain-text report with [OK], [FAIL], and [WARN] status prefixes
Render results safely across clients without markdown task-list syntax
Fall back to the plugin's command-line doctor if the MCP tool call fails

Getting started

Have the context-mode plugin installed and registered so its MCP tool is available.
Invoke the skill with the trigger /context-mode:ctx-doctor.
Read the plain-text status report shown in the conversation.
If the MCP tool call fails, let the skill derive the plugin root and run the command-line doctor as a fallback.

What this skill tells your AI

The instructions your AI receives, as published by mksglu/context-mode in skills/ctx-doctor/SKILL.md and read by Ahel’s review.

Run diagnostics and display results directly in the conversation.

Instructions

Call the ctx_doctor MCP 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:
```
CLI="<PLUGIN_ROOT>/cli.bundle.mjs"; [ ! -f "$CLI" ] && CLI="<PLUGIN_ROOT>/build/cli.js"; node "$CLI" doctor
```
Re-display results verbatim with the same [OK]/[FAIL]/[WARN] prefixes.

Signals

GitHub stars: 26k
Forks: 2k
Last commit: Oct 2026

Questions

What does the ctx-doctor skill check?: It checks runtimes, hooks, FTS5, plugin registration, and npm and marketplace versions through the ctx_doctor MCP tool.
How do I trigger the diagnostics?: Use the trigger /context-mode:ctx-doctor. The skill then calls the ctx_doctor MCP tool and displays the report.
What do the status prefixes mean?: The report uses [OK] for PASS, [FAIL] for FAIL, and [WARN] for WARN. Results are shown verbatim in plain text.
What happens if the MCP tool call fails?: The skill falls back to running the plugin's command-line doctor. It derives the plugin root from the skill's base directory and runs the CLI doctor command.

Advanced

Item type: skill
Key: ctx-doctor
Source: github.com/mksglu/context-mode

github.com/mksglu/context-mode