/plugadvpl:doctor

Diagnose plugadvpl environment and index issues before reindexing.

Updated Aug 27, 2026

Search Tags:#troubleshooting #sqlite #diagnostics #encoding #index #fts5 #plugadvpl

Ready to run

npx skills add https://github.com/JoniPraia/plugadvpl --skill plugadvpl-doctor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: /plugadvpl:doctor
Source: https://github.com/JoniPraia/plugadvpl/tree/main/skills/doctor
Command: npx skills add https://github.com/JoniPraia/plugadvpl --skill plugadvpl-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly identify why the plugadvpl index is failing or behaving incorrectly, including missing files, broken SQLite FTS5 support, outdated schema, and encoding/locale issues.

Core Features & Use Cases

Environment verification: checks uv, Python/venv, platform details, and available plugadvpl version alignment.
Index health checks: validates the presence and accessibility of .plugadvpl/index.db, confirms expected migrations/schema version, and verifies that lookups are loaded (hash matches).
Operational readiness: checks SQLite FTS5 capability, write permissions for .plugadvpl/, disk space availability, and encoding/locale expectations (CP1252 vs UTF-8) to prevent corrupted PRO/PRW handling.

Quick Start

Run /plugadvpl:doctor --quiet to get a compact list of what is failing in your setup.

Frequently Asked Questions about /plugadvpl:doctor

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

FAQPage Schema

Why is my plugadvpl index database missing or failing FTS5 queries?▼

Run plugadvpl diagnostics to identify missing `.plugadvpl/index.db` files, broken SQLite FTS5 support, outdated schema versions, or write permission issues in the `.plugadvpl/` directory.

How do I check if my environment is ready for PRO/PRW source intelligence indexing?▼

Run `uvx plugadvpl doctor` to verify environment readiness for PRO/PRW source intelligence indexing. It checks uv availability, platform details, disk space, and encoding/locale expectations to prevent corrupted source handling.

What causes corrupted PRO/PRW file handling during plugadvpl indexing?▼

Corrupted PRO/PRW file handling during indexing is typically caused by problematic locale and encoding conditions, specifically CP1252 versus UTF-8 mismatches. Diagnostics check these encoding expectations before reindexing.

How do I quickly troubleshoot plugadvpl index problems without verbose output?▼

Quickly troubleshoot plugadvpl index problems by running `uvx plugadvpl doctor --quiet`. This compact mode returns a concise list of failing setup checks, including FTS5 capability and lookup hash integrity.

Does plugadvpl doctor check for stale database migrations and lookup hash integrity?▼

Yes, plugadvpl doctor verifies expected schema versions to detect stale migrations and confirms that lookups are properly loaded by checking if hash matches, ensuring index database integrity.

What are common limitations when diagnosing plugadvpl environment issues?▼

Diagnostics limitations include failing to detect issues if uv is unavailable, or if the SQLite FTS5 extension is missing. The tool cannot fix corrupted indexes automatically; it only diagnoses problems before reindexing.