Qdrant Monitoring
github/awesome-copilot
Guides Qdrant monitoring and observability setup. An agent skill from github/awesome-copilot.
Guides Qdrant monitoring and observability setup. An agent skill from qdrant/skills.
Install Qdrant Monitoring
$ npx skills add qdrant/skills --skill qdrant-monitoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install qdrant/skills qdrant-monitoring --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-monitoring .claude/skills/qdrant-monitoring && 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-monitoring" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring into .claude/skills/qdrant-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-monitoring", 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-monitoringType 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-monitoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install qdrant/skills qdrant-monitoring --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-monitoring .agents/skills/qdrant-monitoring && 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-monitoring" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring into .agents/skills/qdrant-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-monitoring", 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-monitoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install qdrant/skills qdrant-monitoring --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-monitoring .cursor/skills/qdrant-monitoring && 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-monitoring" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring into .cursor/skills/qdrant-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-monitoring", 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-monitoring--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-monitoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install qdrant/skills qdrant-monitoring --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-monitoring .gemini/skills/qdrant-monitoring && 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-monitoring" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring into .gemini/skills/qdrant-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-monitoring", 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-monitoringInstalls 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-monitoring -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-monitoring .github/skills/qdrant-monitoring && 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-monitoring" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring into .github/skills/qdrant-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-monitoring", 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-monitoring -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-monitoring --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-monitoring .opencode/skills/qdrant-monitoring && 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-monitoring" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring into .opencode/skills/qdrant-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-monitoring", 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.
Facts
- Skill name
qdrant-monitoring- GitHub stars
- 254
- Token cost
- ~368 tokens
- SKILL.md length
- 123 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guides Qdrant monitoring and observability setup. An agent skill from qdrant/skills.
- Someone asks how to monitor Qdrant
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- What metrics to track
- Is Qdrant healthy
What it does
Qdrant Monitoring is an agent skill from qdrant/skills, published by the product's own GitHub organization. Guides Qdrant monitoring and observability setup. Use when someone asks 'how to monitor Qdrant', 'what metrics to track', 'is Qdrant healthy', 'optimizer stuck', 'why is memory growing', 'requests are slow', 'set up alerts', 'cluster health check', or needs to set up Prometheus, Grafana, health checks, or log centralization. Also use when debugging production issues that require metric analysis.
Its SKILL.md is about 370 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 DevOps & Cloud, covering Vector databases and Monitoring and alerting. It works with Qdrant, Prometheus and Grafana. 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 to monitor Qdrant
- What metrics to track
- Is Qdrant healthy
- Optimizer stuck
Example prompts
- “how to monitor Qdrant”
- “what metrics to track”
- “is Qdrant healthy”
- “/qdrant-monitoring”
Requirements
- Pre-approved tools (allowed-tools): Read, Grep, Glob
What it can do on your machine
Read from SKILL.md and the folder at commit 1780b6d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlob
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 loads about 368 tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 123 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.
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 1780b6d, republished under its Apache-2.0 licence (© qdrant). 123 words, ~368 tokens.
Download SKILL.mdSave it as
.claude/skills/qdrant-monitoring/SKILL.md (or your agent's skills folder).- name
- qdrant-monitoring
- description
- Guides Qdrant monitoring and observability setup. Use when someone asks 'how to monitor Qdrant', 'what metrics to track', 'is Qdrant healthy', 'optimizer stuck', 'why is memory growing', 'requests are slow', 'set up alerts', 'cluster health check', or needs to set up Prometheus, Grafana, health checks, or log centralization. Also use when debugging production issues that require metric analysis.
- allowed-tools
- Read, Grep, Glob
Qdrant Monitoring
Route first, then answer. Match the user's symptom in the table, Read that file, and answer from it.
Do not answer from this page alone: it contains routing only, not the guidance. If two rows match, read both.
| The user says | Read |
|---|---|
| Want to set up Prometheus, Grafana, or health checks | setup/SKILL.md |
| Need to know which metrics to track | setup/SKILL.md |
| Setting up alerting, log centralization, or Hybrid Cloud metrics | setup/SKILL.md |
| Optimizer stuck or running forever | debugging/SKILL.md |
| Memory keeps growing in production | debugging/SKILL.md |
| Requests are slow and I need to find out why | debugging/SKILL.md |
| Is Qdrant healthy right now | debugging/SKILL.md |
Qdrant monitoring tracks performance and health, and catches issues before they become outages. See the metric reference before tuning anything: Monitoring docs
© 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 of qdrant/skills.
Open the folder on GitHubat commit 1780b6d
Compare with similar skills
Qdrant Monitoring 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 Monitoring this skillqdrant/skills | 254 | — | ~368 | Automated safety check: Pass | Apache-2.0 | |
| Qdrant Monitoringgithub/awesome-copilot | 40k | 1 repos | ~276 | Automated safety check: Pass | MIT | |
| Syncmetapawurb/hotpath-rs | 1.9k | — | ~1.2k | Automated safety check: Notes | MIT | |
| Optimize Slurm TopologyNVlabs/alpasim | 1.3k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Dashboard Previewm4r1k/Eneru | 149 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Graftm4r1k/Eneru | 149 | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
Syncmeta
pawurb/hotpath-rs
Sync changes from the hotpath, hotpath-macros and hotpath-drain crates to their meta counterparts (hotpath-meta, hotpath-macros-meta and hotpath-drain-meta).
Optimize Slurm Topology
NVlabs/alpasim
Optimize AlpaSim Slurm topology throughput using persistent local Prometheus/Grafana telemetry and run artifacts.
Dashboard Preview
m4r1k/Eneru
Visually verify Eneru browser-dashboard changes against a live daemon or audit an exact deployment.
Graft
m4r1k/Eneru
This repo is indexed by graft/. An agent skill from m4r1k/Eneru.
Release Review
m4r1k/Eneru
Mandatory pre-release deep review for minor/major releases (X.Y.0 / X.0.0).
More from qdrant/skills
All 33 skills in this repo- Official
Qdrant Clients SDK
qdrant/skills
Qdrant provides client SDKs for various programming languages, allowing easy integration with Qdrant deployments.
- Official
Qdrant Advisor
qdrant/skills
Diagnose, troubleshoot, and advise on any Qdrant deployment by loading the latest official Qdrant skills live from skills.qdrant.tech.
- Official
Qdrant Deployment Options
qdrant/skills
Guides Qdrant deployment selection. An agent skill from qdrant/skills.
- Official
Qdrant Search Strategies
qdrant/skills
Guides Qdrant search strategy selection. An agent skill from qdrant/skills.
- Official
Qdrant Horizontal Scaling
qdrant/skills
Diagnoses and guides Qdrant horizontal scaling decisions. An agent skill from qdrant/skills.
- Official
Qdrant Indexing Performance Optimization
qdrant/skills
Diagnoses and fixes slow Qdrant indexing and data ingestion.
Related
Works with
Categories
Questions about Qdrant Monitoring
What does Qdrant Monitoring do?
Guides Qdrant monitoring and observability setup. An agent skill from qdrant/skills. Qdrant Monitoring is an agent skill from qdrant/skills, published by the product's own GitHub organization. Guides Qdrant monitoring and observability setup.
When should I use Qdrant Monitoring?
Qdrant Monitoring fits situations like: someone asks how to monitor Qdrant; what metrics to track; is Qdrant healthy; optimizer stuck.
How do I install Qdrant Monitoring in Claude Code?
Run `npx skills add qdrant/skills --skill qdrant-monitoring -a claude-code`. Or copy the skill folder (skills/qdrant-monitoring in qdrant/skills) into .claude/skills/qdrant-monitoring in your project. Claude Code loads it when a task matches its description.
How do I install Qdrant Monitoring in Codex?
Run `npx skills add qdrant/skills --skill qdrant-monitoring -a codex`. Or copy the skill folder (skills/qdrant-monitoring in qdrant/skills) into .agents/skills/qdrant-monitoring in your project. Codex loads it when a task matches its description.
Can I use Qdrant Monitoring 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 -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, .gemini/skills/qdrant-monitoring, .github/skills/qdrant-monitoring and .opencode/skills/qdrant-monitoring in your project.
What does Qdrant Monitoring need to run?
SKILL.md names no scripts, command-line tools or credentials: Qdrant Monitoring is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob.
Does Qdrant Monitoring 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 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 use?
Qdrant Monitoring 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 use?
About 368 tokens (SKILL.md is roughly 1.5k 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?
Skills that share tags, products or a category with Qdrant Monitoring: Qdrant Monitoring (github/awesome-copilot, 40k stars), Syncmeta (pawurb/hotpath-rs, 1.9k stars), Optimize Slurm Topology (NVlabs/alpasim, 1.3k stars) and Dashboard Preview (m4r1k/Eneru, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Qdrant Monitoring?
qdrant (a GitHub organization, an official publisher) maintains it in qdrant/skills, which has 254 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 9, 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.