ctx-doctor

Diagnose context-mode components and output a markdown checklist.

3|1|Updated Aug 10, 2025
One-click install
npx skills add https://github.com/hckhanh/pulumi-any-terraform --skill ctx-doctor-hckhanh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ctx-doctor
Source: https://github.com/hckhanh/pulumi-any-terraform/tree/main/.agents/skills/ctx-doctor
Command: npx skills add https://github.com/hckhanh/pulumi-any-terraform --skill ctx-doctor-hckhanh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill tackles the frustration of debugging context-mode setups by automating checks for runtimes, hooks, FTS5, plugin registration, and version compatibility, preventing cryptic errors in AI plugin environments.

Core Features & Use Cases

  • Comprehensive Diagnostics: Runs server-side checks via MCP tool for all key components, displaying results as a formatted checklist.
  • Fallback Execution: If the tool fails, invokes a local CLI script to perform the same diagnostics.
  • Use Case: When your AI conversation agent starts behaving unexpectedly due to plugin misconfigurations, activate this Skill to quickly identify and resolve issues like outdated npm versions or unregistered hooks.

Quick Start

Trigger the context mode doctor to run full diagnostics on the current setup.

Frequently Asked Questions about ctx-doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose context mode issues in AI plugin environments?

To diagnose context mode issues, run automated server-side checks on runtimes, hooks, FTS5, plugin registration, and version compatibility to identify misconfigurations. Results are displayed as a formatted markdown checklist to quickly pinpoint setup failures.

Why does my AI conversation agent behave unexpectedly due to plugin misconfigurations?

Unexpected agent behavior often stems from plugin misconfigurations like unregistered hooks or outdated npm marketplace versions. Running context mode diagnostics isolates these specific environment failures, preventing cryptic errors by verifying overall setup integrity.

What is the best way to verify FTS5 and hook registration in conversational systems?

The best way to verify FTS5 and hook registration is to trigger a diagnostic tool that checks these components server-side. It outputs a markdown checklist detailing the status of each plugin environment component for immediate review.

Does context mode troubleshooting work without a direct MCP tool connection?

Yes, context mode troubleshooting works without a direct MCP tool connection by utilizing a fallback execution method. If the primary server-side tool call fails, a local CLI script runs via bash to perform the same comprehensive diagnostics.