@metabase/cli 0.1.5 → 0.1.7

package/skill-data/viz/references/settings.md

@@ -0,0 +1,312 @@
+# visualization_settings — full key catalog
+
+Exhaustive reference for `visualization_settings`. The SKILL.md body covers the
+common cases; this file is the long tail. Keys are grouped by the `display` they
+apply to (see the display → namespace map in the body).
+
+**Form note.** Every key name and value enum below is identical in the API/numeric
+form (`mb card create`) and the portable git-sync YAML form. The only form-specific
+constructs are (1) `column_settings` `["ref", …]` keys, where the inner field id is
+numeric in the API form and a name-path in the portable form, and (2) click-behavior
+dimension targets, same rule. All the column-naming keys (`graph.dimensions`,
+`pie.dimension`, `table.columns[].name`, …) are output column-name strings in both.
+
+JSON-body reminder: examples here are shown as YAML/JSON fragments. In a real
+`--body`/`--file` JSON payload, `column_settings` keys are JSON **strings** with
+escaped inner quotes: `"[\"name\",\"TOTAL\"]"`.
+
+---
+
+## Common
+
+| Setting               | Type    | Description                                                         |
+| --------------------- | ------- | ------------------------------------------------------------------- |
+| `column_settings`     | map     | Per-column formatting, keyed by column-reference string (see below) |
+| `card.title`          | string  | Override the card's display title on a dashboard                    |
+| `card.description`    | string  | Override the description                                            |
+| `dashcard.background` | boolean | Show/hide the dashcard background (dashcards only)                  |
+
+## Graph (`bar`, `line`, `area`, `combo`, `scatter`, `waterfall`, `row`, `boxplot`)
+
+| Setting                                 | Type           | Values / notes                                                           |
+| --------------------------------------- | -------------- | ------------------------------------------------------------------------ |
+| `graph.dimensions`                      | array          | Dimension (x-axis) output column names                                   |
+| `graph.metrics`                         | array          | Metric (y-axis) output column names                                      |
+| `graph.series_order`                    | array          | Explicit series display order                                            |
+| `graph.show_values`                     | boolean        | Show value labels on data points                                         |
+| `graph.label_values_frequency`          | string         | `"fit"`, `"all"`                                                         |
+| `graph.show_stack_values`               | string         | `"total"`, `"individual"`, `"all"`                                       |
+| `graph.x_axis.title_text`               | string         | X-axis title                                                             |
+| `graph.x_axis.scale`                    | string         | `"ordinal"`, `"histogram"`, `"timeseries"`, `"linear"`, `"pow"`, `"log"` |
+| `graph.x_axis.axis_enabled`             | boolean/string | `true`, `false`, `"compact"`, `"rotate-45"`, `"rotate-90"`               |
+| `graph.y_axis.title_text`               | string         | Y-axis title                                                             |
+| `graph.y_axis.scale`                    | string         | `"linear"`, `"pow"`, `"log"`                                             |
+| `graph.y_axis.auto_range`               | boolean        | Auto-scale Y axis                                                        |
+| `graph.y_axis.min` / `graph.y_axis.max` | number         | Y bounds when `auto_range` is false                                      |
+| `graph.show_goal`                       | boolean        | Show goal line                                                           |
+| `graph.goal_value`                      | number         | Goal line value                                                          |
+| `graph.goal_label`                      | string         | Goal line label                                                          |
+| `graph.show_trendline`                  | boolean        | Show trend line                                                          |
+| `graph.max_categories_enabled`          | boolean        | Limit number of categories                                               |
+| `graph.max_categories`                  | number         | Maximum categories shown                                                 |
+| `graph.other_category_aggregation_fn`   | string         | `"sum"`, `"avg"`, `"min"`, `"max"`                                       |
+| `stackable.stack_type`                  | string         | `null`, `"stacked"`, `"normalized"`                                      |
+
+### Series settings
+
+Per-series overrides keyed by series name (the metric column name, or the breakout
+value for a split series):
+
+```yaml
+series_settings:
+  Revenue:
+    display: line # override this series' type in a combo chart
+    color: "#509EE3"
+    "line.style": solid # "solid", "dashed", "dotted"
+    "line.size": normal # "S", "M", "L"
+    "line.interpolate": linear # "linear", "cardinal", "step-before", "step-after"
+    "line.missing": interpolate # "interpolate", "zero", "none"
+    "line.marker_enabled": true
+    axis: left # "left", "right"
+    show_series_values: true
+```
+
+### Waterfall extras (`display: waterfall`)
+
+| Setting                    | Type    | Description             |
+| -------------------------- | ------- | ----------------------- |
+| `waterfall.increase_color` | string  | Color for increases     |
+| `waterfall.decrease_color` | string  | Color for decreases     |
+| `waterfall.total_color`    | string  | Color for the total bar |
+| `waterfall.show_total`     | boolean | Show the total bar      |
+
+### BoxPlot extras (`display: boxplot`)
+
+| Setting                | Type    | Values                                 |
+| ---------------------- | ------- | -------------------------------------- |
+| `boxplot.whisker_type` | string  | `"min-max"`, `"tukey"`, `"percentile"` |
+| `boxplot.points_mode`  | string  | `"none"`, `"outliers"`, `"all"`        |
+| `boxplot.show_mean`    | boolean | Show mean marker                       |
+
+## Pie (`display: pie`)
+
+| Setting                  | Type    | Values                                    |
+| ------------------------ | ------- | ----------------------------------------- |
+| `pie.dimension`          | string  | Dimension column name                     |
+| `pie.metric`             | string  | Metric column name                        |
+| `pie.show_legend`        | boolean |                                           |
+| `pie.show_total`         | boolean | Show total in center                      |
+| `pie.percent_visibility` | string  | `"off"`, `"legend"`, `"inside"`, `"both"` |
+| `pie.slice_threshold`    | number  | Min percentage to show as its own slice   |
+| `pie.colors`             | object  | Color map keyed by dimension value        |
+
+## Scalar / Number (`display: scalar`, `number`)
+
+| Setting                           | Type    | Values                          |
+| --------------------------------- | ------- | ------------------------------- |
+| `scalar.field`                    | string  | Output column to display        |
+| `scalar.switch_positive_negative` | boolean | Invert positive/negative colors |
+| `scalar.compact_primary_number`   | string  | `"auto"`, `"yes"`, `"no"`       |
+
+### Smart scalar (`display: smartscalar`)
+
+```yaml
+scalar.comparisons:
+  - id: comp1
+    type: previousPeriod # vs. previous time period
+  - id: comp2
+    type: previousValue # vs. previous value
+  - id: comp3
+    type: periodsAgo # vs. N periods ago
+    value: 12
+  - id: comp4
+    type: staticNumber # vs. fixed number
+    value: 1000
+    label: Target
+```
+
+## Funnel (`display: funnel`)
+
+| Setting            | Type   | Values                |
+| ------------------ | ------ | --------------------- |
+| `funnel.dimension` | string | Dimension column      |
+| `funnel.metric`    | string | Metric column         |
+| `funnel.type`      | string | `"funnel"` or `"bar"` |
+| `funnel.rows`      | array  | Row order definitions |
+
+## Gauge (`display: gauge`)
+
+| Setting                | Type  | Description                                 |
+| ---------------------- | ----- | ------------------------------------------- |
+| `gauge.segments`       | array | Segments, each `{ min, max, color, label }` |
+| `gauge.segment_colors` | array | Segment colors                              |
+
+## Map (`display: map`)
+
+| Setting                                        | Type   | Values                           |
+| ---------------------------------------------- | ------ | -------------------------------- |
+| `map.type`                                     | string | `"region"`, `"pin"`, `"grid"`    |
+| `map.latitude_column`                          | string | Latitude column name             |
+| `map.longitude_column`                         | string | Longitude column name            |
+| `map.metric_column`                            | string | Metric column for coloring       |
+| `map.region`                                   | string | Region map identifier            |
+| `map.pin_type`                                 | string | `"tiles"`, `"markers"`, `"heat"` |
+| `map.colors`                                   | array  | Color scale                      |
+| `map.zoom`                                     | number | Initial zoom level               |
+| `map.center_latitude` / `map.center_longitude` | number | Map center                       |
+
+## Table (`display: table`)
+
+| Setting                   | Type    | Description                                               |
+| ------------------------- | ------- | --------------------------------------------------------- |
+| `table.columns`           | array   | Column order + visibility; each entry `{ name, enabled }` |
+| `table.column_formatting` | array   | Conditional formatting rules (see below)                  |
+| `table.pivot`             | boolean | Enable in-table pivot mode                                |
+| `table.pivot_column`      | string  | Column to pivot on                                        |
+| `table.cell_column`       | string  | Column used for cell values (pivot mode)                  |
+
+### Conditional formatting (`table.column_formatting`)
+
+```yaml
+table.column_formatting:
+  - columns: [Total]
+    type: single # "single" or "range"
+    operator: ">" # "=", "!=", "<", ">", "<=", ">=", "is-null", "not-null"
+    value: 100
+    color: "#84BB4C"
+    highlight_row: false
+  - columns: [Rating]
+    type: range
+    colors: ["#ED6E6E", "#F9CF48", "#84BB4C"]
+    min_type: custom # "min", "max", "custom"
+    min_value: 1
+    max_type: custom
+    max_value: 5
+```
+
+## Pivot table (`display: pivot`)
+
+| Setting                          | Type    | Description                                                     |
+| -------------------------------- | ------- | --------------------------------------------------------------- |
+| `pivot_table.column_split`       | object  | `{ rows: [...names], columns: [...names], values: [...names] }` |
+| `pivot_table.collapsed_rows`     | object  | `{ rows: [...collapsed_keys], value: [] }`                      |
+| `pivot_table.show_row_totals`    | boolean |                                                                 |
+| `pivot_table.show_column_totals` | boolean |                                                                 |
+
+## Sankey (`display: sankey`)
+
+| Setting                   | Type    | Values                                       |
+| ------------------------- | ------- | -------------------------------------------- |
+| `sankey.source`           | string  | Source column                                |
+| `sankey.target`           | string  | Target column                                |
+| `sankey.value`            | string  | Value column                                 |
+| `sankey.node_align`       | string  | `"left"`, `"right"`, `"center"`, `"justify"` |
+| `sankey.show_edge_labels` | boolean |                                              |
+
+## Column settings
+
+`column_settings` is keyed by a JSON-encoded column reference. Prefer the
+`["name", "<output column name>"]` form — it is the canonical key Metabase writes and
+is identical across forms. The `["ref", ["field", <id>, <opts>]]` form uses the
+**legacy** field-ref order (id second); in the API form `<id>` is the numeric field id.
+
+Per-column keys (apply under any column key):
+
+| Key                 | Type        | Values                                                 |
+| ------------------- | ----------- | ------------------------------------------------------ |
+| `column_title`      | string      | Override the column header                             |
+| `number_style`      | string      | `"decimal"`, `"currency"`, `"percent"`, `"scientific"` |
+| `currency`          | string      | ISO code, e.g. `"USD"`                                 |
+| `currency_style`    | string      | `"symbol"`, `"code"`, `"name"`                         |
+| `number_separators` | string      | e.g. `".,"` (decimal + thousands)                      |
+| `decimals`          | number      | Fixed decimal places                                   |
+| `scale`             | number      | Multiply values by this factor                         |
+| `prefix` / `suffix` | string      | Affixes around the value                               |
+| `date_style`        | string      | moment.js format, e.g. `"MMMM D, YYYY"`                |
+| `date_separator`    | string      | e.g. `"/"`                                             |
+| `date_abbreviate`   | boolean     |                                                        |
+| `time_enabled`      | string/null | `null`, `"minutes"`, `"seconds"`, `"milliseconds"`     |
+| `time_style`        | string      | e.g. `"HH:mm"`, `"h:mm A"`                             |
+| `view_as`           | string      | `"link"`, `"image"`, `"email"`, `"auto"`               |
+| `link_text`         | string      | Display text when `view_as: link`                      |
+| `link_url`          | string      | URL template; `{{value}}` interpolates the cell value  |
+| `click_behavior`    | object      | Per-column click behavior (see below)                  |
+
+```yaml
+column_settings:
+  '["name","TOTAL"]':
+    number_style: currency
+    currency: USD
+    currency_style: symbol
+    decimals: 2
+    column_title: "Total Revenue"
+  '["name","CREATED_AT"]':
+    date_style: "MMMM D, YYYY"
+    time_enabled: null
+  '["name","EMAIL"]':
+    view_as: link
+    link_text: "Send email"
+    link_url: "mailto:{{value}}"
+```
+
+## Virtual card settings (dashcards only, `card_id: null`)
+
+| `virtual_card.display` | Extra keys                                                                                                        |
+| ---------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| `heading`              | `text` (the heading string)                                                                                       |
+| `text`                 | `text` (markdown; `{{param}}` placeholders wired via dashcard `parameter_mappings`, target `[text-tag, name]`)    |
+| `link`                 | `link.url`, or `link.entity` `{ id, model }` where model ∈ `question`/`dashboard`/`collection`/`database`/`table` |
+| `iframe`               | `iframe` (the `<iframe …>` HTML string)                                                                           |
+| `placeholder`          | —                                                                                                                 |
+
+```yaml
+visualization_settings:
+  virtual_card:
+    display: text
+  text: "**Bold** and _italic_ markdown content"
+```
+
+## Click behavior
+
+Stored at `visualization_settings.click_behavior` (whole dashcard) or per column at
+`column_settings[<key>].click_behavior`.
+
+| `type`        | Description                                  |
+| ------------- | -------------------------------------------- |
+| `actionMenu`  | Default drill-through menu (no config)       |
+| `crossfilter` | Filter the dashboard using the clicked value |
+| `link`        | Navigate to a URL, question, or dashboard    |
+
+```yaml
+# Link to URL — {{column}} = clicked row value, {{filter:param}} = dashboard parameter
+click_behavior:
+  type: link
+  linkType: url
+  linkTemplate: "https://example.com/orders/{{ORDER_ID}}?status={{filter:status}}"
+  linkTextTemplate: "View Order {{ORDER_ID}}"
+
+# Link to another dashboard/question — targetId is the entity_id of the target
+click_behavior:
+  type: link
+  linkType: dashboard            # or "question"
+  targetId: Q_jD-f-9clKLFZ2TfUG2h
+  parameterMapping:
+    target-param-uuid:
+      id: target-param-uuid
+      source: { id: USER_ID, name: User ID, type: column }
+      target: { id: target-param-uuid, type: parameter }
+
+# Crossfilter — map a clicked column to dashboard parameters
+click_behavior:
+  type: crossfilter
+  parameterMapping:
+    param-uuid:
+      id: param-uuid
+      source: { id: CATEGORY, name: Category, type: column }
+      target: { id: param-uuid, type: parameter }
+```
+
+`parameterMapping` entries: `source` is where the value comes from
+(`{ id, name, type }`, type `"column"`/`"parameter"`); `target` is where it goes
+(`{ id, type }`, type `"parameter"`/`"dimension"`/`"variable"`). A `dimension` target
+carries a `dimension` array — the same target shape as a dashboard parameter mapping.

