Skip to main content
ZICQ

Skills ZICQ category:Agent Workflows databricks-core

Databricks Core

Databricks CLI operations and the parent/entry-point skill for Databricks CLI use: authentication, profile selection, and bundles. Load this first for CLI, auth, profile, and bundle tasks, then load the matching product skill. For finding or exploring data, answering questions about the data, or generating SQL, load the databricks-data-discovery skill (it routes to Genie One). Contains up-to-date guidelines for Databricks-related CLI tasks.

1468 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Databricks CLI operations and the parent/entry-point skill for Databricks CLI use: authentication, profile selection, and bundles. Load this first for CLI, auth, profile, and bundle tasks, then load the matching product skill. For finding or exploring data, answering questions about the data, or generating SQL, load the databricks-data-discovery skill (it routes to Genie One). Contains up-to-date guidelines for Databricks-related CLI tasks.

When to use it

The official description does not include a separate “Use when”. Per the spec, agents activate this skill when the task matches keywords in that description.

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Databricks; Product Skills; Prerequisites; Profile Selection - CRITICAL; Claude Code - IMPORTANT; WORKS: --profile flag.

File analysis

File analysis: instruction-only skill (SKILL.md). The agent loads the full body when activated.

DatabricksProduct SkillsPrerequisitesProfile Selection - CRITICALClaude Code - IMPORTANTWORKS: --profile flagWORKS: chained with &&DOES NOT WORK: separate commandsData Exploration — Use AI Toolsdiscover table structure (columns, types, sample data, stats)run ad-hoc SQL queriesfind the default warehouse

Compatibility:Requires databricks CLI (>= v1.0.0)

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
databricks-core
description
Databricks CLI operations and the parent/entry-point skill for Databricks CLI use: authentication, profile selection, and bundles. Load this first for CLI, auth, profile, and bundle tasks, then load the matching product skill. For finding or exploring data, answering questions about the data, or generating SQL, load the databricks-data-discovery skill (it routes to Genie One). Contains up-to-date guidelines for Databricks-related CLI tasks.
compatibility
Requires databricks CLI (>= v1.0.0)
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "databricks-core" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-1d39c6ee95a52c2d-Databricks-Core.html
Save it as .cursor/skills/databricks-core/SKILL.md or .claude/skills/databricks-core/SKILL.md and keep the frontmatter name and description exactly as-is.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/databricks/databricks-agent-skills' --list

