Menu
Use when the user wants to create, list, describe, delete, suspend, resume, or modify Zilliz Cloud clusters.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when the user reports that a Zilliz Cloud cluster or Milvus collection is unhealthy, slow, stuck, returning errors, hitting quotas, or otherwise misbehaving — or when they ask "what's wrong with...", "why is ... slow", "diagnose ...", "troubleshoot ...".
Zilliz Cloud onboarding and usage assistant. Helps users understand Zilliz Cloud, choose the right plan, estimate costs, write code, debug issues, and adopt new features like Functions, Volumes, and Global Clusters. Use this skill whenever the user asks about Zilliz Cloud — including plan selection, pricing, cost estimation, capacity planning, cluster configuration, SDK usage, schema design, search patterns, migration, troubleshooting, MCP server setup, Terraform, auto-scaling, metrics/alerts, backup/restore, or any "how do I do X with Zilliz Cloud" question. Also trigger when the user mentions keywords like: "Zilliz", "zilliz cloud", "vector database", "which plan", "serverless vs dedicated", "CU", "vCU", "Milvus cloud", "pymilvus", "collection", "embedding function", "hybrid search", "rerank", "BM25", "global cluster", "BYOC", "tiered storage", "volume", "data import", "MCP server", "partition key", or error messages from Zilliz Cloud.
Use when the user wants to create, list, describe, delete, export, or restore backups, or manage backup policies on Zilliz Cloud.
Use when the user wants to check usage, view invoices, or manage payment methods on Zilliz Cloud.
Use when the user wants to create, list, describe, drop, rename, load, release, or manage collections and collection aliases in Milvus.
Use when the user wants to create, list, describe, or drop databases in Milvus.
| name | cluster |
| description | Use when the user wants to create, list, describe, delete, suspend, resume, or modify Zilliz Cloud clusters. |
# Serverless cluster
zilliz cluster create \
--name <cluster-name> \
--type serverless \
--project-id <project-id> \
--region <region-id>
# Free-tier cluster
zilliz cluster create \
--name <cluster-name> \
--type free \
--project-id <project-id> \
--region <region-id>
# Dedicated cluster
zilliz cluster create \
--name <cluster-name> \
--type dedicated \
--project-id <project-id> \
--region <region-id> \
--cu-type <Performance-optimized|Capacity-optimized> \
--cu-size <cu-size>
To find available project IDs, cloud providers, and regions:
zilliz project list
zilliz cluster providers
zilliz cluster regions --cloud-id <aws|gcp|azure>
A Vector Lake (sometimes called a "VectorLake" cluster) is the storage layer
that on-demand clusters attach to (see the on-demand-cluster skill). It is
created via a hand-written subcommand calling
POST /v2/clusters/createVectorLake:
zilliz cluster create-vectorlake \
--project-id <project-id> \
--region-id <region-id> \
[--session-ttl <duration>] \ # idle auto-suspend TTL, min 60s
[--max-query-node-cu <integer>] \
[--max-query-node-replicas <integer>]
After the Vector Lake is RUNNING, attach a query workload with
zilliz on-demand-cluster create --project-id <id> --region-id <region> --cu-size <n> --cluster-name <name>.
zilliz cluster list
# Optional: --region-id <filter-by-region-id>
# Pagination: --page-size <n> --page <n>
# Fetch all pages: --all
zilliz cluster describe --cluster-id <cluster-id>
zilliz cluster modify --cluster-id <cluster-id-to-modify>
# Optional: --cu-size <number-of-compute-units>, --replica <number-of-replicas>
# Or use raw JSON: --body '{"cuSize": 2, "replica": 2}'
zilliz cluster suspend --cluster-id <cluster-id-to-suspend>
zilliz cluster resume --cluster-id <cluster-id-to-resume>
zilliz cluster delete --cluster-id <cluster-id-to-delete>
zilliz cluster providers
zilliz cluster regions
# Optional: --cloud-id <aws|gcp|azure>
zilliz cluster providers and zilliz cluster regions.cluster create, the cluster status will be CREATING. Poll with zilliz cluster describe --cluster-id <id> until the status becomes RUNNING before proceeding with data-plane operations.zilliz context set --cluster-id <id>.cluster create-vectorlake creates a Vector Lake storage instance, not a regular cluster. Query workloads against it run on on-demand clusters (see the on-demand-cluster skill). Do not pass --type to this subcommand; it has its own dedicated parameter set.cluster list supports a --region-id <region> filter for scoping to a single region.