Agent Skills

Qdrant ships a set of agent skills: structured knowledge files that help your AI coding assistant think like a solutions architect, not just retrieve documentation. Skills are hosted at skills.qdrant.tech. Pass the URL of a skill to your agent and it will use it immediately, no installation required.

Using skills by URL keeps your agent’s context focused. Rather than loading all skills upfront, the agent fetches only the skill relevant to your current problem. If you prefer to have skills available offline or without passing URLs manually, you can install them locally in your agent. Refer to this README for instructions.

Philosophy

Skills are not a second copy of the documentation. They act as a navigation and decision layer, helping an agent determine which docs apply, when a feature is the right choice, and what pitfalls to avoid.

Documentation answers “how?” Skills answer “when?”, “why?”, and “what should I check first?”

For example, the docs explain how to enable scalar quantization. A skill tells you whether you should, what to check before you do, and what breaks if you get it wrong.

This is the knowledge that comes from seeing the same production problems many times. It does not fit into product documentation because it is not feature-shaped. It’s diagnostic, situational, and organized by symptoms, not by feature names.

The structure is deliberately problem-oriented and named by symptoms. Each entry opens with a trigger condition so the agent knows when the section applies, followed by imperative steps with direct links to the relevant documentation. The highest-value content is often the “What Not to Do” sections: mistakes that sound reasonable, but are not.

Skills Are Hierarchical

Skills are organized in a hierarchy. Each top-level skill (or hub skill) covers a domain and branches into sub-skills (or leaf skills) for more specific scenarios.

For example, qdrant-search-quality branches into:

  • Diagnosis and Tuning: isolating the source of quality issues, establishing labeled baselines, tuning HNSW parameters, and choosing the right embedding model.
  • Search Strategies: hybrid search, reranking, relevance feedback, and exploration APIs.

This structure helps agents move to the right level of specificity without loading irrelevant context. Explore the full hierarchy and search across all skills at skills.qdrant.tech.

Available Hub Skills

SkillUse for
qdrant-clients-sdkSDK setup and code examples across Python, TypeScript, Rust, Go, .NET, Java
qdrant-scalingData volume, QPS targets, latency budgets, horizontal vs. vertical decisions
qdrant-performance-optimizationSearch speed, memory pressure, indexing bottlenecks
qdrant-search-qualityBad results, low recall, irrelevant matches, hybrid search trade-offs
qdrant-monitoringMetrics, health checks, optimizer issues, cluster debugging
qdrant-deployment-optionsChoosing between local, Docker, self-hosted, Cloud, and embedded
qdrant-model-migrationSwitching embedding models without downtime
qdrant-version-upgradeSafe upgrade paths, compatibility guarantees, rolling upgrades

Installing and Contributing

For instructions on installing skills in your own coding agent (Cursor, Claude Code, OpenCode, and others), refer to this README.

For guidance on contributing new skills or reporting problems, refer to CONTRIBUTING.md in the repository.

Was this page useful?

Thank you for your feedback! 🙏

We are sorry to hear that. 😔 You can edit this page on GitHub, or create a GitHub issue.