package/skill-data/workspace/SKILL.md

@@ -76,8 +76,7 @@ fi
 WS_ID=$(mb workspace create --name "$WS_NAME" --profile "$PARENT" --json | jq -r '.id')
 
 # 2. Provision a database into it (blocks on :provisioned)
-mb workspace database provision "$WS_ID" \
-  --database-id "$DB_ID" \
+mb workspace database provision "$WS_ID" "$DB_ID" \
   --schemas "$SCHEMAS" \
   --wait \
   --profile "$PARENT"
@@ -91,11 +90,10 @@ mb workspace start "$WS_ID" --wait --profile "$PARENT" "${REPO_FLAGS[@]}"
 #    This is the documented exception to "the agent doesn't run auth login" — the child
 #    key was minted by the parent the human authorized, and reading it via
 #    `workspace credentials` is the supported path.
-WS_URL=$(mb workspace url "$WS_ID" --profile "$PARENT" --json | jq -r '.url')
-WS_API_KEY=$(mb workspace credentials "$WS_ID" --profile "$PARENT" --json | jq -r '.api_key')
+WS_URL=$(mb workspace url "$WS_ID" --json | jq -r '.url')
+WS_API_KEY=$(mb workspace credentials "$WS_ID" --json | jq -r '.api_key')
 printf '%s' "$WS_API_KEY" | mb auth login \
   --url "$WS_URL" \
