| name | databricks-dabs |
| description | Create, configure, validate, deploy, run, and manage Declarative Automation Bundles (DABs, formerly Databricks Asset Bundles). Use when working with Databricks resources via DABs including dashboards, jobs, pipelines, alerts, volumes, and apps. |
Declarative Automation Bundles (DABs)
Use this skill for any bundle-related request including creating, configuring, validating, deploying, running, and managing Databricks resources through DABs.
Reference Documentation
The following reference files provide detailed guidance for specific bundle tasks:
- Bundle Structure - Bundle structure, databricks.yml configuration, resource definitions, path resolution, variables, and multi-environment targets
- SDP Pipelines - Spark Declarative Pipeline configurations for DABs
- SQL Alerts - SQL Alert schemas and configuration (critical - API differs from other resources)
- Deploy and Run - Validation, deployment, running resources, monitoring logs, and troubleshooting common issues
- Resource Permissions - Permission levels and access control for bundle resources, per-resource-type levels, grants vs permissions
When to Use This Skill
Load this skill for any request involving:
- Creating new bundle projects or resources
- Configuring databricks.yml or resource YAML files
- Setting up multi-environment deployments (dev/prod targets)
- Deploying or running bundle resources
- Managing permissions for bundle resources
- Troubleshooting bundle validation or deployment errors
- Working with specific resource types (dashboards, jobs, pipelines, alerts, volumes, apps)
General Guidelines
- Always validate after configuration changes - Use
bundle validate --strict --target <target> after any change
- Use reference documentation - Consult the appropriate reference file for detailed patterns and examples
- Follow naming conventions - Resource files should use
<name>.<resource_type>.yml format
- Path resolution is critical - Paths differ based on file location (see Bundle Structure reference)
- Preserve existing structure - Keep user comments and structure when editing YAML files
- Use variables - Parameterize catalog, schema, and warehouse for multi-environment support
