quickstart

Configure Databricks authentication and MLflow settings for agent development.

Updated May 10, 2026
One-click install
npx skills add https://github.com/keqingli1129/agent-langgraph-one --skill quickstart-keqingli1129
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quickstart
Source: https://github.com/keqingli1129/agent-langgraph-one/tree/main/.claude/skills/quickstart
Command: npx skills add https://github.com/keqingli1129/agent-langgraph-one --skill quickstart-keqingli1129

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of configuring a local Databricks-backed agent development environment by creating the required authentication and MLflow settings.

Core Features & Use Cases

  • Environment bootstrap: Creates or updates a local .env with the Databricks CLI profile, MLflow tracking URI, and an auto-created experiment ID.
  • Workspace/app binding: Updates databricks.yml to set the app’s experiment_id and optionally bind the bundle to an existing Databricks app by name.
  • Safe re-runs: Supports idempotent behavior for both the MLflow experiment and Lakebase setup (skipping prompts when configs already exist).

Quick Start

Run the command: uv run quickstart.

Frequently Asked Questions about quickstart

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

FAQPage Schema
How do I set up a local Databricks agent development environment from scratch?

To set up a Databricks agent development environment, this Skill creates local authentication and MLflow configuration files automatically. It generates a `.env` with your Databricks CLI profile, MLflow tracking URI, and experiment ID, while updating `databricks.yml` for the ResponsesAgent workflow.

What prerequisites do I need to configure Databricks authentication for agent development?

Configuring Databricks authentication requires verifying specific tool prerequisites. You must have `uv`, Node 20, and the Databricks CLI installed on your system before generating the `.env` and MLflow configuration files.

Can I safely re-run environment setup if a .env file already exists?

Yes, environment setup supports safe re-runs with idempotent behavior. If configurations already exist, the Skill skips prompts and updates the `.env` and `databricks.yml` files without overwriting existing valid settings.

How do I bind my local MLflow configuration to an existing Databricks app?

You can bind local MLflow configuration to an existing Databricks app by passing the `--app-name` parameter. This updates `databricks.yml` to link the bundle to your specified app and automatically sets the required experiment ID.

Does this quickstart process automatically create an MLflow experiment in Databricks?

Yes, the quickstart process automatically creates an MLflow experiment in Databricks. It generates the experiment ID and writes it directly into your local `.env` file and `databricks.yml` configuration.

What is the best way to initialize Databricks MLflow tracking for first-time agent development?

The best way to initialize Databricks MLflow tracking is running `uv run quickstart`. This command validates prerequisites, creates the `.env` with authentication variables, and configures the MLflow tracking URI idempotently.