@metabase/cli 0.3.0 → 0.3.1-alpha.versioning.9ac5f50

package/skill-data/data-workflow/references/building-clean-tables.md

@@ -131,7 +131,7 @@ Then make the links real, not just implied:
 - **Wire foreign keys between your tables.** Mark each linking id as a foreign key pointing at the id it references — set the column's type to foreign-key and its target so Metabase itself knows the tables connect and can traverse them.
 - **Graft onto existing clean data** the user approved (step 3 / Phase 1): point the linking id at the existing table's id the same way. Link, don't duplicate.
 
-**Set the metadata — a transform's output starts blank, and these tables are Library-bound.** A fresh transform table has no descriptions, raw column names, and untyped columns. You worked it out while investigating; don't leave that knowledge stranded in this chat. Set it on the table so the data explains itself inside Metabase (search, the Question editor, Metabot) and is fit to publish. The mechanics — `mb field update` for semantic types / FK targets / display names, `mb table update` for table descriptions, and the feature each edit unlocks — are in the `metadata` skill; the calls about _what_ to set:
+**Set the metadata — a transform's output starts blank, and these tables are the ones people will start from.** A fresh transform table has no descriptions, raw column names, and untyped columns. You worked it out while investigating; don't leave that knowledge stranded in this chat. Set it on the table so the data explains itself inside Metabase (search, the Question editor, Metabot) and is fit to publish. The mechanics — `mb field update` for semantic types / FK targets / display names, `mb table update` for table descriptions, and the feature each edit unlocks — are in the `metadata` skill; the calls about _what_ to set:
 
 - **Semantic types — the highest-value piece.** A column's semantic type is what makes Metabase treat it right: `type/Email`, `type/Currency`/`type/Price`, `type/Category` (turns into a filter dropdown), `type/City`/`type/State`/`type/Country`, `type/CreationTimestamp`, `type/Description`. Set it on every column whose meaning you decoded. A typed column shows money as money, offers a filter dropdown, and lands on the right chart axis for everyone downstream; an untyped one is a guess.
 - **Descriptions.** A one-line description on each table and every non-obvious column.
@@ -165,7 +165,11 @@ Then report plainly:
 
 End on that connection map: it's what the user reads to trust the result, and what lets whatever they build next join on the right ids instead of guessing.
 
-These clean tables are exactly what belongs in the **Library** — published tables appear first when anyone picks a data source, so people start from your curated set, not the raw source. If the user wants that, publish the polished tables to the Library (`mb library publish` / `mb library create` mechanics, premium feature, and permissions are in `core`). Defining reusable segments / measures / metrics on top is the **reusable-definitions** stage (`references/reusable-definitions.md` in this skill).
+<!-- requires: library -->
+
+These clean tables are exactly what belongs in the **Library** — published tables appear first when anyone picks a data source, so people start from your curated set, not the raw source. If the user wants that, publish the polished tables to the Library (`mb library publish` / `mb library create` mechanics and permissions are in `core`). Defining reusable segments / measures / metrics on top is the **reusable-definitions** stage (`references/reusable-definitions.md` in this skill).
+
+<!-- /requires -->
 
 ---
 

package/skill-data/data-workflow/references/reusable-definitions.md

