Create, configure, validate, deploy, run, and manage DABs — Declarative Automation Bundles (formerly Databricks Asset Bundles) — for Databricks resources including dashboards, jobs, pipelines, alerts, volumes, and apps
76
63%
Does it follow best practices?
Impact
100%
2.63xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/content-moderator/template/.agents/skills/databricks-dabs/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent specificity and distinctiveness, covering both the actions and the resource types comprehensively. The inclusion of both the current name (Declarative Automation Bundles) and former name (Databricks Asset Bundles) is a smart touch for trigger matching. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about DABs, Databricks bundles, deploying Databricks resources, or managing bundle configurations.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions (create, configure, validate, deploy, run, manage) and specific resource types (dashboards, jobs, pipelines, alerts, volumes, apps). Very detailed about what the skill does. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions and resources, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the action verbs and resource types. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'DABs', 'Declarative Automation Bundles', 'Databricks Asset Bundles' (the former name), plus specific resource types like 'dashboards', 'jobs', 'pipelines'. The inclusion of the former name is particularly helpful for users who may use either term. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — DABs/Declarative Automation Bundles is a very specific Databricks concept with clear niche terminology. Unlikely to conflict with other skills due to the specialized domain and explicit naming of the technology. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
44%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions well as a routing/index document with excellent progressive disclosure to reference files, but it lacks actionable content in the body itself. The absence of a concrete end-to-end workflow (create → configure → validate → deploy → run) and executable examples means Claude would need to load reference files for almost any task, making the SKILL.md itself minimally useful as standalone guidance.
Suggestions
Add a concrete quick-start workflow showing the full sequence: create bundle → configure databricks.yml → validate → deploy → run, with actual commands at each step and explicit validation checkpoints.
Include a minimal executable databricks.yml example (even 10-15 lines) so Claude has a concrete starting template without needing to load reference files.
Remove the 'When to Use This Skill' section — it restates the opening line and is metadata Claude doesn't need in the body content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'When to Use This Skill' section is somewhat redundant given the opening line already states the scope. The general guidelines are reasonably tight but include some obvious advice like 'use reference documentation' and 'preserve existing structure' that Claude would already know. | 2 / 3 |
Actionability | The skill provides one concrete command (`bundle validate --strict --target <target>`) and mentions a naming convention, but lacks executable code examples, specific YAML snippets, or copy-paste-ready configurations. Most guidance is directional rather than concrete, deferring to reference files. | 2 / 3 |
Workflow Clarity | There is no clear multi-step workflow defined. The guidelines mention validation but don't sequence the full create → configure → validate → deploy → run workflow. For a skill covering deployment and configuration of resources, the absence of an explicit sequenced workflow with validation checkpoints is a significant gap. | 1 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clearly signaled, one-level-deep references to five specific topic files. Each reference is labeled with a brief description of its contents, making navigation easy and appropriate. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
6338825
Table of Contents
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.