databricks-bundles
Create and configure Declarative Automation Bundles (formerly Asset Bundles) with best practices for multi-environment deployments (CICD). Use when working with: (1) Creating new DAB projects, (2) Adding resources (dashboards, pipelines, jobs, alerts), (3) Configuring multi-environment deployments, (4) Setting up permissions, (5) Deploying or running bundle resources
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 skill description that clearly defines its scope around Declarative Automation Bundles with concrete actions and explicit trigger guidance. It includes both the current and legacy naming ('formerly Asset Bundles'), which aids discoverability. The enumerated use cases provide clear guidance for when Claude should select this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating DAB projects, adding resources (dashboards, pipelines, jobs, alerts), configuring multi-environment deployments, setting up permissions, and deploying/running bundle resources. | 3 / 3 |
Completeness | Clearly answers both 'what' (create and configure DABs with best practices for multi-environment deployments) and 'when' (explicit 'Use when working with...' clause listing five specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Declarative Automation Bundles', 'Asset Bundles', 'DAB', 'dashboards', 'pipelines', 'jobs', 'alerts', 'CICD', 'multi-environment deployments', 'permissions', 'bundle'. Covers both the current and former naming convention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific niche of Declarative Automation Bundles (DABs). The domain-specific terminology (DAB, Asset Bundles, bundle resources) and the enumerated use cases make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent concrete YAML examples and good progressive disclosure through referenced files and related skills. The main weaknesses are moderate verbosity (especially the Apps section and log monitoring details) and the lack of an explicit end-to-end deployment workflow with validation checkpoints for what is fundamentally a multi-step, multi-environment deployment process.
Suggestions
Add an explicit end-to-end deployment workflow (e.g., '1. Validate → 2. Deploy to dev → 3. Verify → 4. Deploy to prod') with validation checkpoints and error recovery steps
Trim the Apps section by removing the comparison table and condensing the log patterns into a shorter reference; move detailed app guidance to a separate file if needed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete YAML examples and tables, but includes some unnecessary explanations (e.g., the Apps 'Key Differences from Other Resources' table, verbose log pattern descriptions, and the 'What logs show' section add bulk). The Apps section is particularly lengthy and could be tightened. | 2 / 3 |
Actionability | Provides fully executable YAML configurations, concrete CLI commands, and copy-paste ready examples for every resource type. Path resolution is clearly documented with a table, and permission levels are explicitly listed per resource type. | 3 / 3 |
Workflow Clarity | The Common Commands section lists validate/deploy/run/destroy in a logical sequence, but there's no explicit workflow tying them together with validation checkpoints. For a multi-environment deployment skill involving potentially destructive operations (deploy --force, destroy), the lack of a clear 'validate → deploy → verify → promote' workflow with feedback loops is a gap. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview, well-signaled one-level-deep references to SDP_guidance.md and alerts_guidance.md, related skills section, and external documentation links. Content is appropriately split between inline essentials and referenced details. | 3 / 3 |
Total | 10 / 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-solutions/ai-dev-kit
- Commit
02aac8c
- 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.