mcpField
Q
qdrant-search-quality

qdrant-search-quality

github.com/qdrantData & databases2651.8k installsUpdated 2d ago
Repository

About qdrant-search-quality

A routing skill for diagnosing Qdrant search-quality problems. It maps symptoms to the relevant guidance files, covering topics such as recall, embeddings, hybrid search, reranking, and relevance feedback.

Key features

  1. 01Routes symptoms to guidance files
  2. 02Covers recall and precision issues
  3. 03Directs embedding-quality investigations
  4. 04Covers hybrid search strategies
  5. 05Includes reranking and relevance feedback

Use cases

  1. 01Finding guidance for irrelevant results
  2. 02Investigating missing search matches
  3. 03Choosing an approach to hybrid search
  4. 04Improving result diversity or relevance

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/qdrant/skills --skill qdrant-search-quality

After installing, type/qdrant-search-qualityin Claude Code to confirm it loaded.

Details

From the project README

Qdrant Search Quality

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 saysRead
Search results are bad or irrelevant, wrong results, missing expected matchesdiagnosis/SKILL.md
Low recall, expected results are missingdiagnosis/SKILL.md
Low precision, too many wrong matchesdiagnosis/SKILL.md
Which embedding model to use, quality dropped after quantization, model change, or data growthdiagnosis/SKILL.md
Not sure if the model, the data, or Qdrant is at faultdiagnosis/SKILL.md
Want to measure recall, build a golden set, ground truth dataset, recall@kdiagnosis/SKILL.md
Is my improvement real, statistically significant, fine-tune the embedding modeldiagnosis/SKILL.md
Need to combine keyword and semantic search, hybrid search, sparse + dense, fusion / RRF, prefetchsearch-strategies/hybrid-search/SKILL.md
Should I rerank, results too similar, need diversity, MMR, recommendation/discovery APIsearch-strategies/SKILL.md
Improving results with relevance feedback or user clicks, cheaper alternative to rerankingsearch-strategies/relevance-feedback/SKILL.md

Most quality issues come from the embedding model or the data, not from Qdrant's configuration — splitting chunks mid-sentence alone can drop quality 30-40%. Rule that out with exact search before tuning any Qdrant parameter: Search API

Comments

Markdown supported