-  --api-key-stdin \
   --profile "$WS_NAME" \
   --json
 
@@ -106,24 +104,12 @@ mb database list --profile "$WS_NAME" --json
 mb setting get remote-sync-url --profile "$WS_NAME" --json    # → "file:///mnt/repo"
 mb git-sync status --profile "$WS_NAME" --json                # → branch, dirty, current task
 
-# 7. (If REPO_FLAGS was set) Ensure the repo has been applied to the fresh workspace.
-#    The container's boot-time auto-import usually handles this on its own, so check
-#    `git-sync status` first — if `current_task` already shows a successful `import` for
-#    the current branch, skip the explicit call (it's a no-op round-trip).
-#    Only when the auto-import hasn't landed yet do you need an explicit import.
-#    The first explicit import on a fresh instance can spuriously report
-#    `status: conflict` (stale task state from the boot-time import); retry once,
-#    then `--force` is safe because the workspace is empty (nothing to lose).
-#    Skipping the import entirely is *not* safe — without it the instance has none
-#    of the repo content and subsequent edits will diverge.
-HOST_BRANCH=$(git -C "$(pwd)" symbolic-ref --short HEAD)
-SYNC_STATUS=$(mb git-sync status --profile "$WS_NAME" --json)
-if ! echo "$SYNC_STATUS" | jq -e --arg b "$HOST_BRANCH" \
-     '.current_task.sync_task_type == "import" and .current_task.status == "successful" and (.branch == $b)' >/dev/null; then
-  mb git-sync import --branch "$HOST_BRANCH" --profile "$WS_NAME" --json \
-    || mb git-sync import --branch "$HOST_BRANCH" --profile "$WS_NAME" --json \
-    || mb git-sync import --branch "$HOST_BRANCH" --force --profile "$WS_NAME" --json
-fi
+# 7. (If REPO_FLAGS was set) Apply the repo to the fresh workspace. The container's
+#    boot-time auto-import usually handles this — the step-6 `git-sync status` shows
+#    whether it landed. If `current_task` is not a successful `import` for the host
+#    branch, run an explicit import. The status-check + retry-then-force guard lives
+#    in the git-sync skill, "First import on a fresh workspace". Skipping the import is
+#    *not* safe — without it the instance has none of the repo content and edits diverge.
 ```
 
 After step 5, drive the child via `mb <verb> --profile $WS_NAME` for everything (cards, transforms, queries, …). To author a transform on the workspace, load the `transform` skill (`mb skills get transform`). To use the sync flow (import host commits, export instance changes), load the `git-sync` skill (`mb skills get git-sync`).
@@ -145,13 +131,13 @@ Don't run `auth login` for them and don't suggest a URL — they pick. Verify wi
 ### 2. License
 
 ```bash
