ctx-doctor

Diagnose context-mode plugin runtime, integration, and version problems.

2|Updated May 5, 2026
One-click install
npx skills add https://github.com/OrestesK/pi --skill ctx-doctor-orestesk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ctx-doctor
Source: https://github.com/OrestesK/pi/tree/main/packages/context-mode/skills/ctx-doctor
Command: npx skills add https://github.com/OrestesK/pi --skill ctx-doctor-orestesk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies configuration, runtime, hook, search, registration, and version issues that can prevent the context-mode plugin from working correctly.

Core Features & Use Cases

  • Runtime Diagnostics: Check required runtimes, hooks, and FTS5 support.
  • Plugin Validation: Verify plugin registration and operational configuration.
  • Version Checks: Compare installed npm and marketplace versions to help identify outdated components.
  • Use Case: Run the diagnostics when context-mode tools are unavailable or behaving unexpectedly, then use the reported status markers to guide troubleshooting.

Quick Start

Ask the context-mode doctor to run all diagnostics and display the complete status report.

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 plugin runtime issues?

Diagnosing context-mode plugin runtime issues involves running a diagnostic tool that checks required runtimes, validates hooks, and verifies FTS5 support to generate a status report for troubleshooting.

Why does my context-mode plugin search stop working unexpectedly?

Search functionality in the context-mode plugin may fail unexpectedly due to missing FTS5 support, failed hook validation, or incorrect plugin registration, which runtime diagnostics are designed to identify and report.

How do I check if my context-mode npm package versions are outdated?

To check if context-mode npm package versions are outdated, run diagnostics that compare installed npm versions against marketplace versions to identify outdated components and resolve integration problems.

Do I need the context-mode MCP diagnostic tool to run health checks?

You do not strictly need the context-mode MCP diagnostic tool to run health checks, as the plugin supports a local Node.js CLI fallback to perform runtime diagnostics and validate operational configuration.

What is the best way to troubleshoot context-mode plugin registration problems?

The best way to troubleshoot context-mode plugin registration problems is to execute a full diagnostic check that verifies plugin registration and operational configuration to pinpoint the exact failure.

Context-mode diagnostics not working, what are the limitations?

Limitations of context-mode diagnostics include the requirement for access to either the context-mode MCP diagnostic tool or the plugin's local Node.js CLI fallback, without which runtime checks cannot execute.