ClaudeSuperPower

databricks-data-discovery

Skill

Discover, explore, and query Databricks data via Genie — the CLI equivalent of the Genie One MCP. MUST be invoked whenever the user asks to find or locate data ('what tables are in X', 'where does X live', 'which catalog/schema has Y'), answer a natural-language question about the data, or write a S

Install

git clone https://github.com/databricks/databricks-agent-skills.git ~/.claude/skills/databricks-data-discovery

What is databricks-data-discovery?

Discover, explore, and query Databricks data via Genie — the CLI equivalent of the Genie One MCP. MUST be invoked whenever the user asks to find or locate data ('what tables are in X', 'where does X live', 'which catalog/schema has Y'), answer a natural-language question about the data, or write a SQL query.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~77 tokens of context used while enabled, before you invoke anything

Documentation

README · ~6 min read

Databricks Data Discovery

This skill routes data work — decide first:

  • the request is about the data — finding it, asking questions of it, or generating SQL → delegate to Genie One: databricks genie ask -s <session-label> "..." (see Routing below).
  • writing files or anything else → use your own coding-agent tools.

Genie One just needs an authenticated CLI profile (the parent databricks-core skill covers auth/profiles if you need it) — but route the data request to Genie first; don't detour into manual catalog browsing.

Routing — Genie vs your coding agent

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills