CtrlK
BlogDocsLog inGet started
Tessl Logo

databricks-core

Databricks CLI operations: auth, profiles, data exploration, and bundles. Contains up-to-date guidelines for Databricks-related CLI tasks.

60

Quality

70%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/databricks-core/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is an excellent skill file that serves as a well-organized hub for Databricks CLI operations. It is concise, highly actionable with executable commands and critical anti-patterns, has clear workflow sequencing with explicit stop conditions, and demonstrates exemplary progressive disclosure by routing to dedicated reference files by task. The inclusion of common pitfalls (positional vs flag arguments, shell session isolation) adds significant practical value.

DimensionReasoningScore

Conciseness

The skill is lean and efficient throughout. It assumes Claude's competence, avoids explaining what Databricks is or how CLI tools work in general, and every section delivers actionable information without padding. The anti-pattern examples (❌ WRONG) earn their tokens by preventing common mistakes.

3 / 3

Actionability

Provides fully executable, copy-paste-ready CLI commands with correct syntax, including critical distinctions between positional and flag-based arguments. The troubleshooting table, anti-pattern examples, and shell session behavior notes are all concrete and immediately usable.

3 / 3

Workflow Clarity

The prerequisites section establishes a clear sequence (install → authenticate → select profile) with explicit stop conditions ('STOP. Do not proceed'). The profile selection workflow is clearly sequenced with validation. The Claude Code section explicitly addresses a subtle shell session pitfall with working vs non-working examples. The 'Required Reading by Task' table provides clear routing for different workflows.

3 / 3

Progressive Disclosure

Excellent hub-and-spoke structure: the SKILL.md serves as a concise overview with well-signaled one-level-deep references to dedicated files (CLI install, auth, data exploration, bundles) and product-specific skills (jobs, pipelines, apps, lakebase). The 'Required Reading by Task' table makes navigation task-driven and intuitive.

3 / 3

Total

12

/

12

Passed

Description

40%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear domain (Databricks CLI) and lists high-level capability areas, giving it reasonable distinctiveness. However, it lacks concrete action verbs, misses common user trigger terms, and critically omits any explicit 'when to use' guidance, significantly weakening its ability to be selected appropriately from a large skill set.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Databricks CLI commands, configuring Databricks authentication, deploying bundles, or exploring Databricks data.'

Replace category labels with concrete actions, e.g., 'Configure Databricks authentication and profiles, explore catalogs/schemas/tables, deploy and manage Databricks Asset Bundles via CLI.'

Include additional natural trigger terms users might say, such as 'databricks workspace', 'databricks jobs', 'dbx', 'unity catalog', or 'bundle deploy'.

DimensionReasoningScore

Specificity

Names the domain (Databricks CLI) and lists some action areas (auth, profiles, data exploration, bundles), but these are categories rather than concrete actions. It doesn't specify what exactly is done within each area (e.g., 'configure authentication tokens', 'deploy bundles', 'query tables').

2 / 3

Completeness

It describes what the skill covers (Databricks CLI operations) but has no explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is entirely missing, which per the rubric should cap completeness at 2, and since the 'what' is also somewhat vague, a score of 1 is appropriate.

1 / 3

Trigger Term Quality

Includes relevant keywords like 'Databricks', 'CLI', 'auth', 'profiles', 'bundles', and 'data exploration', which users might naturally say. However, it misses common variations like 'databricks-cli', 'dbx', 'workspace', 'jobs', 'deploy', or 'databricks connect'.

2 / 3

Distinctiveness Conflict Risk

The description targets a clear niche — Databricks CLI specifically — which is unlikely to conflict with other skills. The mention of Databricks-specific concepts like 'bundles' and 'profiles' further distinguishes it.

3 / 3

Total

8

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
databricks/devhub
Reviewed

Table of Contents

Is this your skill?

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.