Qdrant Performance Optimization
github/awesome-copilot
Different techniques to optimize the performance of Qdrant, including indexing strategies, query optimization, and hardware considerations.
Guides sliding time window scaling in Qdrant. An agent skill from qdrant/skills.
$ npx skills add qdrant/skills --skill qdrant-sliding-time-window -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install qdrant/skills qdrant-sliding-time-window --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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/sliding-time-window .claude/skills/qdrant-sliding-time-window && rm -rf skills-srcUse ~/.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/
Install the "qdrant-sliding-time-window" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-scaling/scaling-data-volume/sliding-time-window into .claude/skills/qdrant-sliding-time-window/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-sliding-time-window", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/qdrant/skills/tree/main/skills/qdrant-scaling/scaling-data-volume/sliding-time-windowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add qdrant/skills --skill qdrant-sliding-time-window -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install qdrant/skills qdrant-sliding-time-window --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qdrant/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/qdrant-scaling/scaling-data-volume/sliding-time-window .agents/skills/qdrant-sliding-time-window && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "qdrant-sliding-time-window" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-scaling/scaling-data-volume/sliding-time-window into .agents/skills/qdrant-sliding-time-window/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-sliding-time-window", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add qdrant/skills --skill qdrant-sliding-time-window -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install qdrant/skills qdrant-sliding-time-window --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qdrant/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/qdrant-scaling/scaling-data-volume/sliding-time-window .cursor/skills/qdrant-sliding-time-window && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "qdrant-sliding-time-window" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-scaling/scaling-data-volume/sliding-time-window into .cursor/skills/qdrant-sliding-time-window/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-sliding-time-window", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/qdrant/skills.git --path skills/qdrant-scaling/scaling-data-volume/sliding-time-window--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add qdrant/skills --skill qdrant-sliding-time-window -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install qdrant/skills qdrant-sliding-time-window --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qdrant/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/qdrant-scaling/scaling-data-volume/sliding-time-window .gemini/skills/qdrant-sliding-time-window && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "qdrant-sliding-time-window" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-scaling/scaling-data-volume/sliding-time-window into .gemini/skills/qdrant-sliding-time-window/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-sliding-time-window", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install qdrant/skills qdrant-sliding-time-windowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add qdrant/skills --skill qdrant-sliding-time-window -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/qdrant/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/qdrant-scaling/scaling-data-volume/sliding-time-window .github/skills/qdrant-sliding-time-window && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "qdrant-sliding-time-window" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-scaling/scaling-data-volume/sliding-time-window into .github/skills/qdrant-sliding-time-window/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-sliding-time-window", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add qdrant/skills --skill qdrant-sliding-time-window -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install qdrant/skills qdrant-sliding-time-window --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qdrant/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/qdrant-scaling/scaling-data-volume/sliding-time-window .opencode/skills/qdrant-sliding-time-window && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "qdrant-sliding-time-window" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-scaling/scaling-data-volume/sliding-time-window into .opencode/skills/qdrant-sliding-time-window/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-sliding-time-window", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
qdrant-sliding-time-windowGuides sliding time window scaling in Qdrant. An agent skill from qdrant/skills.
Qdrant Sliding Time Window is an agent skill from qdrant/skills, published by the product's own GitHub organization. Guides sliding time window scaling in Qdrant. Use when someone asks 'only recent data matters', 'how to expire old vectors', 'time-based data rotation', 'delete old data efficiently', 'social media feed search', 'news search', 'log search with retention', or 'how to keep only last N months of data'.
Its SKILL.md is about 1.2k 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.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 476a18d. It shows what the files ask for, not the result of running them.
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.
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.
Links to these hosts (documentation or services it may open):
skills.qdrant.techFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Qdrant Sliding Time Window loads about 1.2k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 542 words of instructions outside code blocks.
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.
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.
The full file from qdrant/skills at commit 476a18d, republished under its Apache-2.0 licence (© qdrant). 542 words, ~1,184 tokens.
.claude/skills/qdrant-sliding-time-window/SKILL.md (or your agent's skills folder).Use when only recent data needs fast search -- social media posts, news articles, support tickets, logs, job listings. Old data either becomes irrelevant or can tolerate slower access.
Three strategies: shard rotation (recommended), collection rotation (when per-period config differs), and filter-and-delete (simplest, for continuous cleanup).
Use when: data has natural time boundaries (daily, weekly, monthly). Preferred because queries span all time periods in one request without application-level fan-out. User-defined sharding
2025-01, 2025-02, ..., 2025-06)shard_key_selector at query time to search only specific periods for efficiencyUse when: you need per-period collection configuration (e.g., different quantization or storage settings). Collection aliases
Trade-off vs shard rotation: allows per-collection config differences, but requires application-level fan-out and more operational overhead.
Use when: data arrives continuously without clear time boundaries, or you want the simplest setup.
timestamp payload on every point, create a payload index on it Payload indexrange condition Range filterUse when: recent data needs fast in-RAM search, older data should remain searchable at lower performance.
memory: pinned on Qdrant 1.19 or newer, always_ram: true on 1.18 or older) and its dense vectors in page cache (memory: cached, the default; Qdrant rejects pinned for dense vectors), move older collections to mmap/on-disk vectors (memory: cold on 1.19 or newer, on_disk: true on 1.18 or older). Quantization© 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
Just SKILL.md in skills/qdrant-scaling/scaling-data-volume/sliding-time-window of qdrant/skills.
Open the folder on GitHubat commit 476a18d
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.
Qdrant Sliding Time Window 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Qdrant Sliding Time Window this skillqdrant/skills | 253 | 2 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Qdrant Performance Optimizationgithub/awesome-copilot | 40k | 1 repos | ~461 | Automated safety check: Pass | MIT | |
| Qdrant Scalinggithub/awesome-copilot | 40k | 1 repos | ~467 | Automated safety check: Pass | MIT | |
| Codebase Explorationgiancarloerra/SocratiCode | 3.3k | 1 repos | ~1.5k | Automated safety check: Pass | AGPL-3.0 | |
| Qdrant Vector SearchOrchestra-Research/AI-Research-SKILLs | 13k | 5 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Using Vector Databasesancoleman/ai-design-components | 526 | 1 repos | ~3.5k | Automated safety check: Pass | MIT |
github/awesome-copilot
Different techniques to optimize the performance of Qdrant, including indexing strategies, query optimization, and hardware considerations.
github/awesome-copilot
Guides Qdrant scaling decisions. An agent skill from github/awesome-copilot.
giancarloerra/SocratiCode
Explore and understand codebases using SocratiCode semantic search, dependency graphs, and context artifacts.
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.
ancoleman/ai-design-components
Vector database implementation for AI/ML applications, semantic search, and RAG systems.
giuseppe-trisciuoglio/developer-kit
Provides Qdrant vector database integration patterns with LangChain4j.
qdrant/skills
Qdrant provides client SDKs for various programming languages, allowing easy integration with Qdrant deployments.
qdrant/skills
Diagnose, troubleshoot, and advise on any Qdrant deployment by loading the latest official Qdrant skills live from skills.qdrant.tech.
qdrant/skills
Guides Qdrant deployment selection. An agent skill from qdrant/skills.
qdrant/skills
Guides Qdrant search strategy selection. An agent skill from qdrant/skills.
qdrant/skills
Diagnoses and guides Qdrant horizontal scaling decisions. An agent skill from qdrant/skills.
qdrant/skills
Diagnoses and fixes slow Qdrant indexing and data ingestion.
Works with
Categories
Guides sliding time window scaling in Qdrant. An agent skill from qdrant/skills. Qdrant Sliding Time Window is an agent skill from qdrant/skills, published by the product's own GitHub organization. Guides sliding time window scaling in Qdrant.
Qdrant Sliding Time Window fits situations like: someone asks only recent data matters; how to expire old vectors; time-based data rotation; delete old data efficiently.
Run `npx skills add qdrant/skills --skill qdrant-sliding-time-window -a claude-code`. Or copy the skill folder (skills/qdrant-scaling/scaling-data-volume/sliding-time-window in qdrant/skills) into .claude/skills/qdrant-sliding-time-window in your project. Claude Code loads it when a task matches its description.
Run `npx skills add qdrant/skills --skill qdrant-sliding-time-window -a codex`. Or copy the skill folder (skills/qdrant-scaling/scaling-data-volume/sliding-time-window in qdrant/skills) into .agents/skills/qdrant-sliding-time-window in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add qdrant/skills --skill qdrant-sliding-time-window -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-sliding-time-window, .gemini/skills/qdrant-sliding-time-window, .github/skills/qdrant-sliding-time-window and .opencode/skills/qdrant-sliding-time-window in your project.
SKILL.md names no scripts, command-line tools or credentials: Qdrant Sliding Time Window is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: skills.qdrant.tech. This is read from the text; nothing was executed.
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.
Qdrant Sliding Time Window 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.
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Qdrant Sliding Time Window: 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.
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.