@@ -50,7 +50,9 @@ Two things never bend in any mode: when genuinely unsure, **ask** (the Shared Co
   - "Let me add up revenue the same way everywhere, on this table" → a **measure** on the table.
   - "Revenue is an _official company number_ people pull onto dashboards" → a **metric** in a collection, with a default month-by-month view so it charts cleanly. Lean: make it a metric when it's a headline figure the org reuses across many questions/dashboards; keep it a measure when it's a table-local convenience.
 - **Where the metric lives.** Metrics sit in a collection (folder). Lean: put the org's blessed ones in the shared **Library** so they surface prominently; keep experimental ones in a working collection until trusted.
-- **Publish the official tables to the Library.** The clean, analysis-ready tables your definitions sit on are the org's official starting points — the **Library** is how you mark them as such. Tables published to the Library's **Data** section appear _first_ when anyone picks a data source, nudging people toward your curated tables instead of raw warehouse ones. Lean: publish the wide clean tables you built the semantic layer on; hold back raw or half-built ones. Surface which tables you'd publish and confirm. (Library is a Pro/Enterprise feature; only admins and data analysts can publish — mechanics in `core`.)
+<!-- requires: library -->
+- **Publish the official tables to the Library.** The clean, analysis-ready tables your definitions sit on are the org's official starting points — the **Library** is how you mark them as such. Tables published to the Library's **Data** section appear _first_ when anyone picks a data source, nudging people toward your curated tables instead of raw warehouse ones. Lean: publish the wide clean tables you built the semantic layer on; hold back raw or half-built ones. Surface which tables you'd publish and confirm. (Only admins and data analysts can publish — mechanics in `core`.)
+<!-- /requires -->
 - **Default time dimension for a metric.** A monthly default makes it chart nicely on a dashboard, but doesn't lock anyone out of other groupings. Lean: set a sensible default (usually month) for anything headline; leave it off for raw counts that aren't inherently time-series.
 - **How strict a segment is.** "Active" = last 30 vs 90 days is a real business call with no right answer from the data alone. Lean: surface the few reasonable thresholds with how many rows each catches, let the user pick.
 
@@ -101,7 +103,9 @@ Build each agreed definition. The verb mechanics (create/update flags, the `revi
 - **Segment** → `mb segment create`. A flat MBQL filter clause on a table.
 - **Measure** → `mb measure create`. **Exactly one** aggregation on a table.
 - **Metric** → `mb card create` with the metric shape (`type: "metric"`) — it lives in a **collection**, carries the aggregation plus an optional default time dimension. Put org-blessed ones in the Library collection.
+<!-- requires: library -->
 - **Publish the official tables** → `mb library create` then `mb library publish` (mechanics in `core`) to move the clean tables your definitions sit on into the Library's **Data** section, so people start from your curated set, not raw warehouse tables.
+<!-- /requires -->
 
 Then **verify what the user can't see**, before you hand back:
 
@@ -122,10 +126,14 @@ Then **stop. Hard gate — every mode, no exceptions.** Recap in plain language
 >
 > **Metric** (in your **Library**, charts by month):
 > • **Monthly recurring revenue**
->
+
+<!-- requires: library -->
+
 > **Published to the Library** (these now show up first when anyone picks a data source):
 > • **Customers**, **Orders**
->
+
+<!-- /requires -->
+
 > Open any of those tables' Filter or Summarize block in Metabase to see them in place and try one — give it a look before you start building dashboards on top.
 
 End on that plain-language map. It's what the user reads to trust the result — and it's what stops a wrong definition from quietly propagating into everything built next.

package/skill-data/document/SKILL.md

@@ -81,7 +81,10 @@ Every node is `{ "type": string, "attrs"?: object, "content"?: [nodes], "text"?:
 - **`resizeNode`** — wraps a single `cardEmbed` or `flexContainer` to make it resizable (no `_id`). `attrs: { "height": <px>, "minHeight": <px> }`, `content` is exactly one `cardEmbed`/`flexContainer`.
 - **`flexContainer`** — a horizontal row of 1–3 `cardEmbed` / `supportingText` cells side by side (no `_id`). `attrs.columnWidths` is an array of width percentages.
 - **`supportingText`** — a text column that sits next to a card inside a `flexContainer` (id-bearing); `content` is the usual block nodes (`paragraph`, `heading`, lists, …).
-- **`smartLink`** — an inline reference to a Metabase entity (renders as a live chip). Inline, atomic, no `_id`. `attrs: { "entityId": <id>, "model": <model>, "label": <string|null>, "href": <relative-path> }`. `model` ∈ `card`, `dataset`, `metric`, `dashboard`, `collection`, `table`, `database`, `document`, `transform`, `segment`, `user`, `action`, `indexed-entity` (plus `measure` on v60+).
+- **`smartLink`** — an inline reference to a Metabase entity (renders as a live chip). Inline, atomic, no `_id`. `attrs: { "entityId": <id>, "model": <model>, "label": <string|null>, "href": <relative-path> }`. `model` ∈ `card`, `dataset`, `metric`, `dashboard`, `collection`, `table`, `database`, `document`, `transform`, `segment`, `user`, `action`, `indexed-entity`.
+  <!-- requires: smartLinkMeasureModel -->
+  - `measure` is a valid `model` too.
+  <!-- /requires -->
 - **`metabot`** — an inline Metabot prompt block.
 
 ## Embedding an existing card

package/skill-data/git-sync/SKILL.md

@@ -2,6 +2,7 @@
 name: git-sync
 description: Round-trip Metabase content (cards, dashboards, transforms, snippets, collections, Library-published table/field metadata) between an instance and a git remote via `mb git-sync …` — status, dirty / has-remote-changes checks, import, export (with branch guard), branches, stash, add/remove a collection from sync. Load when the user wants to "import the latest changes", "export to git", "push my changes to the repo", "open a PR with my Metabase changes", "git sync", "dirty check", "stash before pulling", "add a collection to sync", or anything `mb git-sync …`.
 allowed-tools: Read, Write, Edit, Bash, AskUserQuestion
+requires: [remoteSync]
 ---
 
 # git-sync (representations ↔ instance)
@@ -130,6 +131,8 @@ mb setting set remote-sync-type '"read-write"' --profile <n>
 
 **Verifying the result.** `mb git-sync status --profile <n> --json` lists the flagged collections under `synced_collections`, and `mb collection get <id> --json` shows the per-collection `is_remote_synced` flag.
 
+<!-- requires: library -->
+
 ## Published table metadata (Library) and sync scope
 
 Table and field metadata — table/field descriptions, semantic types (`type/PK`, `type/FK`), FK targets, plus segments and measures on the table — serializes for **Library-published tables only**, under `databases/<db>/schemas/<schema>/tables/<table>/…` in the repo. Eligibility is two-gated: the table must be published (`mb library publish`), **and** the Library collection holding it must itself carry `is_remote_synced: true`. An ordinary warehouse table, or a transform's target table that isn't published, never serializes — a transform's YAML carries only the transform definition (query, target, description), not the output table's field metadata.
@@ -144,6 +147,8 @@ mb git-sync stash --new-branch <branch> -m "..." --profile <n>     # or create-b
 
 Flagging the collection records it for the next export, which serializes its current content — including already-published tables and their field metadata. `mb library publish` prints a reminder when the target collection is outside the sync scope on an instance with a configured remote.
 
+<!-- /requires -->
+
 ## Don't (git-sync-specific)
 
 - Don't turn instance-side changes into hand-written repo files. When the changes were made against the instance, export them (`stash` / `create-branch` + `export`) and PR the exported branch; reconstructing them as YAML by hand — or pushing files in paths/formats the serializer doesn't own — produces content that never applies on import, and pushing behind Metabase's back races its own sync tasks. Hand-editing YAML belongs to the repo-first workflow, in the serialized layout the repo already uses.

package/skill-data/mbql/SKILL.md

@@ -122,7 +122,7 @@ No `type:"query"` wrapper, no `query:` nesting. If you wrap the query inside a l
 
 ## Legacy formats you may encounter
 
-Older Metabase servers used a different query envelope (sometimes called MBQL 4 / "legacy MBQL"); the `mbql/query` shape above is what recent servers store and return. You won't author the legacy shapes, but you may see them in queries created long ago. Anything not `lib/type: "mbql/query"` is sent as-is and normalized server-side — you lose validation, so don't author these:
+Queries created long ago may carry a different envelope (sometimes called MBQL 4 / "legacy MBQL"); the `mbql/query` shape above is what the server stores and returns. You won't author the legacy shapes, but you may see them in old content. Anything not `lib/type: "mbql/query"` is sent as-is and normalized server-side — you lose validation, so don't author these:
 
 - **Legacy structured** — `{ "type": "query", "database": N, "query": { "source-table": T, … } }`
 - **Flat native** — `{ "type": "native", "database": N, "native": { "query": "SELECT …" } }` — the server accepts it, but author the native stage instead (`native-sql`).

package/skill-data/mbql/references/operators.md

@@ -106,21 +106,26 @@ Units (truncation only): `millisecond`, `second`, `minute`, `hour`, `day`, `week
 
 A stage's `aggregation` is a list of aggregation clauses.
 
-| Op                      | Args                       | Notes                            |
-| ----------------------- | -------------------------- | -------------------------------- |
-| `count`                 | none, or 1 expression      | with arg: count non-NULL         |
-| `sum` `avg` `min` `max` | 1 numeric/orderable        |                                  |
-| `distinct`              | 1 expression               | count of distinct values         |
-| `cum-count`             | none or 1 expression       | running count                    |
-| `cum-sum`               | 1 numeric                  | running sum                      |
-| `stddev` `var` `median` | 1 numeric                  |                                  |
-| `percentile`            | numeric, p (0.0–1.0)       |                                  |
-| `count-where`           | 1 boolean clause           |                                  |
-| `sum-where`             | numeric, boolean clause    |                                  |
-| `distinct-where`        | expression, boolean clause |                                  |
-| `share`                 | 1 boolean clause           | proportion 0–1                   |
-| `metric`                | metric id                  | reference a saved metric card    |
-| `measure`               | measure id                 | reference a saved measure (v59+) |
+| Op                      | Args                       | Notes                         |
+| ----------------------- | -------------------------- | ----------------------------- |
+| `count`                 | none, or 1 expression      | with arg: count non-NULL      |
+| `sum` `avg` `min` `max` | 1 numeric/orderable        |                               |
+| `distinct`              | 1 expression               | count of distinct values      |
+| `cum-count`             | none or 1 expression       | running count                 |
+| `cum-sum`               | 1 numeric                  | running sum                   |
+| `stddev` `var` `median` | 1 numeric                  |                               |
+| `percentile`            | numeric, p (0.0–1.0)       |                               |
+| `count-where`           | 1 boolean clause           |                               |
+| `sum-where`             | numeric, boolean clause    |                               |
+| `distinct-where`        | expression, boolean clause |                               |
+| `share`                 | 1 boolean clause           | proportion 0–1                |
+| `metric`                | metric id                  | reference a saved metric card |
+
+<!-- requires: measures -->
+
+`measure` takes a measure id and references a saved measure.
+
+<!-- /requires -->
 
 ```json
 ["count", {…}]

package/skill-data/metadata/SKILL.md

@@ -43,7 +43,7 @@ mb field update 1711 --body '{"semantic_type":"type/FK","fk_target_field_id":168
 - Queries can pull columns from the related table with no explicit join — `["field", {"source-field": 1711}, 1682]` in MBQL (see `mbql`).
 - Dashboard **linked filters** become possible (a State filter narrowing a City filter). **Linked filters read only these table-metadata FKs** — never a join you wrote inside a saved question — which is why a linked filter that "shows values it shouldn't" almost always means the FK isn't set in metadata. (See `dashboard`.)
 
-Removing the `type/FK` semantic type auto-clears `fk_target_field_id`. Point a FK only at a field in the **same database** — v60+ rejects a cross-database target; v58–v59 accept it silently and leave a broken relationship.
+Removing the `type/FK` semantic type auto-clears `fk_target_field_id`. Point a FK only at a field in the **same database** — a cross-database target is invalid and never resolves to a relationship.
 
 ## Semantic types are labels, not casts
 

package/skill-data/metadata/references/semantic-types.md

@@ -71,7 +71,13 @@ Everything else on a field/table (physical `name`, `base_type`, `effective_type`
 `display_name` · `description` · `caveats` · `points_of_interest` · `semantic_type` · `coercion_strategy` · `fk_target_field_id` · `visibility_type` · `has_field_values` · `settings` · `nfc_path` · `json_unfolding`
 
 **`PUT /api/table/:id` (`mb table update`)**
-`display_name` · `description` · `visibility_type` · `field_order` (`database` / `alphabetical` / `custom` / `smart`) · `entity_type` · `caveats` · `points_of_interest` · `show_in_getting_started` · `owner_user_id` / `owner_email` (ownership) · `data_layer` / `data_authority` / `data_source` (data-governance tiers) · `collection_id` (v62+)
+`display_name` · `description` · `visibility_type` · `field_order` (`database` / `alphabetical` / `custom` / `smart`) · `entity_type` · `caveats` · `points_of_interest` · `show_in_getting_started` · `owner_user_id` / `owner_email` (ownership) · `data_layer` / `data_authority` / `data_source` (data-governance tiers)
+
+<!-- requires: library -->
+
+· `collection_id` — the Library **Data** collection a published table sits in (`mb library publish` sets it; see `core`)
+
+<!-- /requires -->
 
 ## Coercion strategies (common)
 

package/skill-data/native-sql/references/template-tags.md

@@ -86,9 +86,13 @@ SQL: `{{snippet: Active Rows}}`. Create/manage the fragment with `mb snippet` (`
 
 SQL: `{{#42}}` or `{{#42-slug}}`, used where a table/subquery goes (`FROM {{#42}}`, `WITH x AS {{#42}}`). Runs with the referenced card's own defaults; no user value.
 
-### Source table — `table` (v59+)
+<!-- requires: nativeTableTemplateTag -->
 
-A niche v59+ type that references a warehouse table by id (`{type: "table", table-id: <id>}`, optional `source-filters`) where a table/subquery goes — analogous to a card reference but pointing at a raw table. Absent on v0.58. Reach for a card reference (`card`) unless you specifically need a bare-table source tag.
+### Source table — `table`
+
+A niche type that references a warehouse table by id (`{type: "table", table-id: <id>}`, optional `source-filters`) where a table/subquery goes — analogous to a card reference but pointing at a raw table. Reach for a card reference (`card`) unless you specifically need a bare-table source tag.
+
+<!-- /requires -->
 
 ### Temporal unit — `temporal-unit`
 

package/skill-data/notification/SKILL.md

@@ -110,7 +110,13 @@ An alert body has exactly three parts:
 
 Recipients are `{"email": "a@b.com"}` for an external address or `{"id": <user-id>}` for a Metabase user. A Slack channel is **not** a recipient — it goes in `details`: `{"channel_type": "slack", "details": {"channel": "#general"}, …}`.
 
-**`skip_if_empty: true`** suppresses the send when the dashboard's questions return no rows — the way to build a "only tell me when something happened" dashboard report. **`parameters`** sets filter values for this subscription only, so one dashboard can feed several audiences a different slice (Pro/Enterprise). Its entries are dashboard parameter values — the parameter `id`s come from `mb dashboard get <id> --fields parameters --json` (see the `dashboard` skill).
+**`skip_if_empty: true`** suppresses the send when the dashboard's questions return no rows — the way to build a "only tell me when something happened" dashboard report.
+
+<!-- requires: dashboardSubscriptionFilters -->
+
+**`parameters`** sets filter values for this subscription only, so one dashboard can feed several audiences a different slice. Its entries are dashboard parameter values — the parameter `id`s come from `mb dashboard get <id> --fields parameters --json` (see the `dashboard` skill).
+
+<!-- /requires -->
 
 `mb subscription list --archived` is a **swap, not a union** — it returns archived subscriptions _instead of_ active ones, never both. `mb dashboard subscriptions <id>` is the list scoped to one dashboard. `mb subscription archive <id>` also disables every channel on it, so restoring takes two steps: `update --body '{"archived":false}'`, then re-send the `channels` array with `enabled: true`.
 

package/skill-data/transform/SKILL.md

@@ -2,6 +2,7 @@
 name: transform
 description: Author and run Metabase transforms via `mb` — body shape (native SQL or structured MBQL), create + run-with-wait, run inspection, dependencies, cancel, the `update`-vs-recreate iteration rule, the writable-keys-only PATCH contract, plus transform tags and tag-driven transform-job schedules. Load when the user touches transforms — "create a transform", "run a transform", "fix a failing transform", "list transform runs", "cancel a running transform", "manage transform tags", "run a transform job", or anything `mb transform …` / `mb transform-job …` / `mb transform-tag …`.
 allowed-tools: Read, Write, Edit, Bash, AskUserQuestion
+requires: [transforms]
 ---
 
 # Transforms
@@ -67,7 +68,7 @@ TABLE_ID=$(mb transform run <id> --sync --profile <name> --json | jq -r '.target
 mb table get "$TABLE_ID" --include fields --profile <name> --json   # field ids for MBQL
 ```
 
-On `target_table_id: null` (still syncing when the poll timed out; exit 0) re-poll `mb transform get <id> --full --json` until the `target_table_id` / `table` linkage lands.
+On `target_table_id: null` (still syncing when the poll timed out; exit 0) re-poll `mb transform get <id> --json` until `target_table_id` is a number.
 
 Columns and types are inferred from the result set; change the SELECT shape and the next run fails on a column mismatch — drop the table first (`transform delete-table <id>`). A changed shape also needs a re-run with `--sync` before MBQL sees the new/renamed columns.
 
@@ -198,7 +199,16 @@ Key verbs (`mb transform-job --help` for the full list):
 mb transform-job transforms <id> --profile <name> --json   # preview which transforms this job resolves to (by tag)
 mb transform-job run <id> --profile <name> --json          # trigger a job now; runs all its tagged transforms
 mb transform-job run <id> --force-refresh --profile <name> --json   # also re-run dependencies that are already fresh
+```
+
+<!-- requires: transformJobActivation -->
+
+```bash
 mb transform-job set-active false --profile <name> --json  # disable every job at once (true re-enables); admin only
 ```
 
-`transform-job run` is fire-and-forget — the server returns `{message, job_run_id}` immediately, with no per-job-run polling (no `--wait`). Most ad-hoc agent work is one-off `transform run`, not job authoring.
+<!-- /requires -->
+
+Every job row carries `active`; it is `null` on a server that cannot switch jobs off, where every job runs on schedule.
+
+`transform-job run` is fire-and-forget — it returns `{message, started, run_id}` immediately (both `null` when the server does not number job runs: the request was accepted and whether a run started is unsaid), with no per-job-run polling (no `--wait`). Most ad-hoc agent work is one-off `transform run`, not job authoring.

package/skill-data/visualization/SKILL.md

@@ -27,7 +27,10 @@ Decide which relationship in the data matters most, then pick the chart. The sha
 - **Compare a measure across categories** → `bar` (vertical). Use `row` (horizontal bar) when labels are long or there are many categories. Sort by value unless the dimension has a natural order.
 - **Change over time / trend** → `line` for a continuous series; `bar`/`area` for a few discrete periods. Two measures on unlike scales → `combo` (line + bar, dual-axis) — only when the metrics are genuinely related.
 - **Part-to-whole, one snapshot** → `pie`, but only for a meaningful whole with **≤5 slices**; beyond that use a sorted `bar`/`row`. Composition over time → stacked `area`/`bar`.
-- **Distribution / spread / outliers** → a `bar` histogram (bin the measure — see `mbql` binning); on **v59+** servers `boxplot` compares several groups' spread directly.
+- **Distribution / spread / outliers** → a `bar` histogram (bin the measure — see `mbql` binning).
+<!-- requires: boxplotDisplay -->
+- **Spread across several groups** → `boxplot` compares the groups' distributions directly.
+<!-- /requires -->
 - **Correlation between two measures** → `scatter` (a third measure → bubble size).
 - **Sequential additive contributions** (start → +/− steps → total) → `waterfall`.
 - **Stage drop-off in an ordered, cumulative funnel** → `funnel`.
@@ -35,7 +38,7 @@ Decide which relationship in the data matters most, then pick the chart. The sha
 - **Geographic** → `map`: region/choropleth (a region dimension + a measure), pin (lat + long), or grid/heat (coordinates + measure).
 - **Precise values, many columns, mixed types, or no chart fits** → `table`; `pivot` for a cross-tab of two dimensions; `object` for a single record's detail.
 
-Valid `display` values — the registered visualizations: `table`, `bar`, `line`, `area`, `row`, `pie`, `scalar`, `smartscalar`, `combo`, `pivot`, `funnel`, `map`, `scatter`, `waterfall`, `progress`, `gauge`, `object`, `sankey`. The API types `display` as a plain string and accepts any value — it renders an unknown one as nothing. (`boxplot` is registered only on **v59+** servers — older ones render it blank; use a `bar` histogram for distributions instead. `scalar` **is** the "Number" viz — `display: number` is a legacy serialization alias, not a registered visualization; use `scalar`. `list` exists but is hidden — don't pick it. `heading`/`text`/`link`/`iframe`/`action` are dashcard virtuals, not standalone cards — see references.) A typo like `bargraph`/`linechart` is accepted and renders blank — the most common "why is my chart blank" cause.
+Valid `display` values — the registered visualizations: `table`, `bar`, `line`, `area`, `row`, `pie`, `scalar`, `smartscalar`, `combo`, `pivot`, `funnel`, `map`, `scatter`, `waterfall`, `progress`, `gauge`, `object`, `sankey`. The API types `display` as a plain string and accepts any value — it renders an unknown one as nothing. (`scalar` **is** the "Number" viz — `display: number` is a legacy serialization alias, not a registered visualization; use `scalar`. `list` exists but is hidden — don't pick it. `heading`/`text`/`link`/`iframe`/`action` are dashcard virtuals, not standalone cards — see references.) A typo like `bargraph`/`linechart` is accepted and renders blank — the most common "why is my chart blank" cause.
 
 ## Step 2 — bind data columns and set options
 
@@ -53,7 +56,6 @@ Valid `display` values — the registered visualizations: `table`, `bar`, `line`
 | `row`                       | as bar; prefer for long/many category labels              | `graph.dimensions`, `graph.metrics`                        |
 | `scatter`                   | two numeric measures (correlation)                        | `graph.dimensions`, `graph.metrics` (`scatter.bubble` opt) |
 | `waterfall`                 | exactly 1 dimension + ≥1 measure; sequential              | `graph.dimensions` (1), `graph.metrics` (1)                |
-| `boxplot` _(v59+)_          | ≥3 cols, ≥2 dimensions, ≥1 measure                        | `graph.dimensions`, `graph.metrics`                        |
 | `pie`                       | ≥2 rows, ≥2 cols, ≥1 dimension + ≥1 measure; ≤~5 slices   | `pie.dimension`, `pie.metric`                              |
 | `funnel`                    | 2 columns (stage + value); ordered stages                 | `funnel.dimension`, `funnel.metric`                        |
 | `map` (region)              | a string/region dimension + a measure                     | `map.region`, `map.dimension`, `map.metric`                |
@@ -62,6 +64,12 @@ Valid `display` values — the registered visualizations: `table`, `bar`, `line`
 | `pivot`                     | ≥2 cols, all aggregated/breakout                          | — (`pivot_table.column_split` auto)                        |
 | `table` `object`            | anything (table is the universal fallback)                | — (always renders)                                         |
 
+<!-- requires: boxplotDisplay -->
+
+`boxplot` is registered too: ≥3 cols, ≥2 dimensions, ≥1 measure, on **unaggregated** rows; required keys `graph.dimensions`, `graph.metrics`.
+
+<!-- /requires -->
+
 ### The rule that trips everyone: settings name **output columns**, by name
 
 `graph.dimensions`, `graph.metrics`, `pie.dimension`, `pie.metric`, `scalar.field`, `funnel.metric`, `map.latitude_column`, `sankey.source`, … all take **output column-name strings** — the names the query _produces_, not field ids. A `count` aggregation outputs the column `count`; a breakout on a field outputs that field's name; a named aggregation outputs its `name`. These strings are **identical in the API form and the portable (git-sync) form** — no numeric-vs-name footgun here.

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

@@ -2,7 +2,7 @@
 
 ## Contents
 
-- [Cartesian — `bar`, `line`, `area`, `combo`, `scatter`, `waterfall`, `row`, `boxplot`](#cartesian--bar-line-area-combo-scatter-waterfall-row-boxplot) — shared keys (binding, stacking, goal/trend, data labels, axes, tooltip) plus `scatter`, `waterfall`, `row`, `boxplot` extras
+- [Cartesian — `bar`, `line`, `area`, `combo`, `scatter`, `waterfall`, `row`](#cartesian--bar-line-area-combo-scatter-waterfall-row) — shared keys (binding, stacking, goal/trend, data labels, axes, tooltip) plus `scatter`, `waterfall`, `row` extras
 - [Part-to-whole & single value — `pie`, `funnel`, `gauge`, `progress`, `scalar`, `smartscalar`](#part-to-whole--single-value--pie-funnel-gauge-progress-scalar-smartscalar)
 - [Tabular, geographic & flow — `table`, `pivot`, `object`, `map`, `sankey`](#tabular-geographic--flow--table-pivot-object-map-sankey) — includes `table.column_formatting` conditional formatting
 - [`column_settings` — per-column formatting](#column_settings--per-column-formatting) — number/date/currency, `view_as`, alignment, mini bars
@@ -18,7 +18,7 @@ All column-naming keys (`graph.dimensions`, `pie.dimension`, `table.columns[].na
 
 ---
 
-# Cartesian — `bar`, `line`, `area`, `combo`, `scatter`, `waterfall`, `row`, `boxplot`
+# Cartesian — `bar`, `line`, `area`, `combo`, `scatter`, `waterfall`, `row`
 
 `bar`/`line`/`area`/`combo` share an identical key set (combo just defaults the first series to a line, the rest to bars). `scatter`/`waterfall`/`row`/`boxplot` use a subset plus their own extras. Most allow up to 2 dimensions and unlimited metrics; **waterfall is 1 dimension + 1 metric**, boxplot allows 2 dimensions.
 
@@ -102,9 +102,9 @@ Use for sequential additive contributions (start → +/− steps → total). **U
 
 Horizontal bars — use when category labels are long or numerous. Here `graph.dimensions` is the y-axis (categories) and `graph.metrics` the x-axis (values). X-scale is `"ordinal"` only; no trend line, tooltip columns, or split panels. **Required:** `graph.dimensions`, `graph.metrics`.
 
-## boxplot
+<!-- requires: boxplotDisplay -->
 
-_Registered only on **v59+** servers — older ones render `display: boxplot` blank; use a `bar` histogram there._
+## boxplot
 
 Use for distribution/spread/outliers, especially across several groups. Needs **unaggregated** rows. **Use for:** ≥3 columns, ≥2 dimensions, ≥1 measure. **Required:** `graph.dimensions`, `graph.metrics`. X-scale is `"ordinal"`.
 
@@ -115,6 +115,8 @@ Use for distribution/spread/outliers, especially across several groups. Needs **
 | `boxplot.show_mean`        | boolean |                                                | `true`       |
 | `boxplot.show_values_mode` | string  | `"median"`, `"all"` (when `graph.show_values`) | `"median"`   |
 
+<!-- /requires -->
+
 ---
 
 # Part-to-whole & single value — `pie`, `funnel`, `gauge`, `progress`, `scalar`, `smartscalar`

package/skills/metabase-cli/SKILL.md

@@ -17,7 +17,7 @@ Before running any `mb` command, load the workflow content from the CLI:
 
 ```bash
 mb skills get core    # auth, flag conventions, every command group
-mb skills list        # everything available on the installed version
+mb skills list        # every bundled skill the profile's server can use (--all for all of them)
 ```
 
 **Doing a whole job, not one command?** If the user wants an outcome — "make sense of my data", "build a data model", "go from raw data to a dashboard", "answer questions about my data", "be my data analyst", "set up analytics for X" — load the guided end-to-end skill instead and let it drive:

package/dist/card-CHI2bmds.mjs

@@ -1,24 +0,0 @@
-import { t as defineCommandGroup } from "./group-DBM87IgC.mjs";
-//#region src/commands/card/index.ts
-var card_default = defineCommandGroup({
-	name: "card",
-	description: "Manage Metabase cards (questions, models, metrics)",
-	skills: [{
-		skill: "mbql",
-		purpose: "author the dataset_query"
-	}, {
-		skill: "visualization",
-		purpose: "choose display and visualization_settings"
-	}],
-	subCommands: {
-		list: () => import("./list-B4hJuMhA.mjs").then((mod) => mod.default),
-		get: () => import("./get-B_xdF1kq.mjs").then((mod) => mod.default),
-		query: () => import("./query-BbqECzmF.mjs").then((mod) => mod.default),
-		alerts: () => import("./alerts-Bf2RH_p_.mjs").then((mod) => mod.default),
-		create: () => import("./create-C79vErX0.mjs").then((mod) => mod.default),
-		update: () => import("./update-CO4m4wH3.mjs").then((mod) => mod.default),
-		archive: () => import("./archive-C7w49Grr.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { card_default as default };

package/dist/collection-CY0AB99E.mjs

@@ -1,20 +0,0 @@
-import { t as defineCommandGroup } from "./group-DBM87IgC.mjs";
-//#region src/commands/collection/index.ts
-var collection_default = defineCommandGroup({
-	name: "collection",
-	description: "Manage Metabase collections",
-	skills: [{
-		skill: "core",
-		purpose: "collection ref forms and the transforms namespace"
-	}],
-	subCommands: {
-		list: () => import("./list-DMKDsBRd.mjs").then((mod) => mod.default),
-		get: () => import("./get-DkWO0EI0.mjs").then((mod) => mod.default),
-		items: () => import("./items-CQlPXBXE.mjs").then((mod) => mod.default),
-		tree: () => import("./tree-CH-f3bjP.mjs").then((mod) => mod.default),
-		create: () => import("./create-CAQV2g6V.mjs").then((mod) => mod.default),
-		archive: () => import("./archive-BxNPHxOY.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { collection_default as default };

package/dist/document-BbskZPTT.mjs

@@ -1,19 +0,0 @@
-import { t as defineCommandGroup } from "./group-DBM87IgC.mjs";
-//#region src/commands/document/index.ts
-var document_default = defineCommandGroup({
-	name: "document",
-	description: "Manage Metabase documents",
-	skills: [{
-		skill: "document",
-		purpose: "author the ProseMirror document body"
-	}],
-	subCommands: {
-		list: () => import("./list-CNUiF8Z7.mjs").then((mod) => mod.default),
-		get: () => import("./get-D_h-G9bn.mjs").then((mod) => mod.default),
-		create: () => import("./create-tQbnuz-I.mjs").then((mod) => mod.default),
-		update: () => import("./update-D-NE60AV.mjs").then((mod) => mod.default),
-		archive: () => import("./archive-lQqs13Uz.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { document_default as default };

package/dist/get-CvI--9S_.mjs

@@ -1,80 +0,0 @@
-import { i as ConfigError } from "./predicates-Bkm2IoeX.mjs";
-import { F as outputFlags, N as listFlags, R as listEnvelopeSchema, s as renderList, u as writeText } from "./cli.mjs";
-import { n as parseCsv, t as defineMetabaseCommand } from "./runtime-DiKyBxOw.mjs";
-import { n as windowList } from "./window-BkvrP0gB.mjs";
-import { a as readSkillContent, i as loadVisibleSkills, o as selectSkillsByNames, r as loadAllSkills, t as SkillContent } from "./skills-DTCrMcix.mjs";
-//#region src/commands/skills/get.ts
-const SkillGetEnvelope = listEnvelopeSchema(SkillContent);
-const SKILL_OVERSIZE_HINT = "a skill body is indivisible — pass --max-bytes 0 to print it whole, or `mb skills path <name>` to read it from disk";
-const skillContentView = {
-	compactPick: SkillContent,
-	tableColumns: [{
-		key: "name",
-		label: "Name"
-	}, {
-		key: "description",
-		label: "Description"
-	}]
-};
-var get_default = defineMetabaseCommand({
-	meta: {
-		name: "get",
-		description: "Print one or more skills' SKILL.md content. Pass comma-separated names, or --all for every non-hidden skill. --full includes references and templates."
-	},
-	capabilities: null,
-	args: {
-		...outputFlags,
-		...listFlags,
-		names: {
-			type: "positional",
-			description: "Skill name (or comma-separated list). Omit when using --all.",
-			required: false
-		},
-		all: {
-			type: "boolean",
-			description: "Fetch every non-hidden skill"
-		}
-	},
-	outputSchema: SkillGetEnvelope,
-	examples: [
-		"mb skills get core",
-		"mb skills get core --full",
-		"mb skills get git-sync,transform --json",
-		"mb skills get --all --json"
-	],
-	run({ args, ctx }) {
-		const envelope = windowList(pickSkills({
-			names: args.names,
-			all: args.all === true
-		}).map((info) => readSkillContent(info, { includeExtras: ctx.full })), ctx.range);
-		if (ctx.format === "json") {
-			renderList(envelope, skillContentView, {
-				...ctx,
-				oversizeHint: SKILL_OVERSIZE_HINT
-			});
-			return;
-		}
-		writeText(renderText(envelope.data, ctx.full));
-	}
-});
-function pickSkills({ names, all }) {
-	if (all && names !== void 0) throw new ConfigError("--all conflicts with a positional skill name");
-	if (all) return loadVisibleSkills();
-	if (names === void 0) throw new ConfigError("provide a skill name (comma-separated for multiple) or --all");
-	return selectSkillsByNames(loadAllSkills(), parseCsv(names));
-}
-function renderText(payloads, includeExtras) {
-	return payloads.map((payload) => renderTextSection(payload, includeExtras)).join("\n\n");
-}
-function renderTextSection(payload, includeExtras) {
-	const parts = [payload.body.trimEnd()];
-	if (!includeExtras) return parts.join("\n\n");
-	for (const ref of payload.references) parts.push(extraFileHeader(payload.name, ref.path), ref.content.trimEnd());
-	for (const tpl of payload.templates) parts.push(extraFileHeader(payload.name, tpl.path), tpl.content.trimEnd());
-	return parts.join("\n\n");
-}
-function extraFileHeader(skillName, relPath) {
-	return `=== ${skillName}/${relPath} ===`;
-}
-//#endregion
-export { get_default as default };

package/dist/git-sync-MQQYRYLg.mjs

@@ -1,28 +0,0 @@
-import { t as defineCommandGroup } from "./group-DBM87IgC.mjs";
-//#region src/commands/git-sync/index.ts
-var git_sync_default = defineCommandGroup({
-	name: "git-sync",
-	description: "Sync Metabase content with a git remote",
-	skills: [{
-		skill: "git-sync",
-		purpose: "import/export round-trip and dirty checks"
-	}],
-	subCommands: {
-		status: () => import("./status-BhswxJL1.mjs").then((mod) => mod.default),
-		"is-dirty": () => import("./is-dirty-DYeJYhBz.mjs").then((mod) => mod.default),
-		"has-remote-changes": () => import("./has-remote-changes-C684Redh.mjs").then((mod) => mod.default),
-		dirty: () => import("./dirty-DNYoM6Bp.mjs").then((mod) => mod.default),
-		"current-task": () => import("./current-task-MpBFGttd.mjs").then((mod) => mod.default),
-		"cancel-task": () => import("./cancel-task-C5CU1pxU.mjs").then((mod) => mod.default),
-		wait: () => import("./wait-DoMDH226.mjs").then((mod) => mod.default),
-		import: () => import("./import-Rmmttboo.mjs").then((mod) => mod.default),
-		export: () => import("./export-BjfoZRDJ.mjs").then((mod) => mod.default),
-		stash: () => import("./stash-D0S4JmAz.mjs").then((mod) => mod.default),
-		branches: () => import("./branches-DchlyU0i.mjs").then((mod) => mod.default),
-		"create-branch": () => import("./create-branch-CYo6jZth.mjs").then((mod) => mod.default),
-		"add-collection": () => import("./add-collection-B3Ty8SzB.mjs").then((mod) => mod.default),
-		"remove-collection": () => import("./remove-collection-BOnxYvhj.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { git_sync_default as default };

package/dist/library-ClLgrAXy.mjs

@@ -1,19 +0,0 @@
-import { r as Collection } from "./collection-CfulNRBG.mjs";
-import { z } from "zod";
-//#region ../client/src/domain/library.ts
-const LibraryChild = Collection.pick({
-	id: true,
-	name: true,
-	type: true,
-	description: true,
-	is_remote_synced: true
-}).strip();
-const Library = Collection.extend({ effective_children: z.array(LibraryChild) }).loose();
-const LibraryCompact = Library.pick({
-	id: true,
-	name: true,
-	type: true,
-	effective_children: true
-}).strip();
-//#endregion
-export { LibraryCompact as n, Library as t };