Databricks CLI
aehrc/pathling
Expert guidance for using the Databricks CLI to manage Databricks workspaces, clusters, jobs, pipelines, Unity Catalog, SQL warehouses, serving endpoints, secrets, bundles, and all other Databricks…
Unity Catalog metric views: define, create, query, and manage governed business metrics in YAML.
Install Databricks Metric Views
$ npx skills add databricks/databricks-agent-skills --skill databricks-metric-views -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install databricks/databricks-agent-skills databricks-metric-views --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/databricks/databricks-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/databricks-metric-views .claude/skills/databricks-metric-views && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "databricks-metric-views" agent skill from https://github.com/databricks/databricks-agent-skills/tree/main/skills/databricks-metric-views into .claude/skills/databricks-metric-views/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databricks-metric-views", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/databricks/databricks-agent-skills/tree/main/skills/databricks-metric-viewsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add databricks/databricks-agent-skills --skill databricks-metric-views -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install databricks/databricks-agent-skills databricks-metric-views --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/databricks/databricks-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/databricks-metric-views .agents/skills/databricks-metric-views && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "databricks-metric-views" agent skill from https://github.com/databricks/databricks-agent-skills/tree/main/skills/databricks-metric-views into .agents/skills/databricks-metric-views/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databricks-metric-views", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add databricks/databricks-agent-skills --skill databricks-metric-views -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install databricks/databricks-agent-skills databricks-metric-views --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/databricks/databricks-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/databricks-metric-views .cursor/skills/databricks-metric-views && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "databricks-metric-views" agent skill from https://github.com/databricks/databricks-agent-skills/tree/main/skills/databricks-metric-views into .cursor/skills/databricks-metric-views/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databricks-metric-views", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/databricks/databricks-agent-skills.git --path skills/databricks-metric-views--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add databricks/databricks-agent-skills --skill databricks-metric-views -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install databricks/databricks-agent-skills databricks-metric-views --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/databricks/databricks-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/databricks-metric-views .gemini/skills/databricks-metric-views && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "databricks-metric-views" agent skill from https://github.com/databricks/databricks-agent-skills/tree/main/skills/databricks-metric-views into .gemini/skills/databricks-metric-views/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databricks-metric-views", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install databricks/databricks-agent-skills databricks-metric-viewsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add databricks/databricks-agent-skills --skill databricks-metric-views -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/databricks/databricks-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/databricks-metric-views .github/skills/databricks-metric-views && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "databricks-metric-views" agent skill from https://github.com/databricks/databricks-agent-skills/tree/main/skills/databricks-metric-views into .github/skills/databricks-metric-views/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databricks-metric-views", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add databricks/databricks-agent-skills --skill databricks-metric-views -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install databricks/databricks-agent-skills databricks-metric-views --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/databricks/databricks-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/databricks-metric-views .opencode/skills/databricks-metric-views && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "databricks-metric-views" agent skill from https://github.com/databricks/databricks-agent-skills/tree/main/skills/databricks-metric-views into .opencode/skills/databricks-metric-views/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databricks-metric-views", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
databricks-metric-views- GitHub stars
- 345
- Token cost
- ~2k tokens
- SKILL.md length
- 725 words
- Files
- 7 (incl. references, assets)
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Unity Catalog metric views: define, create, query, and manage governed business metrics in YAML.
- Building standardized KPIs
- SKILL.md covers When to Use, First: can this even be a…, Prerequisites and Metric View Lifecycle, plus 2 more sections
- Calls databricks
- Revenue metrics
What it does
Databricks Metric Views is an agent skill from databricks/databricks-agent-skills, published by the product's own GitHub organization. Unity Catalog metric views: define, create, query, and manage governed business metrics in YAML. Use when building standardized KPIs, revenue metrics, order analytics, or any reusable business metrics that need consistent definitions across teams and tools.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files and assets (for example `agents/openai.yaml`, `references/create-patterns.md` and `references/metric-view-advisor.md`). Compatibility notes: Requires databricks CLI (= v1.0.0)
It sits in Game Development, covering OKRs and executive reporting. It works with Databricks and SQL. The repository describes itself as: Databricks AI Tools: skills and plugins for building on Databricks with Claude Code, Cursor, Codex, GitHub Copilot, and other AI coding agents.
When your agent uses it
- Building standardized KPIs
- Revenue metrics
- Order analytics
- Any reusable business metrics that need consistent definitions across teams and tools
Example prompts
- “/databricks-metric-views”
Requirements
- Compatibility (from SKILL.md): Requires databricks CLI (>= v1.0.0)
What it can do on your machine
Read from SKILL.md and the folder at commit f4fcec5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
databricks
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.databricks.comgithub.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires databricks CLI (>= v1.0.0)
From compatibility in the SKILL.md frontmatter.
Context cost
Databricks Metric Views loads about 2k tokens when it runs, and up to ~22k if it reads all its reference files. Until then it costs about 70 tokens; SKILL.md has 725 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 725 words (~1,978 tokens).
“Define reusable, governed business metrics in YAML that separate measure definitions from dimension groupings for flexible querying.”
- name
- databricks-metric-views
- compatibility
- Requires databricks CLI (>= v1.0.0)
- metadata.version
- 0.1.0
- parent
- databricks-core
Files
SKILL.md and 6 other files (references, assets) in skills/databricks-metric-views of databricks/databricks-agent-skills.
- SKILL.md
- agents/openai.yaml
- assets/databricks.png
- assets/databricks.svg
- references/create-patterns.md
- references/metric-view-advisor.md
- references/query-patterns.md
Open the folder on GitHubat commit f4fcec5
Compare with similar skills
Databricks Metric Views next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Databricks Metric Views this skilldatabricks/databricks-agent-skills | 345 | — | ~2k | Automated safety check: Pass | Custom licence | |
| Databricks CLIaehrc/pathling | 137 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| SQL Correctnessdatabricks-solutions/ai-dev-kit | 1.9k | — | ~438 | Automated safety check: Pass | Custom licence | |
| Optimizing Databricks SQLAltimateAI/data-engineering-skills | 127 | — | ~6.7k | Automated safety check: Pass | MIT | |
| Tool Selectiondatabricks-solutions/ai-dev-kit | 1.9k | — | ~519 | Automated safety check: Pass | Custom licence | |
| Mendix Odata Pushdownmendixlabs/mxcli | 128 | — | ~2.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
SQL Correctness
databricks-solutions/ai-dev-kit
SQL evaluation criteria for Databricks. An agent skill from databricks-solutions/ai-dev-kit.
Optimizing Databricks SQL
AltimateAI/data-engineering-skills
Analyze DBSQL queries, including SQL embedded in notebooks (spark.sql(...), %sql cells), for anti-patterns, lint issues, and performance problems, using Databricks-specific dialect and platform…
Tool Selection
databricks-solutions/ai-dev-kit
Evaluates whether the agent selected appropriate MCP tools instead of shell workarounds.
Mendix Odata Pushdown
mendixlabs/mxcli
Push OData query options into the SQL of a Mendix resource served by a read microflow, so $filter, $orderby, $top, $skip, $count and the key lookup reach the database instead of being silently…
Databricks
rocky-data/rocky
Databricks REST API and SQL reference for Rocky's warehouse adapter.
More from databricks/databricks-agent-skills
All 32 skills in this repo- Official
Databricks Dbsql
databricks/databricks-agent-skills
Databricks SQL (DBSQL) advanced features and SQL warehouse capabilities.
- Official
Databricks Synthetic Data Gen
databricks/databricks-agent-skills
Generate realistic synthetic data using Spark + Faker (strongly recommended).
- Official
Databricks Model Serving
databricks/databricks-agent-skills
Databricks Model Serving endpoint lifecycle and ops. An agent skill from databricks/databricks-agent-skills.
- Official
Databricks Python SDK
databricks/databricks-agent-skills
Databricks development guidance including Python SDK, Databricks Connect, CLI, and REST API.
- Official
Databricks Spark Structured Streaming
databricks/databricks-agent-skills
Comprehensive guide to Spark Structured Streaming for production workloads.
- Official
Databricks App Design
databricks/databricks-agent-skills
Design the UX of custom-code Databricks Apps (AppKit/React) data screens — KPI/overview pages, reports, charts, tables, and Genie/chat data assistants — mapped to concrete AppKit components.
Related
Works with
Categories
Questions about Databricks Metric Views
What does Databricks Metric Views do?
Unity Catalog metric views: define, create, query, and manage governed business metrics in YAML. Databricks Metric Views is an agent skill from databricks/databricks-agent-skills, published by the product's own GitHub organization. Unity Catalog metric views: define, create, query, and manage governed business metrics in YAML.
When should I use Databricks Metric Views?
Databricks Metric Views fits situations like: building standardized KPIs; revenue metrics; order analytics; any reusable business metrics that need consistent definitions across teams and tools.
How do I install Databricks Metric Views in Claude Code?
Run `npx skills add databricks/databricks-agent-skills --skill databricks-metric-views -a claude-code`. Or copy the skill folder (skills/databricks-metric-views in databricks/databricks-agent-skills) into .claude/skills/databricks-metric-views in your project. Claude Code loads it when a task matches its description.
How do I install Databricks Metric Views in Codex?
Run `npx skills add databricks/databricks-agent-skills --skill databricks-metric-views -a codex`. Or copy the skill folder (skills/databricks-metric-views in databricks/databricks-agent-skills) into .agents/skills/databricks-metric-views in your project. Codex loads it when a task matches its description.
Can I use Databricks Metric Views in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add databricks/databricks-agent-skills --skill databricks-metric-views -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/databricks-metric-views, .gemini/skills/databricks-metric-views, .github/skills/databricks-metric-views and .opencode/skills/databricks-metric-views in your project.
What does Databricks Metric Views need to run?
Going by SKILL.md and its folder, Databricks Metric Views needs the command-line tools its instructions call (databricks). Compatibility (from SKILL.md): Requires databricks CLI (>= v1.0.0).
Does Databricks Metric Views access the network?
SKILL.md names 2 domains. As links in the text: docs.databricks.com and github.com. This is read from the text; nothing was executed.
Is Databricks Metric Views safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Databricks Metric Views use?
Databricks Metric Views has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Databricks Metric Views use?
About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 20k tokens, read only when the agent opens those files.
What are the alternatives to Databricks Metric Views?
Skills that share tags, products or a category with Databricks Metric Views: Databricks CLI (aehrc/pathling, 137 stars), SQL Correctness (databricks-solutions/ai-dev-kit, 1.9k stars), Optimizing Databricks SQL (AltimateAI/data-engineering-skills, 127 stars) and Tool Selection (databricks-solutions/ai-dev-kit, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Databricks Metric Views?
databricks (a GitHub organization, an official publisher) maintains it in databricks/databricks-agent-skills, which has 345 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 6, 2026.
Source: databricks/databricks-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.