Set up the Databricks chatbot app for local development and deployment. Use when: (1) First time setup, (2) User says 'quickstart', 'set up', 'authenticate', or 'configure databricks', (3) No .env file exists, (4) User says 'enable feedback', 'feedback widget', or 'MLFLOW_EXPERIMENT_ID'.
70
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Run the interactive setup script from the e2e-chatbot-app-next/ directory:
./scripts/quickstart.shThe script walks through the following steps interactively:
databricks auth loginMLFLOW_EXPERIMENT_ID in .envdatabricks.ymlMLFLOW_EXPERIMENT_ID in app.yamldb-chatbot-dev-<username>, max 30 chars)databricks bundle deploy and starts the appIf you skipped feedback during quickstart, or ran the script before feedback support was added, enable it manually:
1. Find the experiment name for your endpoint:
npx tsx scripts/get-experiment-id.ts --endpoint <your-serving-endpoint-name>For Agent Bricks (Knowledge Assistant / Multi-Agent Supervisor):
npx tsx scripts/get-experiment-id.ts --agent-brick <agent-brick-name>2. Set MLFLOW_EXPERIMENT_ID in .env (for local dev):
MLFLOW_EXPERIMENT_ID=<experiment-name-from-step-1>3. Configure databricks.yml — uncomment and fill in the experiment resource:
- name: experiment
description: "MLflow experiment for collecting user feedback"
experiment:
name: "<experiment-name-from-step-1>"
permission: CAN_EDIT4. Configure app.yaml — uncomment the env var:
- name: MLFLOW_EXPERIMENT_ID
valueFrom: experiment5. Redeploy:
databricks bundle deploy
databricks bundle run databricks_chatbot| Issue | Solution |
|---|---|
| Feedback widget not showing after setup | Restart dev server; env vars are read at startup |
get-experiment-id.ts fails with auth error | Run databricks auth login first |
| No experiment found for endpoint | Only custom agents and Agent Bricks endpoints have linked experiments; Foundation Model endpoints do not support feedback |
| Feedback submission returns 403 | App service principal is missing CAN_EDIT on the experiment — check permission: CAN_EDIT in databricks.yml |
| "Instance name is not unique" on deploy | Run ./scripts/cleanup-database.sh to remove the old database instance |
74c0cd0
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.