quickstart

Create Databricks authentication and project configuration files for agent development.

4|Updated May 9, 2026
One-click install
npx skills add https://github.com/victorlou/housing-assistant --skill quickstart-victorlou
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quickstart
Source: https://github.com/victorlou/housing-assistant/tree/main/app/app-templates/.claude/skills/quickstart
Command: npx skills add https://github.com/victorlou/housing-assistant --skill quickstart-victorlou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up a Databricks agent development environment and authentication can be slow and error-prone, especially the first time you run a template or switch workspaces.

Core Features & Use Cases

  • Initial environment setup: validates prerequisites (uv, nvm/Node 20, Databricks CLI) and performs first-time workspace configuration.
  • Authentication and config wiring: creates or updates .env and databricks.yml so local runs and deployments use the correct profile, MLflow experiment, and app binding.
  • Idempotent re-runs: safely reuses an existing .env/experiment/Lakebase configuration to avoid duplicate creation and repeated prompts.

Example use case: You cloned the repository for Databricks agent development on a new machine and need to authenticate, initialize MLflow experiment settings, and bind the bundle to an existing Databricks app before deploying.

Quick Start

Run the quickstart with a workspace URL to create your local configuration: uv run quickstart --host https://your-workspace.cloud.databricks.com.

Frequently Asked Questions about quickstart

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Databricks authentication and configure environment variables for agent development?

Databricks authentication setup is automated by creating a `.env` file containing the `DATABRICKS_CONFIG_PROFILE` and MLflow tracking settings. It validates prerequisites like uv and Node 20 to prepare your local environment for first-time workspace configuration.

What's the best way to initialize MLflow experiment settings and databricks.yml app binding?

Initialize MLflow experiment settings and app binding by running the quickstart command with your workspace URL. It updates `databricks.yml` to bind the bundle to an existing Databricks app and configures the correct profile for deployments.

Do I need the Databricks CLI installed to configure local environment variables and project configuration files?

Yes, Databricks CLI v0.283.0 or higher is required to authenticate and generate the project configuration files. The setup process validates the CLI installation alongside uv and nvm before applying any workspace configuration.

Can I safely re-run Databricks workspace configuration without duplicating MLflow experiments or Lakebase settings?

Yes, Databricks workspace configuration is idempotent, safely reusing existing `.env` files, MLflow experiments, and Lakebase configurations. This prevents duplicate resource creation and avoids repeated prompts during non-interactive CI-style setups.

Why does my Databricks bundle deployment fail when the .env file is missing?

Databricks bundle deployment fails without a `.env` file because the profile and MLflow tracking settings are absent. The setup process applies to non-interactive CI-style runs by generating these required environment variables automatically.

When should I manually configure Databricks authentication instead of automating environment setup?

Manual Databricks authentication configuration is unnecessary for first-time template runs or workspace switches. Automating environment setup handles `.env` creation and `databricks.yml` updates, unless you require custom profile wiring outside standard agent development.