databricks-workspace-sync

To sync local files with a Databricks workspace, use this skill to transfer directories of notebooks, Python scripts, and SQL files via the Databricks CLI. It requires profile configuration and absolute workspace paths to perform safe, repeatable uploads and downloads.

Yes, you can download notebooks and Python scripts from Databricks to your local environment. The skill supports bidirectional syncing to pull workspace assets locally, which is useful for project code backups and offline development.

The supported file formats when syncing code to Databricks include Jupyter notebooks (.ipynb), Python scripts (.py), and SQL files. The skill handles automatic format detection during upload and download transfers.

Yes, you need the Databricks CLI installed and configured with a valid profile to sync workspace files. The skill relies on this CLI to execute project-wide transfers and manage assets across teams safely.

The best way to back up Databricks workspace assets locally is using a bidirectional sync skill that downloads notebooks and scripts via the CLI. This provisions consistent environments and ensures your project code is safely backed up.

Syncing Databricks notebooks uses absolute workspace paths to ensure safe and repeatable file transfers. This approach prevents ambiguity during project-wide syncing and guarantees assets are uploaded to or downloaded from the correct directories.