Agent skill · databricks
databricks-setup-local
Previews, provisions, or diagnoses a uv-managed local Python .venv with `databricks environments setup-local`. Use when the user wants to set up or fix one for Databricks Connect, cluster or serverless compute, `--job-task`, or a bundle target, or when setup-local fails.
What it needs
About 2k tokens when loaded.
What this skill does
Databricks Setup-Local REQUIRED FIRST: Use databricks-core for CLI, authentication, and profile selection. Never use a default profile. For an existing environment, use databricks-execution-compute. Workflow 1. Check CLI and authentication Prefer the latest stable CLI; no online lookup is required. Compare the full semantic version: v0.299.1 is older than v1.12.0. If missing or older, or setup-local is absent from help, reports unknown command, or rejects a documented flag, stop. Use databricks-core to upgrade with approval and verify; never recreate setup-local manually. Use the selected profile for every workspace command. Do not convert another package manager without approval. 2. Confirm the project directory Confirm the root containing (or intended to contain) pyproject.toml, .venv, and uv.lock; ask if multiple roots are plausible. Use it for preview and apply. It must be greenfield or uv-managed, but need not be writable for preview. 3. Select one target Choose exactly one branch: Cluster: use --cluster-id <ID> or --cluster-name <NAME>. If unknown, list clusters with the selected profile and ask; see examples. Serverless: use --serverless-version <N>. No version-list command exists; ask if unspecified. Job task: use --job-task <JOBID>.<TASKKEY>. If the task is unknown, run databricks jobs get <JOBID> --profile <PROFILE> --output json, present task keys, and ask. Bundle: a project with databricks.yml. Use databricks-dabs to inspect its root and selected target. Omit compute flags only when that target resolves supported classic or serverless compute; otherwise ask. Add --target <BUNDLETARGET> for a named target. Never combine compute flags. If no branch resolves, ask the user. 4. Preview Dry-run first; it writes and installs nothing: For bundles, <TARGETARGS> is empty or --target <BUNDLETARGET>. Default to normal mode. Use --constraints-only only when the user explicitly does not want this command managing databricks-connect. See JSON output and examples. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills databricks/databricks-setup-local--d7222e