zilliztech

Use when the user wants to trigger, describe, or list refresh jobs for an external collection (a collection backed by an external data source such as Vector Lake). Note this is the data-plane refresh workflow, not collection CRUD -- for create/drop/load see the collection skill.

Use when the user wants to manage Zilliz Cloud access control -- custom org or project roles and their policies, granting or revoking a role for an organization member, or binding roles to a SCIM user group. This is cloud-level RBAC over organizations, projects, and clusters -- for database users and privileges inside Milvus see the user-role skill.

Use when the user wants to check the status of an async Cloud Job (backup, restore, migration, import, or clone). Also use when the user wants to wait for a long-running operation to complete.

Use when the user wants to create, list, describe, or drop indexes on Milvus collections.

Use when the user needs to install zilliz-cli, log in to Zilliz Cloud, configure credentials, or set the active cluster context. Also use when any other skill reports a missing prerequisite.

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 import bulk data into a Milvus collection via Zilliz Cloud import jobs, or manage import stages (pre-uploaded file holders that import jobs reference).

Use when the user wants a comprehensive overview of their current Zilliz Cloud environment — context, cluster details, databases, and collections with stats.

Use when the user wants to search, query, insert, upsert, get, or delete vectors in a Milvus collection.

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, or drop databases in Milvus.

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

Use when the user wants to create, list, load, release, or drop partitions in a Milvus collection.

Use when the user wants to manage database users, roles, passwords, or access privileges in Milvus.

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, drop, rename, load, release, or manage collections and collection aliases in Milvus.

Use when the user wants to check cluster status, collection statistics, load states, or get an overview of their Zilliz Cloud resources.

Use when the user wants to set up, install, authenticate, or configure the Zilliz Cloud CLI and cluster context for the first time (one-shot onboarding).

Use when the user wants to list available PrivateLink endpoint services, list/create/delete PrivateLink endpoints for a project, or manage the endpoint whitelist on Zilliz Cloud.

Use when the user wants to manage Zilliz Cloud projects or storage volumes. For cloud regions and providers, see the cluster skill.

Use when the user wants to create, list, describe, or delete an on-demand (Vector Lake / VectorLake) cluster. On-demand clusters auto-suspend after an idle TTL and are intended for ad-hoc query workloads against a Vector Lake.

Diagnose and configure MemSearch memory behavior. Use when the user asks about MemSearch configuration, plugin summarization, PROJECT.md/USER.md maintenance, memory directories, index health, provider routing, prompt files, or migration/compatibility questions.

Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this before'. Also use when you see `[memsearch] Recall available if needed` capability hints injected via SessionStart or UserPromptSubmit. Typical flow: search for 3-5 chunks, expand the most relevant, optionally deep-drill into original transcripts via the anchor format. Skip when the question is purely about current code state (use Read/Grep), ephemeral (today's task only), or the user has explicitly asked to ignore memory.