Menú
Set up Qdrant for RAG with collections, payload filtering, and batch ingestion.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use this skill when building, debugging, or improving Retrieval-Augmented Generation systems, including chunking, vector database selection, hybrid search, reranking, multimodal RAG, code documentation RAG, retrieval latency, and production RAG architecture.
Chunk nested documents into parent-child levels so retrieval can move from broad sections to fine-grained passages.
Use semantic boundaries and embedding similarity to chunk text for higher-relevance retrieval.
Route RAG chunking decisions across semantic, hierarchical, sliding-window, contextual-header, and framework-selection strategies.
Use overlapping windows to preserve context across chunk boundaries while controlling retrieval size.
Reduce retrieval latency with caching, batching, and index-level optimization.
| name | qdrant-setup-rag |
| title | Qdrant Setup for RAG |
| description | Set up Qdrant for RAG with collections, payload filtering, and batch ingestion. |
| allowed-tools | ["Read","Grep","Glob","Bash"] |
| category | vector-databases |
| tags | ["qdrant","setup","ingestion","filtering"] |
Qdrant is an open-source vector similarity search engine designed for high-performance RAG applications. This skill covers setting up Qdrant, creating collections with proper indexing, implementing filtering with metadata, and managing document ingestion.
Setting up a vector database for RAG involves multiple considerations:
Set up Qdrant locally or connect to a cloud instance.
Why: Docker provides an isolated environment with persistence, while the cloud option offers managed scalability.
Configure collection parameters based on your embedding model and use case.
Why: Proper configuration at creation time avoids expensive re-indexing later. COSINE is default for normalized embeddings.
Structure your payloads (metadata) for effective filtering.
Why: Well-structured metadata enables powerful filtering queries and helps organize retrieval results.
Upload documents with their embeddings and metadata.
Why: Batch operations significantly improve ingestion performance compared to individual uploads.
Query with metadata filters for targeted retrieval.
Why: Filtering enables domain-specific retrieval (e.g., "search only in documentation" or "search only code examples").
Set up monitoring for collection health.
Why: Monitoring helps identify performance issues and scaling needs before they impact users.
See the Qdrant documentation, Qdrant filtering, Qdrant Python client, and the HNSW paper for production-ready setup patterns.
