qdrant/skills
Navigation hub linking sub-skills for proactive Qdrant tuning: search speed, indexing performance, and memory usage optimization.
npx skills add qdrant/skills --skill qdrant-performance-optimization
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…
3.3M installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsPrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…
568.3K installsOther skills from qdrant/skills · top by installs.
npx skills add qdrant/skills
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Alternate registries and mirrors of this skill.
npx skills add https://github.com/github/awesome-copilot
main
Parsed from SKILL.md frontmatter.
Read, Grep, GlobFiles included with this skill beyond the listing page.
SKILL.md
1,823 B
SUMMARY.md
356 B
Route first, then answer. Match the user's symptom in the table, Read that file, and answer from it. Do not answer from this page alone: it contains routing only, not the guidance. If two rows match, read both.
| The user says | Read |
|---|---|
| Filtered queries much slower than unfiltered | search-speed-optimization/SKILL.md |
| Low QPS, cannot handle the query load | search-speed-optimization/SKILL.md |
| Individual queries take too long to return | search-speed-optimization/SKILL.md |
| Index build or HNSW build takes too long, vector upload is slow | indexing-performance-optimization/SKILL.md |
| Collection stays yellow, optimizer stuck or runs for a long time | indexing-performance-optimization/SKILL.md |
| Bulk upsert of vectors is slow | indexing-performance-optimization/SKILL.md |
| RAM usage too high, out-of-memory crashes | memory-usage-optimization/SKILL.md |
| Want to fit a larger dataset on the same hardware | memory-usage-optimization/SKILL.md |
| Reducing cost by moving data to disk | memory-usage-optimization/SKILL.md |
Latency and throughput pull opposite ways on segment count. For latency, increase segments toward the CPU core count (defaultsegmentnumber: 16). For throughput, use fewer and larger segments (defaultsegmentnumber: 2). Applying the wrong direction makes the reported problem worse.