Rust-powered vector database for production RAG with hybrid search and distributed scaling.
Works with
Supports dense, sparse, and multi-vector storage per point with four distance metrics (COSINE, EUCLID, DOT, MANHATTAN) and HNSW indexing for fast nearest-neighbor search
Rich filtering during search across any payload field, with optional payload indexing for performance and support for complex boolean queries
Quantization options (scalar, product, binary) and on-disk storage for memory effici
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionqdrant-vector-searchExecute the skills CLI command in your project's root directory to begin installation:
Fetches qdrant-vector-search from davila7/claude-code-templates and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate qdrant-vector-search. Access via /qdrant-vector-search in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
High-performance vector database written in Rust for production RAG and semantic search.
Use Qdrant when:
Key features:
Use alternatives instead:
# Python client
pip install qdrant-client
# Docker (recommended for development)
docker run -p 6333:6333 -p 6334:6334 qdrant/qdrant
# Docker with persistent storage
docker run -p 6333:6333 -p 6334:6334 \
-v $(pwd)/qdrant_storage:/qdrant/storage \
qdrant/qdrant
from qdrant_client import QdrantClient
from qdrant_client.models import Distance, VectorParams, PointStruct
# Connect to Qdrant
client = QdrantClient(host="localhost", port=6333)
# Create collection
client.create_collection(
collection_name="documents",
vectors_config=VectorParams(size=384, distance=Distance.COSINE)
)
# Insert vectors with payload
client.upsert(
collection_name="documents",
points=[
PointStruct(
id=1,
vector=[0.1, 0.2, ...], # 384-dim vector
payload={"title": "Doc 1", "category": "tech"}
),
PointStruct(
id=2,
vector=[0.3, 0.4, ...],
payload={"title": "Doc 2", "category": "science"}
)
]
)
# Search with filtering
results = client.search(
collection_name="documents",
query_vector=[0.15, 0.25, ...],
query_filter={
"must": [{"key": "category", "match": {"value": "tech"}}]
},
limit=10
)
for point in results:
print(f"ID: {point.id}, Score: {point.score}, Payload: {point.payload}")
from qdrant_client.models import PointStruct
# Point = ID + Vector(s) + Payload
point = PointStruct(
id=123, # Integer or UUID string
vector=[0.1, 0.2, 0.3, ...], # Dense vector
payload={ # Arbitrary JSON metadata
"title": "Document title",
"category": "tech",
"timestamp": 1699900000,
"tags": ["python", "ml"]
}
)
# Batch upsert (recommended)
client.upsert(
collection_name="documents",
points=[point1, point2, point3],
wait=True # Wait for indexing
)
from qdrant_client.models import VectorParams, Distance, HnswConfigDiff
# Create with HNSW configuration
client.create_collection(
collection_name="documents",
vectors_config=VectorParams(
size=384, # Vector dimensions
distance=Distance.COSINE # COSINE, EUCLID, DOT, MANHATTAN
),
hnsw_config=HnswConfigDiff(
m=16, # Connections per node (default 16)
ef_construct=100, # Build-time accuracy (default 100)
full_scan_threshold=10000 # Switch to brute force below this
),
on_disk_payload=True # Store payload on disk
)
# Collection info
info = client.get_collection("documents")
print(f"Points: {info.points_count}, Vectors: {info.vectors_count}")
| Metric | Use Case | Range |
|---|---|---|
COSINE |
Text embeddings, normalized vectors | 0 to 2 |
EUCLID |
Spatial data, image features | 0 to ∞ |
DOT |
Recommendations, unnormalized | -∞ to ∞ |
MANHATTAN |
Sparse features, discrete data | 0 to ∞ |
# Simple nearest neighbor search
results = client.search(
collection_name="documents",
query_vector=[0.1, 0.2, ...],
limit=10,
with_payload=True,
with_vectors=False # Don't return vectors (faster)
)
from qdrant_client.models import Filter, FieldCondition, MatchValue, Range
# Complex filtering
results = client.search(
collection_name="documents",
query_vector=query_embedding,
query_filter=Filter(
must=[
FieldCondition(key="category", match=MatchValue(value="tech")),
FieldCondition(key="timestamp", range=Range(gte=1699000000))
],
must_not=[
FieldCondition(keyPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
qdrant-vector-search reduced setup friction for our internal harness; good balance of opinion and flexibility.
qdrant-vector-search fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
qdrant-vector-search has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend qdrant-vector-search for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in qdrant-vector-search — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
qdrant-vector-search has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added qdrant-vector-search from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
qdrant-vector-search reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: qdrant-vector-search is focused, and the summary matches what you get after install.
I recommend qdrant-vector-search for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 61