New: 98,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 Monitoring Debugging

by qdrant in qdrant/skills

Diagnoses Qdrant production issues using metrics and observability tools.

OfficialApache-2.0Auto-check passedDatabases

Install Qdrant Monitoring Debugging

skills CLI
$ npx skills add qdrant/skills --skill qdrant-monitoring-debugging -a claude-code

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

GitHub CLI
$ gh skill install qdrant/skills qdrant-monitoring-debugging --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-monitoring/debugging .claude/skills/qdrant-monitoring-debugging && 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-monitoring-debugging
GitHub stars
253
Used in
2 other repos
Token cost
~897 tokens
SKILL.md length
374 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
Apache-2.0

At a glance

Diagnoses Qdrant production issues using metrics and observability tools.

  • Someone reports optimizer stuck
  • SKILL.md covers Optimizer Stuck or Too Slow, Memory Seems Too High, Queries Are Slow and What NOT to Do
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Indexing too slow

What it does

Qdrant Monitoring Debugging is an agent skill from qdrant/skills, published by the product's own GitHub organization. Diagnoses Qdrant production issues using metrics and observability tools. Use when someone reports 'optimizer stuck', 'indexing too slow', 'memory too high', 'OOM crash', 'queries are slow', 'latency spike', or 'search was fast now it's slow'. Also use when performance degrades without obvious config changes.

Its SKILL.md is about 900 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 reports optimizer stuck
  • Indexing too slow
  • Memory too high
  • Queries are slow

Example prompts

  • “optimizer stuck”
  • “indexing too slow”
  • “memory too high”
  • “/qdrant-monitoring-debugging”

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 Monitoring Debugging loads about 897 tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 374 words of instructions outside code blocks.

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

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). 374 words, ~897 tokens.

Download SKILL.mdSave it as .claude/skills/qdrant-monitoring-debugging/SKILL.md (or your agent's skills folder).
name
qdrant-monitoring-debugging
description
Diagnoses Qdrant production issues using metrics and observability tools. Use when someone reports 'optimizer stuck', 'indexing too slow', 'memory too high', 'OOM crash', 'queries are slow', 'latency spike', or 'search was fast now it's slow'. Also use when performance degrades without obvious config changes.

How to Debug Qdrant with Metrics

First check optimizer status. Most production issues trace back to active optimizations competing for resources. If optimizer is clean, check memory, then request metrics.

Optimizer Stuck or Too Slow

Use when: optimizer running for hours, not finishing, or showing errors.

  • Use /collections/{collection_name}/optimizations endpoint (v1.17+) to check status Optimization monitoring
  • Query with optional detail flags: ?with=queued,completed,idle_segments
  • Returns: queued optimizations count, active optimizer type, involved segments, progress tracking
  • Web UI has an Optimizations tab with timeline view and per-task duration metrics Web UI
  • If optimizer_status shows an error in collection info, check logs for disk full or corrupted segments
  • Large merges and HNSW rebuilds legitimately take hours on big datasets. Check progress before assuming it's stuck.

Memory Seems Too High

Use when: memory exceeds expectations, node crashes with OOM, or memory keeps growing.

  • Process memory metrics available via /metrics (RSS, allocated bytes, page faults)
  • Qdrant uses two types of RAM: resident memory (data structures, quantized vectors) and OS page cache (cached disk reads). Page cache filling available RAM is normal. Memory article
  • If resident memory (RSSAnon) exceeds 80% of total RAM, investigate
  • Check /telemetry for per-collection breakdown of point counts and vector configurations
  • Estimate expected memory: num_vectors * dimensions * 4 bytes * 1.5 for vectors, plus payload and index overhead Capacity planning
  • Common causes of unexpected growth: quantized vectors pinned in RAM (memory: pinned on Qdrant 1.19 or newer, always_ram: true on 1.18 or older), too many payload indexes, large max_segment_size during optimization
Show full SKILL.md (129 more words)Show less

Queries Are Slow

Use when: queries slower than expected and you need to identify the cause.

  • Track rest_responses_avg_duration_seconds and rest_responses_max_duration_seconds per endpoint
  • Use histogram metric rest_responses_duration_seconds (v1.8+) for percentile analysis in Grafana
  • Equivalent gRPC metrics with grpc_responses_ prefix
  • Check optimizer status first. Active optimizations compete for CPU and I/O, degrading search latency.
  • Check segment count via collection info. Too many unmerged segments after bulk upload causes slower search.
  • Compare filtered vs unfiltered query times. Large gap means missing payload index. Payload index

What NOT to Do

  • Ignore optimizer status when debugging slow queries (most common root cause)
  • Assume memory leak when page cache fills RAM (normal OS behavior)
  • Make config changes while optimizer is running (causes cascading re-optimizations)
  • Blame Qdrant before checking if bulk upload just finished (unmerged segments)

© 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-monitoring/debugging 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 Monitoring Debugging 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 Monitoring Debugging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qdrant Monitoring Debugging this skillqdrant/skills2532 repos~897Automated safety check: PassApache-2.0
Qdrant Performance Optimizationgithub/awesome-copilot40k1 repos~461Automated safety check: PassMIT
Qdrant Scalinggithub/awesome-copilot40k1 repos~467Automated safety check: PassMIT
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

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

  • 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

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 Monitoring Debugging

What does Qdrant Monitoring Debugging do?

Diagnoses Qdrant production issues using metrics and observability tools. Qdrant Monitoring Debugging is an agent skill from qdrant/skills, published by the product's own GitHub organization. Diagnoses Qdrant production issues using metrics and observability tools.

When should I use Qdrant Monitoring Debugging?

Qdrant Monitoring Debugging fits situations like: someone reports optimizer stuck; indexing too slow; memory too high; queries are slow.

How do I install Qdrant Monitoring Debugging in Claude Code?

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

How do I install Qdrant Monitoring Debugging in Codex?

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

Can I use Qdrant Monitoring Debugging 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-monitoring-debugging -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-monitoring-debugging, .gemini/skills/qdrant-monitoring-debugging, .github/skills/qdrant-monitoring-debugging and .opencode/skills/qdrant-monitoring-debugging in your project.

What does Qdrant Monitoring Debugging need to run?

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

Does Qdrant Monitoring Debugging 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 Monitoring Debugging 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 Monitoring Debugging use?

Qdrant Monitoring Debugging 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 Monitoring Debugging use?

About 897 tokens (SKILL.md is roughly 3.6k 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 Monitoring Debugging?

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

Who maintains Qdrant Monitoring Debugging?

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 7, 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.