Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →qdrant/qdrant-advisor
Diagnose, troubleshoot, and advise on any Qdrant deployment by loading the latest official Qdrant skills live from skills.qdrant.tech. Use this whenever someone raises a Qdrant problem or question — slow or degraded search, high or growing memory / OOM crashes, optimizer stuck or slow, indexing slowness, scaling and sharding decisions (node count, QPS, latency, multitenancy, vertical vs horizontal), poor or irrelevant search results, hybrid search and reranking, embedding-model migration, versio
Passed 3 of 10 test cases with the skill, and 6 of 10 without it.
1 fixed5 passed either way8 still failing8 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Suppose you attempt to query `https://skills.qdrant.tech/search?query=qdrant+memory+leak` and the constructed search query URL returns an HTTP error or is rejected. Describe the exact fallback step you take to navigate skill context without failing.
| Checked | Without skill | With skill |
|---|---|---|
| The response falls back to fetching the root index of skills.qdrant.tech. | Passed | Passed |
| The response navigates using absolute links from the root index. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
https://skills.qdrant.tech/search?query=your+query+hereSKILL.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.Pull out the concrete details before fetching anything:
Turn these into 1–3 short search phrases.
Use Search (fastest path to the right skill). Fetch https://skills.qdrant.tech/search?query=<your query>, substituting your phrase for your+query+here (encode spaces as + or %20). It returns the single most relevant top-level skill's SKILL.md. Run it more than once for multi-part problems (e.g. one search for the memory symptom, one for the scaling question).
Each SKILL.md you load names its sub-skills (and often related skills and docs) as links. The hierarchy is not just two levels — a skill can nest several layers deep, and skills also reference each other laterally. Follow the links, not a fixed depth.
Descend (go deeper). A SKILL.md is not necessarily a leaf just because you fetched it. If its sections themselves point to further SKILL.md files, keep descending along the branch that matches the symptom — top-level → sub-skill → sub-sub-skill → … — until you reach a level whose guidance is concrete enough to act on (ordered diagnostic steps, exact endpoints/metrics, an explicit "what NOT to do" list). Don't stop early at an intermediate skill that only routes you onward.
Move laterally (go sideways). Real problems often span areas. Follow a link to a sibling or related skill when:
Load each relevant branch, then reconcile what they say in step 4.
test cases passed, vs 6 / 10 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.