Update agent skills to 5322ddbb8a8de914d631df350d7a4d91e77edbb7 (#208)

Automated update of the agent skills content.

Co-authored-by: databricks-ci-ghec-2[bot] <184307802+databricks-ci-ghec-2[bot]@users.noreply.github.com>

Author: databricks-ci-ghec-2[bot]

.gen.json

@@ -1,3 +1,3 @@
 {
-  "source_commit": "5443705509e5ac693d61a35ba974cb7f68f444c6"
+  "source_commit": "5322ddbb8a8de914d631df350d7a4d91e77edbb7"
 }

experimental/databricks-genie/SKILL.md

@@ -50,6 +50,9 @@ databricks genie list-spaces
 
 # Create a Genie Space from a local file
 # IMPORTANT: sample_questions require a 32-char hex "id" and "question" must be an array
+# IMPORTANT: parent_path must ALREADY EXIST — create it first, or create fails with
+#   "Tree node with path ... does not exist":
+databricks workspace mkdirs /Workspace/Users/you@company.com/genie_spaces
 databricks genie create-space --json "{
   \"warehouse_id\": \"WAREHOUSE_ID\",
   \"title\": \"Sales Analytics\",
@@ -121,7 +124,8 @@ The `serialized_space` field is a JSON string containing the full space configur
 
 - **ID format:** 32-character lowercase hex, unique across **all three lists combined** (a duplicate between e.g. `text_instructions` and `example_question_sqls` is rejected).
 - **Text fields are arrays:** `question`, `sql`, and `content` are arrays of strings, not plain strings.
-- **Sort order matters:** `data_sources.tables` must be sorted by `identifier`; `example_question_sqls` and `text_instructions` must be sorted by `id`. (`sample_questions` is silently re-sorted server-side.)
+- **Sort order matters:** `data_sources.tables` must be sorted by `identifier`, and each table's `column_configs` must be sorted by `column_name`; `example_question_sqls` and `text_instructions` must be sorted by `id`. (`sample_questions` is silently re-sorted server-side.)
+- **`text_instructions` accepts at most one item** — the API rejects more than one (`text_instructions must contain at most one item`). Merge all guidance (persona, table guide, investigation flow, answer style) into a single entry.
 - **Simple ID scheme that satisfies both rules:** prefix per list + monotonic counter, total 32 hex chars — `1…0001`, `1…0002` for `sample_questions`; `2…0001`, `2…0002` for `example_question_sqls`; `3…0001` for `text_instructions`. Authoring order = sort order, no collisions.
 
 ### Text Instructions

skills/databricks-aibi-dashboards/SKILL.md

@@ -3,7 +3,7 @@ name: databricks-aibi-dashboards
 description: "Create Databricks AI/BI dashboards. Must use when creating, updating, or deploying Lakeview dashboards as Databricks Dashboard have a unique json structure. CRITICAL: You MUST test ALL SQL queries via CLI BEFORE deploying. Follow guidelines strictly."
 compatibility: Requires databricks CLI (>= v1.0.0)
 metadata:
-  version: "0.2.0"
+  version: "0.2.1"
 parent: databricks-core
 ---
 
@@ -193,6 +193,15 @@ databricks workspace-entity-tag-assignments create-tag-assignment \
 
 ---
 
+## UPDATING AN EXISTING DASHBOARD
+
+To change a dashboard that already exists, build the updated JSON with the [creation workflow](#new-dashboard-creation-workflow) above, then deploy it with `update` + `publish` on the **same** `DASHBOARD_ID` — never re-run `create`/import.
+
+- **Don't `create`/import to update.** That mints a new dashboard id + URL and breaks any link you've already shared; `create` is for brand-new dashboards only.
+- **`update` changes only the draft.** The `/published` link viewers see stays on the last snapshot until you `publish` again — so always `publish` after `update`.
+
+---
+
 ## JSON Structure (Required Skeleton)
 
 Every dashboard's `serialized_dashboard` content must follow this exact structure:

skills/databricks-lakebase/SKILL.md

@@ -13,7 +13,20 @@ parent: databricks-core
 
 Lakebase is Databricks' serverless Postgres-compatible database, available on both AWS and Azure (GA). It provides fully managed OLTP storage with autoscaling, branching, and scale-to-zero.
 
-> **Autoscaling by Default (March 2026):** All new Lakebase instances are Autoscaling projects. The `/database/` APIs now create autoscaling instances behind the scenes. Existing provisioned instances are unchanged.
+> **Provisioned Lakebase no longer exists — never create it.** The old Provisioned tier (static, non-scalable Postgres; `databricks database` CLI / `w.database` SDK) is being migrated to Autoscaling over summer 2026, with no customer action required. Lakebase today is Autoscaling-only (`databricks postgres` / `w.postgres`). Do not attempt to create Provisioned instances; if a user asks for one, tell them Provisioned instances don't exist anymore and point them to Autoscaling. Treat the legacy `database` resource key in app configs as retired — migrate to the `postgres` resource key. For the legacy DAB `synced_database_tables` resource, use the `databricks postgres create-synced-table` CLI flow instead (see the Common Issues row and `references/synced-tables.md`).
+
+For context when reading older configs or docs, here is how the retired Provisioned tier maps to Autoscaling:
+
+| Aspect | Provisioned (retired) | Autoscaling (current) |
+|--------|-----------------------|-----------------------|
+| CLI group | `databricks database` | `databricks postgres` |
+| Top-level resource | Instance | Project |
+| Capacity | CU_1–CU_8 (16 GB/CU) | 0.5–112 CU (2 GB/CU) |
+| Branching | Not supported | Full support |
+| Scale-to-zero | Not supported | Configurable |
+| HA | Readable secondaries | 1–3 secondaries + read replicas |
+| Data API | Not available | PostgREST HTTP API |
+| Cloud | AWS only | AWS and Azure |
 
 **Compliance:** Supports HIPAA, C5, TISAX, or None.
 
@@ -157,23 +170,6 @@ databricks postgres reset-branch projects/<PROJECT_ID>/branches/<BRANCH_ID> --pr
 
 **Delete:** Protected branches must be unprotected first (`update-branch` to set `spec.is_protected` to `false`). Cannot delete branches with children. **Never delete the `production` branch.**
 
-## Key Differences from Lakebase Provisioned
-
-> All new instances default to Autoscaling as of March 2026. Automatic migration of Provisioned instances begins June 2026.
-
-| Aspect | Provisioned | Autoscaling |
-|--------|-------------|-------------|
-| CLI group | `databricks database` | `databricks postgres` |
-| Top-level resource | Instance | Project |
-| Capacity | CU_1--CU_8 (16 GB/CU) | 0.5--112 CU (2 GB/CU) |
-| Branching | Not supported | Full support |
-| Scale-to-zero | Not supported | Configurable |
-| HA | Readable secondaries | 1--3 secondaries + read replicas |
-| Data API | Not available | PostgREST HTTP API |
-| Cloud | AWS only | AWS and Azure |
-
-**Migration:** Manual via `pg_dump`/`pg_restore` (requires pausing writes). Automatic seamless upgrades (seconds of downtime) begin June 2026 -- no customer action required.
-
 ## What's Next
 
 ### Build a Databricks App
@@ -201,10 +197,9 @@ For the full app workflow, use the **`databricks-apps`** skill.
 `apps init --features lakebase` (above) wires the database at scaffold time. To
 attach a project to an **existing** app, update its resources.
 
-**Use the `postgres` resource key for an Autoscaling project** — its fields are
-`branch` + `database` (full resource paths from the table above). The legacy
-`database` key (`instance_name` + `database_name`) is for **Provisioned**
-instances only; using it for an Autoscaling project fails with
+**Use the `postgres` resource key** — its fields are `branch` + `database`
+(full resource paths from the table above). The legacy `database` key
+(`instance_name` + `database_name`) is deprecated; using it fails with
 `Database instance <name> does not exist`. Get the exact paths from
 `list-branches` / `list-databases` (the DB name is often hyphenated, e.g.
 `databricks-postgres`).
@@ -342,7 +337,7 @@ For vector embeddings with pgvector, see [pgvector.md](references/pgvector.md).
 | Sync permissions error | Ensure `USE CATALOG`/`USE SCHEMA` on source table and `CREATE TABLE` in storage catalog |
 | Synced table null bytes | Null bytes (0x00) in STRING/ARRAY/MAP/STRUCT columns cause sync failures. Sanitize source data: `REPLACE(col, CAST(CHAR(0) AS STRING), '')` |
 | Synced table data modified | Only read queries, indexes, and DROP TABLE allowed on synced tables in Postgres. Modifications break sync pipeline. |
-| DABs `synced_database_tables` with Autoscaling | Do NOT use — maps to the Provisioned API. Use `databricks postgres create-synced-table` CLI instead. DAB support for Autoscaling synced tables (`postgres_synced_tables`) is not yet available. |
+| DABs `synced_database_tables` | Deprecated — maps to a legacy API and fails on current Lakebase. Use `databricks postgres create-synced-table` CLI instead. DAB support via `postgres_synced_tables` is not yet available. |
 
 ## SDK and Version Requirements
 

skills/databricks-lakebase/references/computes-and-scaling.md

@@ -2,7 +2,7 @@
 
 ## Compute Sizing
 
-Each Compute Unit (CU) allocates ~2 GB of RAM. Lakebase Provisioned used ~16 GB per CU.
+Each Compute Unit (CU) allocates ~2 GB of RAM.
 
 | Category | Range | Notes |
 |----------|-------|-------|

skills/databricks-lakebase/references/off-platform.md

@@ -41,7 +41,7 @@ const pool = createLakebasePool({
 - OpenTelemetry metrics: `lakebase.token.refresh.duration`, `lakebase.query.duration`, pool connection gauges
 - Logging: `{ debug, info, warn, error }` boolean flags or custom logger instance
 
-> **Lakebase Autoscaling only.** This package is not compatible with Lakebase Provisioned. For the full config reference, see the [`@databricks/lakebase` README](https://github.com/databricks/appkit/tree/main/packages/lakebase).
+> For the full config reference, see the [`@databricks/lakebase` README](https://github.com/databricks/appkit/tree/main/packages/lakebase).
 
 **ORM integration:**
 

skills/databricks-lakebase/references/synced-tables.md

@@ -102,7 +102,7 @@ databricks postgres delete-synced-table "synced_tables/<LAKEBASE_CATALOG>.<SCHEM
 
 Deletes the sync pipeline and the UC table entry. The Postgres table remains and must be dropped manually if no longer needed (`DROP TABLE <schema>.<table>`).
 
-> **DABs:** The bundle schema includes `synced_database_tables`, but it maps to the Provisioned Terraform resource (`databricks_database_synced_database_table`), not the Autoscaling API. **Do not use `synced_database_tables` in DABs with Autoscaling projects** — it routes through the Provisioned API and may create unintended Provisioned instances. DAB support for Autoscaling synced tables (`postgres_synced_tables`) is blocked on Terraform provider work and not yet available. **For Autoscaling projects, use the CLI commands above.**
+> **DABs:** The bundle schema includes `synced_database_tables`, but it maps to a deprecated Terraform resource (`databricks_database_synced_database_table`) that fails on current Lakebase. **Do not use `synced_database_tables` in DABs.** DAB support via `postgres_synced_tables` is blocked on Terraform provider work and not yet available — use the CLI commands above instead.
 
 ## Example: Sync NYC Taxi Data to Lakebase