메뉴
Use when the user wants to create, list, load, release, or drop partitions in a Milvus collection.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
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, delete, suspend, resume, or modify Zilliz Cloud clusters.
Use when the user wants to create, list, describe, drop, rename, load, release, or manage collections and collection aliases in Milvus.
| name | partition |
| description | Use when the user wants to create, list, load, release, or drop partitions in a Milvus collection. |
All partition commands accept an optional --database <db-name> flag. If omitted, the database from the current context is used.
zilliz partition create --collection <collection-name> --partition <partition-name>
# Optional: --database <database-name>
zilliz partition list --collection <collection-name>
# Optional: --database <database-name>
zilliz partition drop --collection <collection-name> --partition <partition-name-to-drop>
# Optional: --database <database-name>
zilliz partition has --collection <collection-name> --partition <partition-name>
# Optional: --database <database-name>
zilliz partition get-stats --collection <collection-name> --partition <partition-name>
# Optional: --database <database-name>
zilliz partition load --collection <collection-name> --names '["partition1", "partition2"]'
# Optional: --database <database-name>
zilliz partition release --collection <collection-name> --names '["partition1", "partition2"]'
# Optional: --database <database-name>
_default partition.