New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Qdrant Version Upgrade

by qdrant in qdrant/skills

Covers upgrading Qdrant server and SDKs without interrupting availability or losing data integrity.

OfficialApache-2.0Auto-check passedDatabases

Install Qdrant Version Upgrade

skills CLI
$ npx skills add qdrant/skills --skill qdrant-version-upgrade -a claude-code

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

GitHub CLI
$ gh skill install qdrant/skills qdrant-version-upgrade --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-version-upgrade .claude/skills/qdrant-version-upgrade && 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-version-upgrade
GitHub stars
253
Token cost
~1.3k tokens
SKILL.md length
692 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
Apache-2.0

At a glance

Covers upgrading Qdrant server and SDKs without interrupting availability or losing data integrity.

  • Works in 5 steps: Back up first: It's recommended to take… → Check release notes for default and… → Test your client app against the target… → …
  • Someone asks how do I upgrade Qdrant
  • SKILL.md covers Pre-Upgrade Checklist, Crossing More Then One Minor…, Troubleshooting Behavior… and What NOT to Do
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Qdrant Version Upgrade is an agent skill from qdrant/skills, published by the product's own GitHub organization. Covers upgrading Qdrant server and SDKs without interrupting availability or losing data integrity. Use when someone asks 'how do I upgrade Qdrant', 'can I jump from 1.15 to 1.18', 'rolling upgrade without downtime', 'do I upgrade the client or the server first', 'which SDK version matches my server', 'what should I check before upgrading', or 'something changed after we upgraded'.

Its SKILL.md is about 1.3k 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 and Code migrations. 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 how do I upgrade Qdrant
  • Can I jump from 1.15 to 1.18
  • Rolling upgrade without downtime
  • Do I upgrade the client

Example prompts

  • “how do I upgrade Qdrant”
  • “can I jump from 1.15 to 1.18”
  • “rolling upgrade without downtime”
  • “/qdrant-version-upgrade”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Back up first: It's recommended to take a backup or snapshot before updating to allow for rollbacks. If the upgrade fails or you need to…
  2. Check release notes for default and behavior changes, not just deprecations. Version upgrades may introduce changes to default settings…
  3. Test your client app against the target server version first in a non-prod environment, and check SDK release notes for deprecated/removed…
  4. It's recommended to run at least 2 CPU cores per node. During upgrades, Qdrant may perform background optimization while still handling…
  5. Use a replication factor of 2 or higher if you need a zero-downtime rolling upgrade. With a replication factor of 1, the upgrade requires…

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
    • github.com

    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 Version Upgrade loads about 1.3k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 692 words of instructions outside code blocks.

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

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). 692 words, ~1,349 tokens.

