Update to Zilliz

{
  "description": "Use when the user wants to create, list, describe, or drop databases in Milvus.",
  "included_files": [],
  "name": "database",
  "skill_md_contents": "---\nname: database\ndescription: Use when the user wants to create, list, describe, or drop databases in Milvus.\n---\n\n## Prerequisites\n\n1. CLI installed, a usable data-plane credential configured, and cluster context set (see setup skill).\n\n## Commands Reference\n\n### Create a Database\n\n```bash\nzilliz database create --name <database-name>\n# Or use raw JSON: --body '{\"properties\": {}}'\n```\n\nAvailability depends on the current endpoint, credential, and service configuration. Report the CLI or server response without inferring support from a cluster label alone.\n\n### List Databases\n\n```bash\nzilliz database list\n```\n\n### Describe a Database\n\n```bash\nzilliz database describe --name <database-name>\n```\n\nIf details are unavailable, fall back to the information returned by `database list` and the current context.\n\n### Drop a Database\n\n```bash\nzilliz database drop --name <database-name-to-drop>\n```\n\nThis action is destructive. Confirm the exact database and impact immediately before execution.\n\n## Guidance\n\n- Use `database list` and the current context to discover available database names. Do not assume that a database named `default` exists or is accessible.\n- When an operation is rejected, report the returned permission or availability error and continue with independent database capabilities where possible.\n- Before dropping a database, confirm with the user -- all collections in it will be deleted.\n- After creating a database, suggest switching context: `zilliz context set --database <db-name>`.\n- To work with collections in a non-default database, use `--database` flag on collection commands or switch context.\n"
}