Gke Cost Analysis
google/skills
Answer natural language questions and perform analysis on GKE cluster and workload costs using BigQuery billing exports, cost allocation data, and live cluster monitoring metrics.
Setting up and running Qdrant Hybrid Cloud on your own Kubernetes cluster (managed, on-prem, or edge): prerequisites, storage/CSI and backups, installing the Qdrant Cloud agent and operator…
Install Qdrant Hybrid Cloud Setup
$ npx skills add qdrant/skills --skill qdrant-hybrid-cloud-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install qdrant/skills qdrant-hybrid-cloud-setup --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-hybrid-cloud-setup .claude/skills/qdrant-hybrid-cloud-setup && 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-hybrid-cloud-setup" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-hybrid-cloud-setup into .claude/skills/qdrant-hybrid-cloud-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-hybrid-cloud-setup", 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-hybrid-cloud-setupType 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-hybrid-cloud-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install qdrant/skills qdrant-hybrid-cloud-setup --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-hybrid-cloud-setup .agents/skills/qdrant-hybrid-cloud-setup && 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-hybrid-cloud-setup" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-hybrid-cloud-setup into .agents/skills/qdrant-hybrid-cloud-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-hybrid-cloud-setup", 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-hybrid-cloud-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install qdrant/skills qdrant-hybrid-cloud-setup --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-hybrid-cloud-setup .cursor/skills/qdrant-hybrid-cloud-setup && 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-hybrid-cloud-setup" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-hybrid-cloud-setup into .cursor/skills/qdrant-hybrid-cloud-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-hybrid-cloud-setup", 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-hybrid-cloud-setup--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-hybrid-cloud-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install qdrant/skills qdrant-hybrid-cloud-setup --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-hybrid-cloud-setup .gemini/skills/qdrant-hybrid-cloud-setup && 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-hybrid-cloud-setup" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-hybrid-cloud-setup into .gemini/skills/qdrant-hybrid-cloud-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-hybrid-cloud-setup", 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-hybrid-cloud-setupInstalls 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-hybrid-cloud-setup -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-hybrid-cloud-setup .github/skills/qdrant-hybrid-cloud-setup && 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-hybrid-cloud-setup" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-hybrid-cloud-setup into .github/skills/qdrant-hybrid-cloud-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-hybrid-cloud-setup", 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-hybrid-cloud-setup -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-hybrid-cloud-setup --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-hybrid-cloud-setup .opencode/skills/qdrant-hybrid-cloud-setup && 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-hybrid-cloud-setup" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-hybrid-cloud-setup into .opencode/skills/qdrant-hybrid-cloud-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-hybrid-cloud-setup", 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-hybrid-cloud-setup- GitHub stars
- 253
- Token cost
- ~1.7k tokens
- SKILL.md length
- 810 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Setting up and running Qdrant Hybrid Cloud on your own Kubernetes cluster (managed, on-prem, or edge): prerequisites, storage/CSI and backups, installing the Qdrant Cloud agent and operator…
- Someone wants to set up
- SKILL.md covers Preparing the Kubernetes…, Creating the environment, Creating a cluster in the… and Exposing and securing a cluster, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Configure Hybrid Cloud on their own infrastructure
What it does
Qdrant Hybrid Cloud Setup is an agent skill from qdrant/skills, published by the product's own GitHub organization. Setting up and running Qdrant Hybrid Cloud on your own Kubernetes cluster (managed, on-prem, or edge): prerequisites, storage/CSI and backups, installing the Qdrant Cloud agent and operator, creating/exposing/securing clusters, registry mirroring, and secret rotation. Use when someone wants to set up, install, deploy, or configure Hybrid Cloud on their own infrastructure; is running Qdrant on their own EKS, GKE, AKS, OpenShift, or other Kubernetes; asks about the agent or operator, a storage class or volume…
Its SKILL.md is about 1.7k 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 Container orchestration. It works with Qdrant, Kubernetes and Google Kubernetes Engine. 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 wants to set up
- Configure Hybrid Cloud on their own infrastructure
- Is running Qdrant on their own EKS
- Other Kubernetes
Example prompts
- “/qdrant-hybrid-cloud-setup”
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 Hybrid Cloud Setup loads about 1.7k tokens when it runs. Until then it costs about 176 tokens; SKILL.md has 810 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 476a18d, republished under its Apache-2.0 licence (© qdrant). 810 words, ~1,749 tokens.
Download SKILL.mdSave it as
.claude/skills/qdrant-hybrid-cloud-setup/SKILL.md (or your agent's skills folder).- name
- qdrant-hybrid-cloud-setup
- description
- Setting up and running Qdrant Hybrid Cloud on your own Kubernetes cluster (managed, on-prem, or edge): prerequisites, storage/CSI and backups, installing the Qdrant Cloud agent and operator, creating/exposing/securing clusters, registry mirroring, and secret rotation. Use when someone wants to set up, install, deploy, or configure Hybrid Cloud on their own infrastructure; is running Qdrant on their own EKS, GKE, AKS, OpenShift, or other Kubernetes; asks about the agent or operator, a storage class or volume snapshots for Hybrid Cloud, exposing a cluster, mirroring Qdrant images, or rotating secrets; or when a Hybrid Cloud install is failing on storage or connectivity.
Setting Up Qdrant Hybrid Cloud
You've already chosen Hybrid Cloud (managed control plane on your own infra). If you're still deciding, that's the qdrant-deployment-options skill. Most setup failures trace to one of two things: storage (the CSI driver can't do what Qdrant needs) or connectivity (the agent can't reach Qdrant Cloud). Diagnose which before touching anything else.
Preparing the Kubernetes cluster (do this first)
Use when: about to create the environment, or the install/cluster provisioning failed on storage.
- Qdrant needs a block-storage CSI driver. Network storage (NFS) and object storage (S3) are unsupported: a cluster wired to those will fail, not degrade Prerequisites.
- Create the
StorageClass(withallowVolumeExpansion: true) and theVolumeSnapshotClassbeforehand, not after. Without volume expansion you can't grow disk later; without aVolumeSnapshotClassand the CSI snapshot controller you can't take backups. - Any standards-compliant Kubernetes works, and there's platform-specific setup guidance for the managed ones: Akamai (Linode/LKE), AWS (EKS), Civo, DigitalOcean (DOKS), Gcore, GCP (GKE), Azure (AKS), Oracle (OKE), OVHcloud, Red Hat OpenShift, Scaleway, STACKIT, and Vultr Deployment Platforms.
- Platform matters for what storage supports: some (e.g. Linode/LKE, Vultr) don't support CSI volume snapshots at all, so backups are unavailable there. Check your provider's snapshot page and prefer its recommended instance and disk types (e.g. gp3 on EKS, Premium SSD v2 on AKS) before committing.
- Confirm outbound connectivity: the agent opens connections to
grpc.cloud.qdrant.ioandapi.cloud.qdrant.ioon 443. Firewalls/egress proxies block this silently: a "stuck installing" agent is usually this. - You need
cluster-adminpluskubectlandhelmconfigured against the target cluster.
Creating the environment
Use when: running the install wizard in the Cloud Console.
- The Kubernetes namespace is permanent: it's the one choice you can't change later. Everything else (node selectors, tolerations, registry URLs, proxy) is editable after creation, so don't over-think them now.
- The wizard generates a one-time install command that creates secrets and installs the agent + operator via Helm. You only need it for the initial install; updates happen from the Console afterward Setup guide.
- Advanced operator behavior (pod scheduling, security context, ingress, networking, and snapshot management) is tuned in the operator configuration at the environment level, and can be changed after install Operator configuration.
- Air-gapped or registry-restricted? Mirror the
/qdrant/images and/qdrant-charts/charts into your own registry and set the container + chart URLs in the environment's advanced section. Sync all architectures (or the right one) or ARM/x86 nodes will fail to pull.
Creating a cluster in the environment
Use when: the environment exists and you're provisioning a database.
- Pick the Database Storage Class and Volume Snapshot Class here. Setting Volume Snapshot Class to
Nonedisables backups;emptyDirfor the snapshot volume makes it ephemeral (lost on pod restart): deliberate choices, not defaults to accept blindly Cluster creation. - By default Qdrant Cloud reserves ~20% CPU/memory per pod for the OS and system components. Small nodes may need more reserved; large nodes less. Aim for one database pod per node.
- Use node selectors / tolerations / topology spread constraints to keep databases on dedicated nodes and spread across zones.
Show full SKILL.md (307 more words)Show less
Exposing and securing a cluster
Use when: apps outside the Kubernetes cluster need to reach Qdrant, or asked about API keys/TLS.
- Default is a
ClusterIPservice: internal-only, no API key. The moment you expose it (LoadBalancer, NodePort, or Ingress) you MUST configure an API key, supplied as a Kubernetes secret referenced in the cluster config Networking & security. - Internal node-to-node gRPC uses port 6335 and is never protected by API key or TLS. It must never be publicly reachable; Hybrid Cloud ships a NetworkPolicy restricting it, so don't loosen that.
- TLS: offload at the ingress/LB, or terminate in Qdrant via a TLS secret. Don't do both by accident.
Logging
Use when: setting log levels or wiring cluster logs into your stack. (For metrics/Prometheus/Grafana, use the qdrant-monitoring skill instead.)
- Log levels are set in two different places: per-database in the Cluster detail page, but for the Agent and Operator in the Hybrid Cloud Environment config, not per-cluster Networking, Logging & Monitoring.
- Logs are plain pod logs with no Qdrant-specific format. Point any Kubernetes-aware log collector at all pods in the Qdrant namespace; nothing Qdrant-specific to configure.
What NOT to Do
- Provision on NFS, S3, or any non-block storage: it's unsupported and will fail outright, not just run slowly.
- Create the
StorageClass/VolumeSnapshotClass(or enableallowVolumeExpansion) after the fact, then discover you can't scale disk or take backups. They must exist beforehand. - Assume backups "just work" on Linode or Vultr: verify CSI snapshot support for your platform first.
- Expose a cluster via LoadBalancer/Ingress without setting an API key, or leave port 6335 publicly reachable.
- Regenerate the install command (or rotate secrets) and forget to reapply it: the agent-to-Cloud link breaks silently until you do.
- Delete a Hybrid Cloud environment before deleting its clusters: tear down clusters first, then the environment, then run the cleanup script, or you'll strand resources in the cluster.
© 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-hybrid-cloud-setup of qdrant/skills.
Open the folder on GitHubat commit 476a18d
Compare with similar skills
Qdrant Hybrid Cloud Setup 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 Hybrid Cloud Setup this skillqdrant/skills | 253 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Gke Cost Analysisgoogle/skills | 21k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Devopsnicepkg/auto-company | 192 | 2 repos | ~814 | Automated safety check: Pass | MIT | |
| KubeShark for KubernetesLukasNiessen/kubernetes-skill | 444 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Kcli Cluster Deploymentkarmab/kcli | 653 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Aicr Analyzing SnapshotsNVIDIA/aicr | 432 | — | ~3.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Devops
nicepkg/auto-company
Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm).
KubeShark for Kubernetes
LukasNiessen/kubernetes-skill
Keeps Kubernetes manifests, Helm charts and policies grounded by diagnosing six failure modes, such as insecure defaults and API drift, and loading only matching references.
Kcli Cluster Deployment
karmab/kcli
Guides deployment and management of Kubernetes clusters with kcli.
- Official
Aicr Analyzing Snapshots
NVIDIA/aicr
A skill your agent uses when analyzing an AICR snapshot YAML file, reviewing cluster state, comparing provider characteristics, extracting GPU/network topology insights, or generating a cluster…
GCP Gke
sickn33/agentic-awesome-skills
Deploy and manage Google Kubernetes Engine clusters. An agent skill from sickn33/agentic-awesome-skills.
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 Hybrid Cloud Setup
What does Qdrant Hybrid Cloud Setup do?
Setting up and running Qdrant Hybrid Cloud on your own Kubernetes cluster (managed, on-prem, or edge): prerequisites, storage/CSI and backups, installing the Qdrant Cloud agent and operator…. Qdrant Hybrid Cloud Setup is an agent skill from qdrant/skills, published by the product's own GitHub organization. Setting up and running Qdrant Hybrid Cloud on your own Kubernetes cluster (managed, on-prem, or edge): prerequisites, storage/CSI and backups, installing the Qdrant Cloud agent and operator, creating/exposing/securing clusters, registry mirroring, and secret rotation.
When should I use Qdrant Hybrid Cloud Setup?
Qdrant Hybrid Cloud Setup fits situations like: someone wants to set up; configure Hybrid Cloud on their own infrastructure; is running Qdrant on their own EKS; other Kubernetes.
How do I install Qdrant Hybrid Cloud Setup in Claude Code?
Run `npx skills add qdrant/skills --skill qdrant-hybrid-cloud-setup -a claude-code`. Or copy the skill folder (skills/qdrant-hybrid-cloud-setup in qdrant/skills) into .claude/skills/qdrant-hybrid-cloud-setup in your project. Claude Code loads it when a task matches its description.
How do I install Qdrant Hybrid Cloud Setup in Codex?
Run `npx skills add qdrant/skills --skill qdrant-hybrid-cloud-setup -a codex`. Or copy the skill folder (skills/qdrant-hybrid-cloud-setup in qdrant/skills) into .agents/skills/qdrant-hybrid-cloud-setup in your project. Codex loads it when a task matches its description.
Can I use Qdrant Hybrid Cloud Setup 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-hybrid-cloud-setup -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-hybrid-cloud-setup, .gemini/skills/qdrant-hybrid-cloud-setup, .github/skills/qdrant-hybrid-cloud-setup and .opencode/skills/qdrant-hybrid-cloud-setup in your project.
What does Qdrant Hybrid Cloud Setup need to run?
SKILL.md names no scripts, command-line tools or credentials: Qdrant Hybrid Cloud Setup is instructions for the agent only.
Does Qdrant Hybrid Cloud Setup 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 Hybrid Cloud Setup 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 Hybrid Cloud Setup use?
Qdrant Hybrid Cloud Setup 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 Hybrid Cloud Setup use?
About 1.7k tokens (SKILL.md is roughly 7k 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 Hybrid Cloud Setup?
Skills that share tags, products or a category with Qdrant Hybrid Cloud Setup: Gke Cost Analysis (google/skills, 21k stars), Devops (nicepkg/auto-company, 192 stars), KubeShark for Kubernetes (LukasNiessen/kubernetes-skill, 444 stars) and Kcli Cluster Deployment (karmab/kcli, 653 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Qdrant Hybrid Cloud Setup?
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.