Download SKILL.mdSave it as .claude/skills/qdrant-version-upgrade/SKILL.md (or your agent's skills folder).
name
qdrant-version-upgrade
description
Covers upgrading Qdrant server and SDKs without interrupting availability or losing data integrity. Use when someone asks 'how do I upgrade Qdrant', 'can I jump from 1.15 to 1.18', 'rolling upgrade without downtime', 'do I upgrade the client or the server first', 'which SDK version matches my server', 'what should I check before upgrading', or 'something changed after we upgraded'.

Qdrant Version Upgrade

Qdrant has the following guarantees about version compatibility:

  • Major and minor versions of Qdrant and SDK are expected to match. For example, Qdrant 1.17.x is compatible with SDK 1.17.x.

  • Client SDKs are tested to be backward compatible with the latest 3 minor versions of Qdrant. For example, SDK 1.17.x works with Qdrant 1.15.x to 1.17.x, but only for the features the server version supports Upgrades

  • For migration to the next minor version, it is recommended to first upgrade the SDK to the next minor version and then upgrade the Qdrant server.

  • Storage compatibility is only guaranteed for one minor version. For example, data stored with Qdrant 1.16.x is expected to be compatible with Qdrant 1.17.x. If you need to migrate more than one minor version, it is required do the upgrade step by step, one minor version at a time. For example, to migrate from 1.15.x to 1.17.x, you need to first upgrade to 1.16.x and then to 1.17.x. Note: Qdrant Cloud automates this process, so you can directly upgrade from 1.15.x to 1.17.x without intermediate steps.

  • A Qdrant cluster with a replication factor of 2 or higher can be upgraded without downtime by performing a rolling upgrade. This means that you can upgrade one node at a time while the other nodes continue to serve requests. This allows you to maintain availability of your application during the upgrade process. More about replication factor: Replication factor

For managing Qdrant version upgrades in Qdrant Cloud, you can use the qcloud CLI tool.

Pre-Upgrade Checklist

  1. Back up first: It's recommended to take a backup or snapshot before updating to allow for rollbacks. If the upgrade fails or you need to revert, you can restore the pre-upgrade snapshot. Qdrant Cloud applies data migrations during upgrades, so there's no live downgrade. Snapshots Cloud backups

  2. Check release notes for default and behavior changes, not just deprecations. Version upgrades may introduce changes to default settings, validation rules, or query behavior that can affect existing workloads even when APIs remain compatible.

  3. Test your client app against the target server version first in a non-prod environment, and check SDK release notes for deprecated/removed methods before switching over.

  4. It's recommended to run at least 2 CPU cores per node. During upgrades, Qdrant may perform background optimization while still handling regular operations. With only 1 core, these tasks can compete for CPU resources and can significantly slow down the upgrade process.

  5. Use a replication factor of 2 or higher if you need a zero-downtime rolling upgrade. With a replication factor of 1, the upgrade requires a downtime window.

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

Crossing More Then One Minor Versions

Use when: the running version is two or more minor versions behind the target.

  • Self-hosted: step through every intermediate minor version, and land on the latest patch of each before moving on. From 1.15 to 1.17, go to the newest 1.16.x first, then 1.17.x. Upgrading Qdrant
  • Each step is its own rolling restart, so the total is a multiple of a single-version upgrade. This takes longer than a single-version bump, so plan for it and prefer non-peak hours.
  • Qdrant Cloud chains the intermediate updates for you, so 1.15.x to 1.17.x is a single action. Updating Qdrant Cloud clusters
  • Upgrade on a regular cadence to keep future jumps to one minor version. Regular upgrades also reduce the complexity of future migrations by avoiding large version jumps.

Troubleshooting Behavior Changes After an Upgrade

Use when: results, scores, or latency look different once the new version is live.

  • When investigating a bug or unexpected behavior after an upgrade, check the release notes/changelog between the source and target versions for deprecations, default-value changes, and behavior changes that may affect your workload.

  • Compare relative ranking and recall against your pre-upgrade baseline, not absolute score values. Scoring internals can change between versions and still be correct.

What NOT to Do

  • Treat identical absolute scores as an acceptance criterion across versions
  • Read only the target version's notes and skip intermediate minor and patch releases
  • Jump multiple minor versions at once on self-hosted deployments
  • Assume a rolling upgrade finished without confirming that every node reports the target version

© 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-version-upgrade of qdrant/skills.

Open the folder on GitHubat commit 476a18d

Compare with similar skills

Qdrant Version Upgrade 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 Version Upgrade compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qdrant Version Upgrade this skillqdrant/skills253—~1.3kAutomated safety check: PassApache-2.0
Qdrant Version Upgradegithub/awesome-copilot40k2 repos~485Automated safety check: PassMIT
Codebase Explorationgiancarloerra/SocratiCode3.3k1 repos~1.5kAutomated safety check: PassAGPL-3.0
Cognee Community Packagestopoteretes/cognee32k—~1.2kAutomated safety check: PassApache-2.0
Qdrant Vector SearchOrchestra-Research/AI-Research-SKILLs13k5 repos~3.4kAutomated safety check: PassMIT
Amazon Documentdbaws/agent-toolkit-for-aws2.8k—~5.9kAutomated safety check: PassApache-2.0

Similar skills

  • Qdrant Version Upgrade

    github/awesome-copilot

    Official

    Guidance on how to upgrade your Qdrant version without interrupting the availability of your application and ensuring data integrity.

    40k GitHub starsUsed in 2 repos~485 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

  • Cognee Community Packages

    topoteretes/cognee

    Guide to using and contributing cognee community packages: database adapters, data-source connectors, custom tasks and retrievers, and Keywords AI observability.

    32k GitHub stars~1.2k tokensUpdated today
    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

  • Amazon Documentdb

    aws/agent-toolkit-for-aws

    Official

    Manages Amazon DocumentDB end-to-end — serverless-on-8.0 cluster setup, TLS/VPC/driver config, flexible-schema and vector-search data modeling, MongoDB compatibility assessment, DMS-based migration…

    2.8k GitHub stars~5.9k tokensUpdated today
    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

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

  • Qdrant Deployment Options

    qdrant/skills

    Official

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

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

  • Qdrant Search Strategies

    qdrant/skills

    Official

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

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

  • Qdrant Horizontal Scaling

    qdrant/skills

    Official

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

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

Works with

Categories

Questions about Qdrant Version Upgrade

What does Qdrant Version Upgrade do?

Covers upgrading Qdrant server and SDKs without interrupting availability or losing data integrity. Qdrant Version Upgrade is an agent skill from qdrant/skills, published by the product's own GitHub organization. Covers upgrading Qdrant server and SDKs without interrupting availability or losing data integrity.

When should I use Qdrant Version Upgrade?

Qdrant Version Upgrade fits situations like: someone asks how do I upgrade Qdrant; can I jump from 1.15 to 1.18; rolling upgrade without downtime; do I upgrade the client.

How do I install Qdrant Version Upgrade in Claude Code?

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

How do I install Qdrant Version Upgrade in Codex?

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

Can I use Qdrant Version Upgrade 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-version-upgrade -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-version-upgrade, .gemini/skills/qdrant-version-upgrade, .github/skills/qdrant-version-upgrade and .opencode/skills/qdrant-version-upgrade in your project.

What does Qdrant Version Upgrade need to run?

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

Does Qdrant Version Upgrade access the network?

SKILL.md names 2 domains. As links in the text: skills.qdrant.tech and github.com. This is read from the text; nothing was executed.

Is Qdrant Version Upgrade 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 Version Upgrade use?

Qdrant Version Upgrade 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 Version Upgrade use?

About 1.3k tokens (SKILL.md is roughly 5.4k 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 Version Upgrade?

Skills that share tags, products or a category with Qdrant Version Upgrade: Qdrant Version Upgrade (github/awesome-copilot, 40k stars), Codebase Exploration (giancarloerra/SocratiCode, 3.3k stars), Cognee Community Packages (topoteretes/cognee, 32k 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 Version Upgrade?

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.