zilliz 1.0.2

TUI and CLI tool for managing Zilliz Cloud clusters and Milvus operations
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180

# Skill configuration: maps JSON model resources to plugin skills.
#
# Each skill entry defines:
#   description:   SKILL.md frontmatter description (trigger text for Claude)
#   resources:     list of {plane, resource} pairs from JSON models
#                  plane: "control" (control-plane.json) or "data" (data-plane.json)
#   prerequisites: markdown text for the Prerequisites section
#   header:        optional text inserted before auto-generated commands
#   hand_written:  if true, skill is fully hand-written (overlay is copied as-is)

skills:
  cluster:
    description: >-
      Use when the user wants to create, list, describe, delete,
      suspend, resume, or modify Zilliz Cloud clusters.
    resources:
      - plane: control
        resource: cluster
    prerequisites: |
      1. CLI installed and logged in (see setup skill).
      2. No cluster context required -- these are control-plane operations.

  collection:
    description: >-
      Use when the user wants to create, list, describe, drop, rename, load,
      release, or manage collections and collection aliases in Milvus.
    resources:
      - plane: data
        resource: collection
      - plane: data
        resource: alias
        section_title: Collection Aliases
    prerequisites: |
      1. CLI installed, logged in, and cluster context set (see setup skill).
    header: >-
      All collection commands accept an optional `--database <db-name>` flag
      to target a non-default database. If omitted, the database from the
      current context is used.

  vector:
    description: >-
      Use when the user wants to search, query, insert, upsert, get, or
      delete vectors in a Milvus collection.
    resources:
      - plane: data
        resource: vector
    prerequisites: |
      1. CLI installed, logged in, and cluster context set (see setup skill).
      2. Target collection must exist and be loaded (see collection skill).
    header: >-
      All vector commands accept an optional `--database <db-name>` flag
      to target a non-default database. If omitted, the database from the
      current context is used.

  database:
    description: >-
      Use when the user wants to create, list, describe, or drop databases
      in Milvus.
    resources:
      - plane: data
        resource: database
    prerequisites: |
      1. CLI installed, logged in, and cluster context set (see setup skill).

  index:
    description: >-
      Use when the user wants to create, list, describe, or drop indexes
      on Milvus collections.
    resources:
      - plane: data
        resource: index
    prerequisites: |
      1. CLI installed, logged in, and cluster context set (see setup skill).
      2. Target collection must exist (see collection skill).
    header: >-
      All index commands accept an optional `--database <db-name>` flag.
      If omitted, the database from the current context is used.

  partition:
    description: >-
      Use when the user wants to create, list, load, release, or drop
      partitions in a Milvus collection.
    resources:
      - plane: data
        resource: partition
    prerequisites: |
      1. CLI installed, logged in, and cluster context set (see setup skill).
      2. Target collection must exist (see collection skill).
    header: >-
      All partition commands accept an optional `--database <db-name>` flag.
      If omitted, the database from the current context is used.

  user-role:
    description: >-
      Use when the user wants to manage database users, roles, passwords,
      or access privileges in Milvus.
    resources:
      - plane: data
        resource: user
        section_title: Users
      - plane: data
        resource: role
        section_title: Roles
    prerequisites: |
      1. CLI installed, logged in, and cluster context set (see setup skill).

  backup:
    description: >-
      Use when the user wants to create, list, describe, delete, export,
      or restore backups, or manage backup policies on Zilliz Cloud.
    resources:
      - plane: control
        resource: backup
    prerequisites: |
      1. CLI installed and logged in (see setup skill).
      2. No cluster context required -- backup operations use `--cluster-id` directly.

  import:
    description: >-
      Use when the user wants to import bulk data into a Milvus collection
      via Zilliz Cloud import jobs.
    resources:
      - plane: control
        resource: import
    prerequisites: |
      1. CLI installed and logged in (see setup skill).
      2. Target collection must exist on the target cluster.

  billing:
    description: >-
      Use when the user wants to check usage, view invoices, or manage
      payment methods on Zilliz Cloud.
    resources:
      - plane: control
        resource: billing
    prerequisites: |
      1. CLI installed and logged in via OAuth (see setup skill).
      2. Billing features require OAuth login -- API Key mode may not have access.

  project-region:
    description: >-
      Use when the user wants to manage Zilliz Cloud projects or storage
      volumes. For cloud regions and providers, see the cluster skill.
    resources:
      - plane: control
        resource: project
        section_title: Projects
      - plane: control
        resource: volume
        section_title: Volumes
    prerequisites: |
      1. CLI installed and logged in (see setup skill).

  job:
    description: >-
      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.
    resources:
      - plane: control
        resource: job
    prerequisites: |
      1. CLI installed and logged in (see setup skill).
      2. A job ID from a previous async operation (backup create, import start, etc.).

  # Fully hand-written skills (no JSON model counterpart)
  setup:
    hand_written: true
    description: >-
      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.
    prerequisites: ""

  monitoring:
    hand_written: true
    description: >-
      Use when the user wants to check cluster status, collection statistics,
      load states, or get an overview of their Zilliz Cloud resources.
    prerequisites: ""