What problem does it solve? When a RAG MCP server fails to start, returns errors, ranks the wrong document first, or serves stale content, developers waste time guessing at root causes. This Skill provides a structured decision tree that isolates the fault before any code changes are made. ## Core Features & Use Cases - Symptom-based triage: A quick-reference table maps seven symptoms (not starting, errors, wrong top result, language gaps, low scores, build failures, stale index) to dedicated diagnostic sections. - Dual-stack coverage: Separate diagnostic paths for the Python server (sentence-transformers, Qdrant REST) and the .NET server (ONNX tokenizer, Qdrant gRPC on port 6334). - Concrete fixes: Each section pairs error messages with root causes and exact commands, such as checking Qdrant collection health, verifying venv paths in .vscode/mcp.json, and running incremental vs. force-full re-indexing. - Use Case: A developer queries in Polish and gets the wrong document at rank #1. The Skill walks them through an expansion test against multilingual-glossary.yaml to confirm a language gap, then routes them to the glossary-expansion workflow. ## Quick Start Ask the assistant to diagnose why the RAG MCP server returns low scores for a specific query and follow the decision tree it produces.