Databricks Dabs

What it does

The source routes bundle structure, resource configuration, permissions and deployment into focused references. It treats validation and environment selection as part of the change, while noting that successful configuration validation does not catch every naming or runtime problem.

Best for

Teams maintaining jobs, pipelines, dashboards or applications as versioned Databricks configuration rather than a series of dashboard edits.

Tradeoffs and requirements

Bundles can create or update billable infrastructure. The correct workspace, profile and target must be explicit, and validation is not a deployment proof. Resource-specific permissions and names need checking against the actual account and current CLI behavior.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code; this catalog never runs it.

npx skills add https://github.com/databricks/databricks-agent-skills/tree/d50672205671c6d6edc847b1ddc36e7cba69bd32/skills/databricks-dabs --skill databricks-dabs

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Network Access — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

74/100 · Metadata coverage 80% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

0/100

0

Repository Health

85/100

85

Compatibility Evidence

80/100

80

Popularity

46/100

46

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Inspect the existing bundle and selected target, then change only the relevant resource definition. Review the deployment difference and run strict validation before an authorized operation in a development environment.

How to judge the result

Read back the deployed resource and run a representative job or application check. Confirm environment isolation, effective permissions and resource names, and retain configuration and state evidence needed to reverse an unsuccessful rollout.