Fix Lakebase and Apps skill guidance based on agent conversation analysis

Five agent conversations building Lakebase-backed apps revealed consistent
patterns of wasted work. This fixes the root causes in skill documentation:
remove wasteful exploratory commands, add missing --version flag, and
document default resource names.

Co-authored-by: Isaac

Author: pkosiec

skills/databricks-apps/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: databricks-apps
 description: Build apps on Databricks Apps platform. Use when asked to create dashboards, data apps, analytics tools, or visualizations. Invoke BEFORE starting implementation.
-compatibility: Requires databricks CLI (>= v0.292.0)
+compatibility: Requires databricks CLI (>= v0.294.0)
 metadata:
   version: "0.1.1"
 parent: databricks
@@ -100,6 +100,8 @@ npx @databricks/appkit docs ./docs/plugins/analytics.md  # example: specific doc
 1. **Get the manifest** (JSON schema describing plugins and their resources):
    ```bash
    databricks apps manifest --profile <PROFILE>
+   # See plugins available in a specific AppKit version:
+   databricks apps manifest --version <VERSION> --profile <PROFILE>
    # Custom template:
    databricks apps manifest --template <GIT_URL> --profile <PROFILE>
    ```
@@ -118,6 +120,7 @@ npx @databricks/appkit docs ./docs/plugins/analytics.md  # example: specific doc
    # With custom template:
    databricks apps init --template <GIT_URL> --name <NAME> --features ... --set ... --profile <PROFILE>
    ```
+   Optionally use `--version <VERSION>` to target a specific AppKit version.
    - **Required**: `--name`, `--profile`. Name: ≤26 chars, lowercase letters/numbers/hyphens only. Use `--features` only for **optional** plugins the user wants (plugins with `requiredByTemplate: false` or absent); mandatory plugins must not be listed in `--features`.
    - **Resources**: Pass `--set` for every required resource (each field in `resources.required`) for (1) all plugins with `requiredByTemplate: true`, and (2) any optional plugins you added to `--features`. Add `--set` for `resources.optional` only when the user requests them.
    - **Discovery**: Use the parent `databricks` skill to resolve IDs (e.g. warehouse: `databricks warehouses list --profile <PROFILE>` or `databricks experimental aitools tools get-default-warehouse --profile <PROFILE>`).

skills/databricks-jobs/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: databricks-jobs
 description: Develop and deploy Lakeflow Jobs on Databricks. Use when creating data engineering jobs with notebooks, Python wheels, or SQL tasks. Invoke BEFORE starting implementation.
-compatibility: Requires databricks CLI (>= v0.292.0)
+compatibility: Requires databricks CLI (>= v0.294.0)
 metadata:
   version: "0.1.0"
 parent: databricks

skills/databricks-lakebase/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: databricks-lakebase
 description: "Manage Lakebase Postgres Autoscaling projects, branches, and endpoints via Databricks CLI. Use when asked to create, configure, or manage Lakebase Postgres databases, projects, branches, computes, or endpoints."
-compatibility: Requires databricks CLI (>= v0.292.0)
+compatibility: Requires databricks CLI (>= v0.294.0)
 metadata:
   version: "0.1.0"
 parent: databricks
@@ -60,6 +60,8 @@ Run `databricks postgres -h` before constructing any command. Run `databricks po
 
 ## Create a Project
 
+> **Do NOT list projects before creating.**
+
 ```bash
 databricks postgres create-project <PROJECT_ID> \
   --json '{"spec": {"display_name": "<DISPLAY_NAME>"}}' \
@@ -139,7 +141,7 @@ databricks apps init --name <APP_NAME> \
   --features lakebase \
   --set "lakebase.postgres.branch=<BRANCH_NAME>" \
   --set "lakebase.postgres.database=<DATABASE_NAME>" \
-  --profile <PROFILE>
+  --run none --profile <PROFILE>
 ```
 
 Where `<BRANCH_NAME>` is the full resource name (e.g. `projects/<PROJECT_ID>/branches/<BRANCH_ID>`) and `<DATABASE_NAME>` is the full resource name (e.g. `projects/<PROJECT_ID>/branches/<BRANCH_ID>/databases/<DB_ID>`).

skills/databricks-pipelines/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: databricks-pipelines
 description: Develop Lakeflow Spark Declarative Pipelines (formerly Delta Live Tables) on Databricks. Use when building batch or streaming data pipelines with Python or SQL. Invoke BEFORE starting implementation.
-compatibility: Requires databricks CLI (>= v0.292.0)
+compatibility: Requires databricks CLI (>= v0.294.0)
 metadata:
   version: "0.1.0"
 parent: databricks

skills/databricks/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "databricks"
 description: "Databricks CLI operations: auth, profiles, data exploration, and bundles. Contains up-to-date guidelines for Databricks-related CLI tasks."
-compatibility: Requires databricks CLI (>= v0.292.0)
+compatibility: Requires databricks CLI (>= v0.294.0)
 metadata:
   version: "0.1.0"
 ---
@@ -21,7 +21,7 @@ For specific products, use dedicated skills:
 ## Prerequisites
 
 1. **CLI installed**: Run `databricks --version` to check.
-   - **If the CLI is missing or outdated (< v0.292.0): STOP. Do not proceed or work around a missing CLI.**
+   - **If the CLI is missing or outdated (< v0.294.0): STOP. Do not proceed or work around a missing CLI.**
    - **Read the [CLI Installation](databricks-cli-install.md) reference file and follow the instructions to guide the user through installation.**
    - Note: In sandboxed environments (Cursor IDE, containers), install commands write outside the workspace and may be blocked. Present the install command to the user and ask them to run it in their own terminal.