npx skills add 'https://github.com/databricks/databricks-agent-skills' --skill 'databricks-core'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- name: "databricks-core" description: "Databricks CLI operations and the parent/entry-point skill for Databricks CLI use: authentication, profile selection, and bundles. Load this first for CLI, auth, profile, and bundle tasks, then load the matching product skill. For finding or exploring data, answering questions about the data, or generating SQL, load the databricks-data-discovery skill (it routes to Genie One). Contains up-to-date guidelines for Databricks-related CLI tasks." compatibility: Requires databricks CLI (>= v1.0.0) metadata: version: "0.1.0" --- # Databricks Core skill for Databricks CLI, authentication, and data exploration. ## Product Skills For specific products, use dedicated skills: - **databricks-jobs** - Lakeflow Jobs development and deployment - **databricks-pipelines** - Lakeflow Spark Declarative Pipelines (batch and streaming data pipelines) - **databricks-apps** - Full-stack TypeScript app development and deployment - **databricks-lakebase** - Lakebase Postgres Autoscaling project management - **databricks-model-serving** - Model Serving endpoint management and inference For **data discovery, exploration, and query generation** — finding tables, answering natural-language questions about the data, or generating SQL — use **databricks-data-discovery** (it asks Genie One first, then falls back to manual exploration). If it isn't installed, use the AI-tool commands below and [Manual Data Exploration](manual-data-exploration.md). ## Prerequisites 1. **CLI installed and current**: the CLI must be >= v1.0.0. A CLI that is present but too old is not "good enough" — it must be upgraded, not worked around. - **Run the floor check in [CLI Installation](databricks-cli-install.md).** If it reports `UPGRADE` or `INSTALL`: STOP and follow that reference file to upgrade or install — do not proceed or tell the user their CLI is fine. - **If another skill routed you here to upgrade** (it needs a newer CLI than v1.0.0 — e.g. `databricks-setup-local` needs v1.12.0), that skill already detected the gap. A passing v1.0.0 floor check is not enough: follow the Update / repair procedures to install the latest stable, which satisfies any skill's floor. - 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. - **Exception:** If CLI installation is blocked (sandboxed containers, restricted environments), ask the user whether to fall back to direct REST API calls using `DATABRICKS_HOST` and `DATABRICKS_TOKEN` environment variables if present in the shell. See the [Databricks REST API docs](https://docs.databricks.com/api/workspace/introduction). 2. **Authenticated**: `databricks auth profiles` - If not: see [CLI Authentication](databricks-cli-auth.md) ## Profile Selection - CRITICAL **NEVER auto-select a profile.** 1. List profiles: `databricks auth profiles` 2. Present ALL profiles to user with workspace URLs 3. Let user choose (even if only one exists) 4. Offer to create new profile if needed ## Claude Code - IMPORTANT Each Bash command runs in a **separate shell session**. ```bash # WORKS: --profile flag databricks apps list --profile my-workspace # WORKS: chained with && export DATABRICKS_CONFIG_PROFILE=my-workspace && databricks apps list # DOES NOT WORK: separate commands export DATABRICKS_CONFIG_PROFILE=my-workspace databricks apps list # profile not set! ``` ## Data Exploration — Use AI Tools **Use these instead of manually navigating catalogs/schemas/tables:** ```bash # discover table structure (columns, types, sample data, stats) databricks experimental aitools tools discover-schema catalog.schema.table --profile # run ad-hoc SQL queries databricks experimental aitools tools query "SELECT * FROM table LIMIT 10" --profile # find the default warehouse databricks experimental aitools tools get-default-warehouse --profile ``` **Names are literal.** Use catalog/schema/table names exactly as given — never change a hyphen to an underscore or otherwise normalize them. In SQL, backtick-quote any name part with special characters (e.g. `` `my-catalog`.schema.table ``); unquoted hyphens cause a parse error. These commands are first-class for running known SQL and profiling — Genie isn't required for that. For natural-language data questions, locating data you can't pin down, or generating a query from a question, prefer the `databricks-data-discovery` skill (above) if it's installed. See [Manual Data Exploration](manual-data-exploration.md) for the full command surface, quoting rules, and troubleshooting. ## Quick Reference **⚠️ CRITICAL: Some commands use positional arguments, not flags** ```bash # current user databricks current-user me --profile # list resources databricks apps list --profile databricks jobs list --profile databricks clusters list --profile databricks warehouses list --profile databricks pipelines list --profile databricks serving-endpoints list --profile # ⚠️ Unity Catalog — POSITIONAL arguments (NOT flags!) databricks catalogs list --profile # ✅ CORRECT: positional args databricks schemas list --profile databricks tables list --profile databricks tables get .. --profile # ❌ WRONG: these flags/commands DON'T EXIST # databricks schemas list --catalog-name ← WILL FAIL # databricks tables list --catalog ← WILL FAIL # databricks sql-warehouses list ← doesn't exist, use `warehouses list` # databricks execute-statement ← doesn't exist, use `experimental aitools tools query` # databricks sql execute ← doesn't exist, use `experimental aitools tools query` # When in doubt, check help: # databricks schemas list --help # get details databricks apps get --profile databricks jobs get --job-id --profile databricks clusters get --cluster-id --profile # bundles databricks bundle init --profile databricks bundle validate --profile databricks bundle deploy -t --profile databricks bundle run -t --profile ``` ## Troubleshooting | Error | Solution | |-------|----------| | `cannot configure default credentials` | Use `--profile` flag or authenticate first | | `configuration does not support OAuth tokens` | The command requires OAuth (e.g., `databricks apps logs`). Re-authenticate with `databricks auth login --host --profile `. See [CLI Authentication](databricks-cli-auth.md). | | `PERMISSION_DENIED` | Check workspace/UC permissions | | `RESOURCE_DOES_NOT_EXIST` | Verify resource name/id and profile | ## Required Reading by Task | Task | READ BEFORE proceeding | |------|------------------------| | First time setup | [CLI Installation](databricks-cli-install.md) | | Auth issues / new workspace | [CLI Authentication](databricks-cli-auth.md) | | Exploring tables/schemas | [Manual Data Exploration](manual-data-exploration.md) (or `databricks-data-discovery` if installed) | | Deploying jobs/pipelines | Use `/databricks-dabs` | ## Reference Guides - [CLI Installation](databricks-cli-install.md) - [CLI Authentication](databricks-cli-auth.md) - [Manual Data Exploration](manual-data-exploration.md)

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Superpowers

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…