Zilliz Cloud CLI Skill

Zilliz Cloud CLI Skill

Operate Zilliz Cloud through zilliz-cli. All operations are executed via shell commands.

Prerequisite Check (always run first)

Before any operation, verify in order:

# 1. Install or update the CLI
curl -fsSL https://raw.githubusercontent.com/​zilliztech/​zilliz-cli/​master/​install.sh | bash

# 2. Logged in? If not: guide user to login in their terminal
zilliz auth status

# 3. Context set? (only for data-plane ops)
zilliz context current

CRITICAL: zilliz login, zilliz configure, and zilliz auth switch require interactive input — NEVER run them in a non-interactive shell. Instruct the user to run in their own terminal. NEVER ask for API keys in chat.

Command Pattern

zilliz <resource> <action> --flag <value> [--optional-flag <value>]

All commands support --output json|table|text (default: text). Use --output json for programmatic parsing.

Cluster Type Capabilities

Check cluster type first when a command fails with permission errors.

Reference Files

Each reference covers one resource domain with full command syntax, options, and guidance. Read the relevant reference when handling that domain:

Quick-Start Workflow

For new users, guide through setup in order:

1. Install CLI: curl -fsSL https://raw.githubusercontent.com/​zilliztech/​zilliz-cli/​master/​install.sh | bash
2. Authenticate: user runs zilliz login in their terminal
3. Verify: zilliz auth status
4. List clusters: zilliz cluster list
5. Set context: zilliz context set --cluster-id <id>
6. Verify: zilliz context current && zilliz collection list

Common Workflows

Create collection and prepare for search:

1. zilliz collection create --name <name> --dimension <dim> — create
2. zilliz index create --collection <name> — index (AUTOINDEX recommended)
3. zilliz collection load --name <name> — load into memory
4. zilliz vector search --collection <name> --data '[[...]]' — search

Status overview (read references/​monitoring.md):

1. zilliz context current --output json
2. zilliz cluster describe --cluster-id <id> --output json
3. zilliz database list --output json
4. For each DB: collection list, get-stats, get-load-state, index list
5. Present as formatted table

Async Operations

These return immediately with a jobId; track with job describe (see references/​job.md):

Safety Rules

• Confirm before destructive ops: drop collection/​database, delete cluster/​backup, drop user/​role
• Sensitive commands in user's terminal: zilliz login, zilliz configure, zilliz billing bind-card
• Never expose credentials in chat or command output