Official agent skill

Qdrant Horizontal Scaling

by qdrant in qdrant/skills

Diagnoses and guides Qdrant horizontal scaling decisions. An agent skill from qdrant/skills.

OfficialApache-2.0Auto-check passedDatabases

Install Qdrant Horizontal Scaling

skills CLI
$ npx skills add qdrant/skills --skill qdrant-horizontal-scaling -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install qdrant/skills qdrant-horizontal-scaling --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/qdrant/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/qdrant-scaling/scaling-data-volume/horizontal-scaling .claude/skills/qdrant-horizontal-scaling && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
qdrant-horizontal-scaling
GitHub stars
253
Used in
2 other repos
Token cost
~833 tokens
SKILL.md length
406 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
Apache-2.0

At a glance

Diagnoses and guides Qdrant horizontal scaling decisions. An agent skill from qdrant/skills.

  • Someone asks vertical
  • SKILL.md covers Most basic distributed…, Choosing number of shards, Changing number of shards and What NOT to Do
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • How many nodes?

What it does

Qdrant Horizontal Scaling is an agent skill from qdrant/skills, published by the product's own GitHub organization. Diagnoses and guides Qdrant horizontal scaling decisions. Use when someone asks 'vertical or horizontal?', 'how many nodes?', 'how many shards?', 'how to add nodes', 'resharding', 'data doesn't fit', or 'need more capacity'. Also use when data growth outpaces current deployment.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases, covering Vector databases. It works with Qdrant. The repository describes itself as: Agent skills for Qdrant vector search: scaling, performance optimization, search quality, monitoring, deployment, model migration, version upgrades, and SDK usage across Python…. The licence is Apache-2.0.

When your agent uses it

  • Someone asks vertical
  • How many nodes?
  • How many shards?
  • How to add nodes

Example prompts

  • “vertical or horizontal?”
  • “how many nodes?”
  • “how many shards?”
  • “/qdrant-horizontal-scaling”

What it can do on your machine

Read from SKILL.md and the folder at commit 476a18d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • skills.qdrant.tech

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Qdrant Horizontal Scaling loads about 833 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 406 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~833

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from qdrant/skills at commit 476a18d, republished under its Apache-2.0 licence (© qdrant). 406 words, ~833 tokens.

