databricks-core
Databricks CLI operations: auth, profiles, data exploration, and bundles. Contains up-to-date guidelines for Databricks-related CLI tasks.
76
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/inventory-intelligence/template/.agents/skills/databricks-core/SKILL.mdQuality
Discovery
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 niche (Databricks CLI) and lists high-level capability areas, making it distinctive. However, it lacks concrete action verbs, misses some natural trigger terms, and critically omits any explicit 'Use when...' guidance, which weakens its ability to be reliably selected from a large skill set.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Databricks CLI commands, authentication setup, workspace configuration, bundle deployment, or data exploration via Databricks.'
Replace category labels with concrete actions, e.g., 'Configure Databricks authentication and profiles, explore catalog/schema/table data, deploy and manage Databricks Asset Bundles (DABs).'
Include additional natural trigger terms users might say, such as 'DABs', 'databricks workspace', 'dbx', 'databricks deploy', 'databricks jobs', or 'databricks token'.
| Dimension | Reasoning | Score |
|---|---|---|
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, this scores a 1. | 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', 'deploy', 'jobs', or 'DABs' that users might use. | 2 / 3 |
Distinctiveness Conflict Risk | Databricks CLI is a clear, specific niche that is unlikely to conflict with other skills. The mention of 'Databricks' combined with 'CLI' and specific sub-areas like 'bundles' and 'profiles' makes this distinctly identifiable. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that serves as an effective hub for Databricks CLI operations. It excels at conciseness by delivering only what Claude needs to know (shell session behavior, positional vs flag arguments, common wrong commands), provides fully executable examples, and has excellent progressive disclosure with clear routing to specialized skills and reference files. The anti-pattern examples (wrong commands that will fail) are particularly valuable for preventing common mistakes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what Databricks is, what CLI tools are, or other concepts Claude already knows. Every section delivers actionable information without padding, and the anti-patterns (wrong commands) are valuable additions that prevent common errors. | 3 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready commands with concrete examples. It includes correct and incorrect usage patterns, specific flags, positional argument syntax, and a troubleshooting table with direct solutions. The shell session caveat with working vs non-working examples is particularly actionable. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: check CLI installation → authenticate → select profile → execute commands. The prerequisites section has explicit stop conditions (STOP if CLI missing), the profile selection section has a clear numbered sequence, and the 'Required Reading by Task' table provides clear routing for different scenarios. For a skill that primarily orchestrates CLI commands rather than destructive batch operations, validation is appropriately handled. | 3 / 3 |
Progressive Disclosure | The skill is an excellent overview that clearly signals one-level-deep references: dedicated product skills listed at top, reference guides for installation/auth/data exploration linked at relevant points and summarized at bottom. The 'Required Reading by Task' table provides clear navigation. Content is appropriately split between the overview and referenced files. | 3 / 3 |
Total | 12 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- databricks/devhub
- Commit
6338825
- 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.