Update to Zilliz

{
  "description": "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).",
  "included_files": [],
  "name": "quickstart",
  "skill_md_contents": "---\nname: quickstart\ndescription: 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).\n---\n\nGuide the user through the complete Zilliz Cloud CLI setup. Follow these steps in order:\n\n## Step 1: Install zilliz-cli\n\nCheck if already installed:\n\n```bash\nzilliz --version\n```\n\nIf not installed or needs upgrading:\n\n```bash\ncurl -fsSL https://raw.githubusercontent.com/zilliztech/zilliz-cli/master/install.sh | bash\n```\n\nVerify:\n\n```bash\nzilliz --version\n```\n\n## Step 2: Inspect available access\n\nInspect control-plane authentication and the existing data-plane context independently:\n\n```bash\nzilliz auth status\nzilliz context current --output json\n```\n\nIf the requested workflow needs control-plane access and no usable authentication is available, instruct the user to open their own terminal and run one of:\n\n1. **Browser login** — `zilliz login` — opens a browser for OAuth and uses the account's assigned permissions.\n2. **API Key via login** — `zilliz login --api-key` — prompts for API key, no browser needed.\n3. **API Key via configure (legacy)** — `zilliz configure` — prompts for API key, simpler setup.\n4. **Environment variable** — configure `ZILLIZ_API_KEY` with a token supported by the intended API endpoint.\n\n**IMPORTANT:** These commands require interactive input and cannot run inside the agent. Do NOT ask the user to paste API keys into the chat.\n\nDo not require `zilliz auth status` to succeed for a data-plane-only workflow. If an endpoint and context are already available, validate them with `zilliz database list --output json` or `zilliz collection list --output json`.\n\n## Step 3: Resolve the target context\n\nWhen control-plane discovery is available, list clusters:\n\n```bash\nzilliz cluster list --output json\n```\n\nIf discovery is unavailable, ask the user to configure the cluster ID and endpoint in their own terminal. Set an explicit context instead of treating discovery failure as an authentication failure:\n\n```bash\nzilliz context set --cluster-id <cluster-id> --endpoint <endpoint>\nzilliz database list --output json\nzilliz context set --database <database-name>\n```\n\nUse a database returned by the service or an existing database already stored in context. Do not assume its name.\n\n## Step 4: Verify the requested capability\n\nConfirm the data-plane context and perform a non-destructive probe:\n\n```bash\nzilliz context current --output json\nzilliz collection list --output json\n```\n\nIf the user also needs control-plane operations, verify the relevant read command separately. Report which capabilities were verified and which were unavailable without inferring the reason from a service label alone.\n"
}