Download SKILL.mdSave it as .claude/skills/qdrant-horizontal-scaling/SKILL.md (or your agent's skills folder).
name
qdrant-horizontal-scaling
description
Diagnoses and guides Qdrant horizontal scaling decisions. Use when someone asks 'vertical or horizontal?', 'how many nodes?', 'how many shards?', 'how to add nodes', 'resharding', 'data doesn't fit', or 'need more capacity'. Also use when data growth outpaces current deployment.

What to Do When Qdrant Needs More Capacity

Vertical first: simpler operations, no network overhead, good up to ~100M vectors per node depending on dimensions and quantization. Horizontal when: data exceeds single node capacity, need fault tolerance, need to isolate tenants, or IOPS-bound (more nodes = more independent IOPS).

Most basic distributed configuration

  • 3 nodes with replication_factor: 2 for zero-downtime scaling, and at least 2 shards per node (6 shards) so you can add nodes later without resharding Sharding

Minimum of 3 nodes is important for consensus and fault tolerance. With 3 nodes, you can lose 1 node without downtime. With 2 nodes, losing 1 node causes downtime for collection operations. Replication factor of 2 means each shard has 1 replica, so you have 2 copies of data. This allows for zero-downtime scaling and maintenance. With replication_factor: 1, zero-downtime is not guaranteed even for point-level operations, and cluster maintenance requires downtime.

Choosing number of shards

Shards are the unit of data distribution. More shards allows more nodes and better distribution, but adds overhead. Fewer shards reduces overhead but limits horizontal scaling.

For cluster of 3-6 nodes the recommended shard count is 6-12. This allows for 2-4 shards per node, which balances distribution and overhead.

Show full SKILL.md (203 more words)Show less

Changing number of shards

Use when: shard count isn't evenly divisible by node count, causing uneven distribution, or need to rebalance.

Resharding is expensive and time-consuming, it should be used as a last resort if regular data distribution is not possible. Resharding is designed to be transparent for user operations, updates and searches should still work during resharding with some small performance impact.

But resharding operation itself is time-consuming and requires to move large amounts of data between nodes.

  • Available in Qdrant Cloud Resharding
  • Resharding is not available for self-hosted deployments.

Better alternatives: over-provision shards initially, or spin up new cluster with correct config and migrate data.

What NOT to Do

  • Do not jump to horizontal before exhausting vertical (adds complexity for no gain)
  • Do not set shard_number that isn't a multiple of node count (uneven distribution)
  • Do not use replication_factor: 1 in production if you need fault tolerance
  • Do not add nodes to a self-hosted cluster without rebalancing shards (use the shard move API to redistribute); Qdrant Cloud rebalances shards automatically Cluster scaling
  • Do not scale down RAM without load testing (cache eviction causes days-long latency incidents)
  • Do not hit the collection limit by using one collection per tenant (use payload partitioning)

© qdrant, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/qdrant-scaling/scaling-data-volume/horizontal-scaling of qdrant/skills.

Open the folder on GitHubat commit 476a18d

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in qdrant/skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Qdrant Horizontal Scaling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Qdrant Horizontal Scaling compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qdrant Horizontal Scaling this skillqdrant/skills2532 repos~833Automated safety check: PassApache-2.0
Qdrant Performance Optimizationgithub/awesome-copilot40k1 repos~461Automated safety check: PassMIT
Qdrant Scalinggithub/awesome-copilot40k1 repos~467Automated safety check: PassMIT
Codebase Explorationgiancarloerra/SocratiCode3.3k1 repos~1.5kAutomated safety check: PassAGPL-3.0
Qdrant Vector SearchOrchestra-Research/AI-Research-SKILLs13k5 repos~3.4kAutomated safety check: PassMIT
Using Vector Databasesancoleman/ai-design-components5261 repos~3.5kAutomated safety check: PassMIT

Similar skills

  • Qdrant Performance Optimization

    github/awesome-copilot

    Official

    Different techniques to optimize the performance of Qdrant, including indexing strategies, query optimization, and hardware considerations.

    40k GitHub starsUsed in 1 repo~461 tokens
    DatabasesAuto-check passed
  • Qdrant Scaling

    github/awesome-copilot

    Official

    Guides Qdrant scaling decisions. An agent skill from github/awesome-copilot.

    40k GitHub starsUsed in 1 repo~467 tokens
    DatabasesAuto-check passed
  • Codebase Exploration

    giancarloerra/SocratiCode

    Explore and understand codebases using SocratiCode semantic search, dependency graphs, and context artifacts.

    3.3k GitHub starsUsed in 1 repo~1.5k tokens
    DatabasesAuto-check passed
  • Qdrant Vector Search

    Orchestra-Research/AI-Research-SKILLs

    Explains how to run Qdrant, a Rust vector database, for RAG and semantic search, covering collections, points, distance metrics and filtered or batched queries.

    13k GitHub starsUsed in 5 repos~3.4k tokens
    DatabasesAuto-check passed
  • Using Vector Databases

    ancoleman/ai-design-components

    Vector database implementation for AI/ML applications, semantic search, and RAG systems.

    526 GitHub starsUsed in 1 repo~3.5k tokens
    DatabasesAuto-check passed
  • Qdrant

    giuseppe-trisciuoglio/developer-kit

    Provides Qdrant vector database integration patterns with LangChain4j.

    355 GitHub starsUsed in 1 repo~1.6k tokens
    DatabasesAuto-check: notes

More from qdrant/skills

All 33 skills in this repo
  • Qdrant Clients SDK

    qdrant/skills

    Official

    Qdrant provides client SDKs for various programming languages, allowing easy integration with Qdrant deployments.

    253 GitHub starsUsed in 2 repos~752 tokens
    Auto-check: notes
  • Qdrant Advisor

    qdrant/skills

    Official

    Diagnose, troubleshoot, and advise on any Qdrant deployment by loading the latest official Qdrant skills live from skills.qdrant.tech.

    253 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • Official

    Guides Qdrant deployment selection. An agent skill from qdrant/skills.

    253 GitHub starsUsed in 2 repos~976 tokens
    Auto-check passed
  • Official

    Guides Qdrant search strategy selection. An agent skill from qdrant/skills.

    253 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Official

    Diagnoses and reduces Qdrant memory usage. An agent skill from qdrant/skills.

    253 GitHub starsUsed in 2 repos~1.6k tokens
    Auto-check passed

Works with

Categories

Questions about Qdrant Horizontal Scaling

What does Qdrant Horizontal Scaling do?

Diagnoses and guides Qdrant horizontal scaling decisions. An agent skill from qdrant/skills. Qdrant Horizontal Scaling is an agent skill from qdrant/skills, published by the product's own GitHub organization. Diagnoses and guides Qdrant horizontal scaling decisions.

When should I use Qdrant Horizontal Scaling?

Qdrant Horizontal Scaling fits situations like: someone asks vertical; how many nodes?; how many shards?; how to add nodes.

How do I install Qdrant Horizontal Scaling in Claude Code?

Run `npx skills add qdrant/skills --skill qdrant-horizontal-scaling -a claude-code`. Or copy the skill folder (skills/qdrant-scaling/scaling-data-volume/horizontal-scaling in qdrant/skills) into .claude/skills/qdrant-horizontal-scaling in your project. Claude Code loads it when a task matches its description.

How do I install Qdrant Horizontal Scaling in Codex?

Run `npx skills add qdrant/skills --skill qdrant-horizontal-scaling -a codex`. Or copy the skill folder (skills/qdrant-scaling/scaling-data-volume/horizontal-scaling in qdrant/skills) into .agents/skills/qdrant-horizontal-scaling in your project. Codex loads it when a task matches its description.

Can I use Qdrant Horizontal Scaling in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add qdrant/skills --skill qdrant-horizontal-scaling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qdrant-horizontal-scaling, .gemini/skills/qdrant-horizontal-scaling, .github/skills/qdrant-horizontal-scaling and .opencode/skills/qdrant-horizontal-scaling in your project.

What does Qdrant Horizontal Scaling need to run?

SKILL.md names no scripts, command-line tools or credentials: Qdrant Horizontal Scaling is instructions for the agent only.

Does Qdrant Horizontal Scaling access the network?

SKILL.md names 1 domain. As links in the text: skills.qdrant.tech. This is read from the text; nothing was executed.

Is Qdrant Horizontal Scaling safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Qdrant Horizontal Scaling use?

Qdrant Horizontal Scaling is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Qdrant Horizontal Scaling use?

About 833 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Qdrant Horizontal Scaling?

Skills that share tags, products or a category with Qdrant Horizontal Scaling: Qdrant Performance Optimization (github/awesome-copilot, 40k stars), Qdrant Scaling (github/awesome-copilot, 40k stars), Codebase Exploration (giancarloerra/SocratiCode, 3.3k stars) and Qdrant Vector Search (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Qdrant Horizontal Scaling?

qdrant (a GitHub organization, an official publisher) maintains it in qdrant/skills, which has 253 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 6, 2026.

Source: qdrant/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.