-mb license status --profile <parent> --json
+mb workspace license status --json
 ```
 
 If `present: false`, ask the operator to run, themselves:
 
 ```bash
-echo "<your-token>" | mb license set --profile <parent>
+echo "<your-token>" | mb workspace license set
 ```
 
 A workspace child cannot start without a parent license — it inherits feature gates from the parent.
@@ -192,8 +178,7 @@ mb table list --db-id <db-id> --profile <parent> --json \
 Provision (one db per call; `--schemas` is required, no "all" wildcard):
 
 ```bash
-mb workspace database provision <ws-id> \
-  --database-id <db-id> \
+mb workspace database provision <ws-id> <db-id> \
   --schemas <schema1>,<schema2> \
   --wait \
   --profile <parent>
@@ -219,7 +204,7 @@ Before running `start`, ask the user about Remote Sync (see "Always ask about Re
 Despite the `--port` flag's "auto-shifts up if taken" hint, in practice `workspace start` fails with `docker start failed for metabase-workspace-<id>` when the host port is occupied — typically by a stale workspace container from a prior session. **List local containers first** and pass an explicit free `--port`:
 
 ```bash
-mb workspace ps --profile <parent>          # → currently-running workspace containers + their host ports
+mb workspace ps          # → currently-running workspace containers + their host ports
 docker ps --filter "name=metabase-workspace" \
   --format "{{.Names}}\t{{.Ports}}\t{{.Status}}"  # also surfaces stopped containers
 ```
@@ -239,17 +224,15 @@ mb workspace start <ws-id> --repo /path/to/repo --repo-branch dev --repo-mode re
 
 `--wait` blocks until `state: "running"`. Don't omit it for interactive bring-up — without it the next step (saving credentials as a child profile) races the container's HTTP listener and you'll get spurious connection errors.
 
-| Flag                   | Purpose                                                                                                                                                                                                                                                                                                                      |
-| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--port <n>`           | Host port (default 3000; **does not** auto-shift reliably — pass an explicit free port if 3000 might be taken).                                                                                                                                                                                                              |
-| `--wait`               | Block until `/api/health` reports ready before returning.                                                                                                                                                                                                                                                                    |
-| `--no-pull`            | Skip `docker pull` (image already present).                                                                                                                                                                                                                                                                                  |
-| `--no-metadata`        | Skip the warehouse metadata export.                                                                                                                                                                                                                                                                                          |
-| `--force`              | Recreate even if a container for this workspace exists. Preserves the app db.                                                                                                                                                                                                                                                |
-| `--timeout <ms>`       | Per-phase readiness deadline (default 240000). Covers the post-create config-consumption wait, (with `--wait`) the `/api/health` probe, and (with `--metadata`) the metadata-import status poll on the child. Bump if the first cold boot exceeds the default — image pull + JVM startup can stretch on slow disks/networks. |
-| `--repo <host-path>`   | Bind-mount a host directory at `/mnt/repo` and inject `remote-sync-url=file:///mnt/repo` into config.yml.                                                                                                                                                                                                                    |
-| `--repo-branch <name>` | `remote-sync-branch` value. Default: current branch of the host repo (`git symbolic-ref --short HEAD`).                                                                                                                                                                                                                      |
-| `--repo-mode <mode>`   | `read-write` (default) or `read-only`. Also flips the bind mount's mount mode.                                                                                                                                                                                                                                               |
+- `--port <n>` — host port (default 3000; **does not** auto-shift reliably — pass an explicit free port if 3000 might be taken).
+- `--wait` — block until `/api/health` reports ready before returning.
+- `--no-pull` — skip `docker pull` (image already present).
+- `--no-metadata` — skip the warehouse metadata export.
+- `--force` — recreate even if a container for this workspace exists. Preserves the app db.
+- `--timeout <ms>` — per-phase readiness deadline (default 240000). Covers the post-create config-consumption wait, (with `--wait`) the `/api/health` probe, and (with `--metadata`) the metadata-import status poll on the child. Bump if the first cold boot exceeds the default — image pull + JVM startup can stretch on slow disks/networks.
+- `--repo <host-path>` — bind-mount a host directory at `/mnt/repo` and inject `remote-sync-url=file:///mnt/repo` into config.yml.
+- `--repo-branch <name>` — `remote-sync-branch` value. Default: current branch of the host repo (`git symbolic-ref --short HEAD`).
+- `--repo-mode <mode>` — `read-write` (default) or `read-only`. Also flips the bind mount's mount mode.
 
 **Notes on `--repo`:**
 
@@ -264,21 +247,20 @@ mb workspace start <ws-id> --repo /path/to/repo --repo-branch dev --repo-mode re
 `url` and `credentials` both return JSON envelopes. Extract fields with `jq`:
 
 ```bash
-mb workspace url <ws-id> --profile <parent> --json
+mb workspace url <ws-id> --json
 # → {"workspace_id": ..., "url": "http://localhost:3000"}
 
-mb workspace credentials <ws-id> --profile <parent> --json
+mb workspace credentials <ws-id> --json
 # → {"email": ..., "password": ..., "api_key": ...}
 ```
 
 Save the child's API key as its own named profile. **Always pipe the key on stdin** (the CLI rejects `--api-key "$VAR"`).
 
 ```bash
-WS_URL=$(mb workspace url <ws-id> --profile <parent> --json | jq -r '.url')
-WS_API_KEY=$(mb workspace credentials <ws-id> --profile <parent> --json | jq -r '.api_key')
+WS_URL=$(mb workspace url <ws-id> --json | jq -r '.url')
+WS_API_KEY=$(mb workspace credentials <ws-id> --json | jq -r '.api_key')
 printf '%s' "$WS_API_KEY" | mb auth login \
   --url "$WS_URL" \
-  --api-key-stdin \
   --profile <ws-name> \
   --json
 ```
@@ -306,18 +288,18 @@ Log in with the **admin email + password** from `workspace credentials` (the API
 
 ## Lifecycle
 
-| User intent                       | Command                                                              |
-| --------------------------------- | -------------------------------------------------------------------- |
-| List local workspace containers   | `mb workspace ps --profile <parent>`                                 |
-| Tail logs                         | `mb workspace logs <ws-id> --tail 200 --profile <parent>`            |
-| Follow logs                       | `mb workspace logs <ws-id> --follow --profile <parent>`              |
-| Read admin email/password/API key | `mb workspace credentials <ws-id> --profile <parent> --json`         |
-| Stop (preserves app db)           | `mb workspace stop <ws-id> --profile <parent>`                       |
-| Restart                           | `mb workspace start <ws-id> --force --wait --profile <parent>`       |
-| Remove container + app db         | `mb workspace remove <ws-id> --yes --profile <parent>`               |
-| Remove container, keep app db     | `mb workspace remove <ws-id> --keep-volume --yes --profile <parent>` |
+| User intent                       | Command                                                        |
+| --------------------------------- | -------------------------------------------------------------- |
+| List local workspace containers   | `mb workspace ps`                                              |
+| Tail logs                         | `mb workspace logs <ws-id> --tail 200`                         |
+| Follow logs                       | `mb workspace logs <ws-id> --follow`                           |
+| Read admin email/password/API key | `mb workspace credentials <ws-id> --json`                      |
+| Stop (preserves app db)           | `mb workspace stop <ws-id>`                                    |
+| Restart                           | `mb workspace start <ws-id> --force --wait --profile <parent>` |
+| Remove container + app db         | `mb workspace delete <ws-id> --yes`                            |
+| Remove container, keep app db     | `mb workspace delete <ws-id> --keep-volume --yes`              |
 
-The supported restart path is `stop` + `start --force` (or `start --force` directly). The app db volume persists across `stop`/`start` cycles, so users/sessions/saved questions survive. `remove`, `start --force`, and `stop` are destructive enough to confirm before running unless the user explicitly asked for them.
+The supported restart path is `stop` + `start --force` (or `start --force` directly). The app db volume persists across `stop`/`start` cycles, so users/sessions/saved questions survive. `delete`, `start --force`, and `stop` are destructive enough to confirm before running unless the user explicitly asked for them.
 
 ## Diagnose
 
@@ -326,14 +308,14 @@ Pick the symptom.
 ### `start` succeeds but the database isn't visible in the UI
 
 ```bash
-mb workspace logs <ws-id> --tail 300 --profile <parent> | grep -iE "advanced-config|workspace|error"
+mb workspace logs <ws-id> --tail 300 | grep -iE "advanced-config|workspace|error"
 ```
 
 | Log signal                                                       | Cause                                                             | Fix                                                                                                                         |
 | ---------------------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
 | `Spec assertion failed ... :input ... :output`                   | Parent emits keys the child's spec doesn't accept (server-side).  | File against the parent. Not a CLI issue.                                                                                   |
 | `Connection refused` / `unknown host` against the warehouse host | Container can't reach the source DB.                              | Source DB credentials configured on the parent use a host that doesn't resolve from inside docker. Use a routable hostname. |
-| `Invalid token` / `License expired`                              | EE license bad or unset on the parent (forwarded into the child). | Re-set on the parent: `mb license set` (operator pastes).                                                                   |
+| `Invalid token` / `License expired`                              | EE license bad or unset on the parent (forwarded into the child). | Re-set on the parent: `mb workspace license set` (operator pastes).                                                         |
 
 ### `workspace credentials` returns values that don't authenticate
 
@@ -344,20 +326,20 @@ This is a parent↔child credential drift bug — the parent's record for the wo
 Recovery (works reliably):
 
 ```bash
-mb workspace remove <ws-id> --yes --profile <parent>     # destroys container + volume; keeps parent record + provisioned dbs
+mb workspace delete <ws-id> --yes     # destroys container + volume; keeps parent record + provisioned dbs
 mb workspace start  <ws-id> --port <fresh-port> --wait --profile <parent>  # different port from the bad attempt
-mb workspace credentials <ws-id> --profile <parent> --json | jq -r '.api_key' \
+mb workspace credentials <ws-id> --json | jq -r '.api_key' \
   | xargs -I{} curl -s -H "x-api-key: {}" http://localhost:<fresh-port>/api/user/current   # smoke check
 ```
 
-Why "different port": empirically, restarting on the same port after the drifted attempt can cling to the same broken state; switching ports forces a clean parent-side handoff. If you must reuse the original port, `workspace remove --yes` plus a brief pause (a few seconds) before `start` increases the success rate.
+Why "different port": empirically, restarting on the same port after the drifted attempt can cling to the same broken state; switching ports forces a clean parent-side handoff. If you must reuse the original port, `workspace delete --yes` plus a brief pause (a few seconds) before `start` increases the success rate.
 
-`workspace remove --yes` is destructive — it drops the container _and_ the app db volume — but in the bring-up window (before any user content has been imported) there's nothing to lose. The provisioned-database records on the parent survive the remove and don't need to be re-created.
+`workspace delete --yes` is destructive — it drops the container _and_ the app db volume — but in the bring-up window (before any user content has been imported) there's nothing to lose. The provisioned-database records on the parent survive the delete and don't need to be re-created.
 
 ### Container exited shortly after `start`
 
 ```bash
-mb workspace ps --profile <parent>
+mb workspace ps
 ```
 
 `Exited (137)` → OOM. Bump Docker host memory to ≥ 6 GB.
@@ -392,7 +374,7 @@ mb workspace list --profile <parent> --full --json \
 
 ### Workspace UI demands the setup wizard
 
-You opened the URL before health passed and walked through the wizard, which created a fresh app db and bypassed the workspace bring-up. `mb workspace remove <ws-id> --yes --profile <parent>` then `start --wait` again. Don't open the URL before `state: "running"`.
+You opened the URL before health passed and walked through the wizard, which created a fresh app db and bypassed the workspace bring-up. `mb workspace delete <ws-id> --yes` then `start --wait` again. Don't open the URL before `state: "running"`.
 
 ### `git status` on the host shows confusing "staged changes" after `git-sync export`
 

package/skills/metabase-cli/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: metabase-cli
-description: Drive a Metabase instance from the terminal via the `mb` CLI. Authenticate with named profiles; inspect databases (list, get, full metadata rollup, schemas, tables in a schema) and trigger manual schema sync / field-values rescan; inspect tables, fields; list/get/create/update/archive cards (questions, models, metrics) and run them as JSON/CSV/XLSX; list/get/create/update dashboards and patch dashcards; list/get/create collections and traverse the hierarchy by id, entity_id, or "root"/"trash" (with items and recursive tree); list/get/create/update/archive native query snippets, segments, and measures; author/update/run transforms and schedule transform-jobs; read/update settings; search content (cards, dashboards, collections, transforms, metrics); manage Enterprise workspaces; git-sync to/from a git remote (status, dirty, import, export, branches, stash, add/remove a collection from sync). Use whenever the user wants to interact with a Metabase from the terminal — "log into metabase", "what profiles do I have", "list cards", "run card 42 as CSV", "create a transform", "list dashboards", "move a dashcard", "list collections", "what's in collection 4", "show the collection tree", "list snippets", "create a segment", "archive a measure", "search metabase for X", "spin up a workspace", "import the latest changes", "add a directory to git sync", "set a setting", "what schemas are in this database", "trigger a sync", "rescan field values", or anything hitting `mb <verb>`.
-allowed-tools: Bash(mb:*), Bash(npx mb:*), Read, Write, Edit, AskUserQuestion
+description: Drive a Metabase instance from the terminal via the `mb` CLI — auth, databases, cards, dashboards, transforms, queries, search, git-sync, Enterprise workspaces. Discovery entry; load the full guide with `mb skills get core`.
+allowed-tools: Bash, Read, Write, Edit, AskUserQuestion
 hidden: true
 ---
 
@@ -13,30 +13,9 @@ Install: `npm i -g @metabase/cli`
 
 ## Start here
 
-This file is a discovery stub, not the usage guide. Before running any `mb` command, load the actual workflow content from the CLI:
+Before running any `mb` command, load the workflow content from the CLI:
 
 ```bash
-mb skills get core              # start here — auth, flag conventions, every command group
-mb skills get core --full       # include all references for the deep dive
+mb skills get core    # auth, flag conventions, every command group
+mb skills list        # everything available on the installed version
 ```
-
-The CLI serves skill content bundled with the installed version, so instructions never go stale. The content in this stub cannot change between releases, which is why it just points at `mb skills get core`.
-
-## Specialized skills
-
-Load a specialized skill when the task falls outside one-shot CLI use:
-
-```bash
-mb skills get workspace         # Enterprise workspaces: create, provision, start, child credentials, diagnose
-mb skills get transform         # author + run transforms (native SQL and MBQL 5), iterate on failures
-mb skills get git-sync          # round-trip Metabase content to/from a git remote
-```
-
-Run `mb skills list` to see everything available on the installed version.
-
-## Why mb
-
-- Native `fetch`, typed Zod schemas, redacted secrets — the supported path for Metabase REST automation.
-- One `--profile` per command targets staging, prod, a workspace child, whatever the user has configured.
-- Output is shaped for agents: compact projection by default, `--full` / `--fields a,b.c` / `--json` / `--max-bytes` on every list/get.
-- `mb __manifest` returns the canonical, machine-readable inventory of every command — name, args, output schema. Use it instead of scraping `--help`.

package/dist/add-collection-ucsyAMkV.mjs

@@ -1,11 +0,0 @@
-import "./package-DFUprkSZ.mjs";
-import "./command-augment-D9pI9Vbh.mjs";
-import "./render-DuoDUTVL.mjs";
-import "./predicates-CGO17Q15.mjs";
-import "./runtime-CDu6fykq.mjs";
-import "./parse-id-CysSaCbf.mjs";
-import "./poll-task-BQe0NvJZ.mjs";
-import "./poll-p9Y7-JEQ.mjs";
-import { SyncSettingsUpdateResult, add_collection_default, setCollectionRemoteSynced, syncSettingsUpdateView } from "./add-collection-C_iovi9i.mjs";
-
-export { add_collection_default as default };

package/dist/api-key-BENHbTbV.mjs

@@ -1,13 +0,0 @@
-import { defineCommand } from "citty";
-
-//#region src/commands/api-key/index.ts
-var api_key_default = defineCommand({
-	meta: {
-		name: "api-key",
-		description: "Manage Metabase API keys"
-	},
-	subCommands: { create: () => import("./create-CrUq6sib.mjs").then((mod) => mod.default) }
-});
-
-//#endregion
-export { api_key_default as default };

package/dist/auth-DICRtJDy.mjs

@@ -1,19 +0,0 @@
-import { defineCommand } from "citty";
-
-//#region src/commands/auth/index.ts
-var auth_default = defineCommand({
-	meta: {
-		name: "auth",
-		description: "Authenticate against a Metabase instance"
-	},
-	default: "login",
-	subCommands: {
-		login: () => import("./login-D1nZwgKv.mjs").then((m) => m.default),
-		status: () => import("./status-1oUnw803.mjs").then((m) => m.default),
-		list: () => import("./list-DV6CONhp.mjs").then((m) => m.default),
-		logout: () => import("./logout-DD4q5whi.mjs").then((m) => m.default)
-	}
-});
-
-//#endregion
-export { auth_default as default };