qdrant-advisor

# Qdrant Troubleshooting & Advisory ## Core principle Do not answer Qdrant questions from memory. Qdrant evolves quickly (new endpoints, metrics, defaults, and deployment patterns land often), and the authoritative, current guidance lives at `skills.qdrant.tech` as a hierarchy of agent skills. Your job is to **load the relevant skill context live, then ground your diagnosis in it** — loading only the branch that matches the problem, never the whole tree. You are *consuming* these skills as context. You are **not** installing them and nothing needs to be installed. ## The knowledge source - **Search**: `https://skills.qdrant.tech/search?query=your+query+here` - The structure is **hierarchical**: top-level skill `SKILL.md` → sub-skill `SKILL.md` → linked documentation pages. Each level narrows scope. Traverse it depth-first, following only the branch(es) that match the symptom. ## Workflow ### 1. Frame the problem Pull out the concrete details before fetching anything: - The **symptom(s)** in the user's words (e.g. "memory keeps climbing", "queries got slow after a bulk upload", "results are irrelevant"). - The **deployment type** (local, Docker, self-hosted, Cloud, embedded) and **version**, if known. - **What changed** recently (upgrade, new index, traffic spike, model swap). Turn these into 1–3 short search phrases. ### 2. Find the right skill(s) **Use Search (fastest path to the right skill).** Fetch `https://skills.qdrant.tech/search?query=<your query>`, substit...