← ZillizCONTENT HISTORY

Update to Zilliz

Snapshot Sep 30, 2026 · 23:15 UTC · version 1.4.4

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when the user wants a comprehensive overview of their current Zilliz Cloud environment — context, cluster details, databases, and collections with stats.",
  "included_files": [],
  "name": "status",
  "skill_md_contents": "---\nname: status\ndescription: Use when the user wants a comprehensive overview of their current Zilliz Cloud environment — context, cluster details, databases, and collections with stats.\n---\n\nGather and display a status overview of the user's current Zilliz Cloud environment. Run commands with `--output json` for structured data, then present a formatted summary.\n\n## Step 1: Inspect current access\n\nVerify the CLI and inspect both authentication surfaces:\n\n```bash\nzilliz --version\nzilliz auth status\nzilliz context current --output json\n```\n\nDo not stop solely because `zilliz auth status` reports no control-plane login. A configured data-plane context may still be usable.\n\n## Step 2: Show Current Context\n\n```bash\nzilliz context current --output json\n```\n\nIf no context is set, suggest running `zilliz context set --cluster-id <id>`.\n\n## Step 3: Optional cluster details\n\nUsing the cluster ID from context:\n\n```bash\nzilliz cluster describe --cluster-id <cluster-id> --output json\n```\n\nIf this command succeeds, present the cluster name, status, plan, and region. If it is unavailable or denied, preserve the error briefly and continue with data-plane status. Do not ask the user to change credentials unless cluster metadata is required for their request.\n\n## Step 4: Database List\n\n```bash\nzilliz database list --output json\n```\n\nIf database listing is unavailable but the context already names a database, continue with that database and mark database discovery as unavailable.\n\n## Step 5: Collections Summary\n\nFor each database returned in Step 4, gather collection information:\n\n```bash\nzilliz collection list --database <db-name> --output json\n```\n\nFor each collection, gather stats and index info:\n\n```bash\nzilliz collection get-stats --name <name> --database <db-name> --output json\nzilliz collection get-load-state --name <name> --database <db-name> --output json\nzilliz index list --collection <name> --database <db-name> --output json\n```\n\n## Step 6: Present Summary\n\nFormat the results as a readable summary:\n\n**Context:** <cluster-id> | <endpoint>\n**Cluster metadata:** <available fields, or unavailable with the current access>\n\nFor each database, show its collections:\n\n**Database:** <db-name>\n\n| Collection | Rows | Load State | Indexes |\n|---|---|---|---|\n| my_collection | 10,000 | Loaded | vector_idx (AUTOINDEX) |\n| ... | ... | ... | ... |\n\nDistinguish verified facts from unavailable metadata. Report successful data-plane checks even when optional control-plane checks fail.\n"
}

SHA-256 of public snapshot: 3868814fe60351ac4c777117fd221b1f2ea82c9addf6fcd2ecb40d22f8e7c3b8