qdrant/skills brings together 33 skills for data, analytics and databases, DevOps and cloud. Start with the task descriptions below, then compare the individual skill's score, source files and license.
33 listed skills; recorded scores 70–84/100. 12 full reviews with separate installation details. Scores describe the saved source snapshot, using the Suede Skill Check.
Download the collection manifest: complete task descriptions, scores, license information, source revisions and install routes for all 33 listed skills. Use it to compare options or hand your selection to an agent.
Choose a skill for your task
Start with these 6 skills: the highest recorded score per category, then the highest remaining scores. The complete table below includes all 33 listings. Task descriptions come from the publisher; score explanations come from the saved report.
qdrant-edge 84/100 · B
Publisher's task description: Guides building on Qdrant Edge, the embedded in-process shard. Use when someone asks 'how to sync Edge with the server', 'keep a local shard in sync with Qdrant Cloud', 'BM25 or keyword search on Edge', 'hybrid search on Edge', 'embeddings on device', 'Edge snapshots', 'apply a partial snapshot', 'why is my Edge search empty after inserts', or is writing custom sync, BM25, or fusion code against qdrant-edge. Also use when deciding what Edge ships built-in versus what you must implement.
Score evidence: Full points for structural checks, recent maintenance and instruction depth. Largest point gaps: boundary clause (0/4); reference files (0/3).
See all score components for qdrant-edge
Structural checks
56 of 56
Description length
5 of 5
Boundary clause
0 of 4
Example request
3 of 3
Instruction depth
7 of 7
Reference files
0 of 3
Bundled scripts
0 of 2
Recent maintenance
9 of 9
Curated-list citations
4 of 7
Tool permissions declared
0 of 2
Compatibility declared
0 of 2
License: Apache-2.0 governs reuse and modification of these files.
Publisher's task description: Guides Qdrant monitoring and observability setup. Use when someone asks 'how to monitor Qdrant', 'what metrics to track', 'is Qdrant healthy', 'optimizer stuck', 'why is memory growing', 'requests are slow', 'set up alerts', 'cluster health check', or needs to set up Prometheus, Grafana, health checks, or log centralization. Also use when debugging production issues that require metric analysis.
Score evidence: Full points for structural checks, recent maintenance and description length. Largest point gaps: instruction depth (1/7); boundary clause (0/4).
See all score components for qdrant-monitoring
Structural checks
56 of 56
Description length
5 of 5
Boundary clause
0 of 4
Example request
3 of 3
Instruction depth
1 of 7
Reference files
0 of 3
Bundled scripts
0 of 2
Recent maintenance
9 of 9
Curated-list citations
4 of 7
Tool permissions declared
2 of 2
Compatibility declared
0 of 2
License: Apache-2.0 governs reuse and modification of these files.
Publisher's task description: Guides use of the Qdrant Migration Tool CLI to move vectors, metadata, and sparse embeddings from another vector database into Qdrant. Use when someone asks 'how do I migrate from Pinecone/Weaviate/Milvus/Elasticsearch/OpenSearch/pgvector/s3/Azure/Chroma/Redis/MongoDB/FAISS/Solr to Qdrant', 'move my vector database to Qdrant', 'is there a migration tool for Qdrant', 'my migration got interrupted, how do I resume it', 'migration is too slow', or 'collection wasn't created after migration'. Also use when picking migration batch size, deciding on `--net=host`, or verifying data after a migration.
Score evidence: Full points for structural checks, recent maintenance and instruction depth. Largest point gaps: boundary clause (0/4); reference files (0/3).
See all score components for qdrant-migration-tool
Structural checks
56 of 56
Description length
5 of 5
Boundary clause
0 of 4
Example request
3 of 3
Instruction depth
7 of 7
Reference files
0 of 3
Bundled scripts
0 of 2
Recent maintenance
9 of 9
Curated-list citations
4 of 7
Tool permissions declared
0 of 2
Compatibility declared
0 of 2
License: Apache-2.0 governs reuse and modification of these files.
Publisher's task description: Guides embedding model migration in Qdrant without downtime. Use when someone asks 'how to switch embedding models', 'how to migrate vectors', 'how to update to a new model', 'zero-downtime model change', 'how to re-embed my data', or 'can I use two models at once'. Also use when upgrading model dimensions, switching providers, or A/B testing models.
Score evidence: Full points for structural checks, recent maintenance and instruction depth. Largest point gaps: boundary clause (0/4); reference files (0/3).
See all score components for qdrant-model-migration
Structural checks
56 of 56
Description length
5 of 5
Boundary clause
0 of 4
Example request
3 of 3
Instruction depth
7 of 7
Reference files
0 of 3
Bundled scripts
0 of 2
Recent maintenance
9 of 9
Curated-list citations
4 of 7
Tool permissions declared
0 of 2
Compatibility declared
0 of 2
License: Apache-2.0 governs reuse and modification of these files.
Publisher's task description: Guides tenant isolation architecture in Qdrant for multi-tenant or multi-user applications. Use when someone asks 'how to isolate customer data', 'how to build multi-tenant search/RAG', 'how many collections should I create', 'how to partition tenants by payload', 'a customer's data legally has to stay in a certain country or region'. Also use when they describe a symptom: one customer's data is way bigger than the rest and slowing everyone down, or one tenant is hogging resources.
Score evidence: Full points for structural checks, recent maintenance and instruction depth. Largest point gaps: boundary clause (0/4); reference files (0/3).
See all score components for qdrant-multitenancy
Structural checks
56 of 56
Description length
5 of 5
Boundary clause
0 of 4
Example request
3 of 3
Instruction depth
7 of 7
Reference files
0 of 3
Bundled scripts
0 of 2
Recent maintenance
9 of 9
Curated-list citations
4 of 7
Tool permissions declared
0 of 2
Compatibility declared
0 of 2
License: Apache-2.0 governs reuse and modification of these files.
Publisher's task description: Sizes a Qdrant deployment before it is provisioned. Use when someone asks 'how much RAM do I need', 'how many nodes', 'how big should my cluster be', 'sizing', 'capacity planning', 'will N vectors fit', 'what instance type should I pick', or gives a vector count and dimensions and asks what to provision. Also use when an existing estimate needs checking before hardware or a cluster tier is bought.
Score evidence: Full points for structural checks, recent maintenance and instruction depth. Largest point gaps: boundary clause (0/4); reference files (0/3).
See all score components for qdrant-sizing
Structural checks
56 of 56
Description length
5 of 5
Boundary clause
0 of 4
Example request
3 of 3
Instruction depth
7 of 7
Reference files
0 of 3
Bundled scripts
0 of 2
Recent maintenance
9 of 9
Curated-list citations
4 of 7
Tool permissions declared
0 of 2
Compatibility declared
0 of 2
License: Apache-2.0 governs reuse and modification of these files.
Select one skill. Use the folder-specific command beside its description to start with the workflow you need. Skills with publisher-specific license terms link to that publisher's setup route.
Read the setup requirements. Check the source, license and any named tools or environment variables. Installing a SKILL.md folder supplies instructions to the agent; any external CLI, MCP server, account or service still needs its own setup.
Check the result. Open the installed SKILL.md and confirm that its name matches your selection. In Claude Code use the project's .claude/skills/ folder; in Codex use .agents/skills/. The skills CLI also supports other Agent Skills hosts.
Try one representative task. Supply the input files, expected output and success criteria. Compare the result with those criteria before adding more skills or running the workflow on live work.
Diagnoses, troubleshoots, and advises on Qdrant deployments by loading the latest official Qdrant skills live from skills.qdrant.tech, covering performance, scaling, search quality, and monitoring.
Guides choosing a Qdrant deployment type, such as Docker, Cloud, local mode, embedded, Qdrant EDGE, or self-hosted, including when lowest latency is needed.
Guides installing and running Qdrant Hybrid Cloud on your own Kubernetes cluster, covering storage, backups, the agent and operator, cluster exposure, and secret rotation.
Guides using the Qdrant Migration Tool CLI to move vectors, metadata, and sparse embeddings from other vector databases into Qdrant, including resuming interrupted runs.
Guides migrating to a new embedding model in Qdrant without downtime, including re-embedding data, changing model dimensions, switching providers, and A/B testing models.
Guides Qdrant monitoring and observability setup, including which metrics to track, Prometheus, Grafana, health checks, alerts, and log centralization.
Guides tenant isolation architecture in Qdrant for multi-tenant applications, including partitioning tenants by payload, how many collections to create, and data residency.
Guides Qdrant scaling decisions such as node count, sharding, vertical versus horizontal scaling, throughput, tail latency, and retention windows for expiring old vectors.
Sizes a Qdrant deployment before provisioning, estimating RAM, node count, and instance type from vector count and dimensions, or checking an existing estimate.
Covers upgrading Qdrant server and SDKs without interrupting availability or losing data integrity, including rolling upgrades, version compatibility, and pre-upgrade checks.
Navigation hub linking sub-skills for proactive Qdrant tuning: search speed, indexing performance, and memory usage optimization. Use when planning…Get badges
Choose the numeric badge, the letter badge, or both. Each links to this skill’s Suede AI listing; either valid linked badge can qualify for the feature offer.
For data, analytics and databases, compare task fit first, then the score components, installation requirements and license. Two skills with the same score can earn their points in different ways; use their reports to see the difference.
This general badge links to the repository listing. For the two quality badges and feature offer, choose Get badges beside a skill below. Each skill keeps its own score and grade.
Markdown
[](https://suedeai.directory/qdrant/skills/)
HTML
<a href="https://suedeai.directory/qdrant/skills/"><img src="https://suedeai.directory/qdrant/skills/badge.svg" alt="Suede AI Skills Directory: listed" height="20"></a>
Limited-time feature offer: Display either quality badge in your repository or skill README, linked to your listing, then request verification. Suede AI checks the rendered README at a recorded commit. Eligible skills scoring 80–99 with a verified badge can receive a featured placement while the offer is open. Request badge verification.