mcpbeat

Databricks AI Runtime

databricks/databricks-ai-runtime

Databricks AI Runtime (`air`) CLI — the command-line tool for submitting and managing GPU training workloads on Databricks serverless compute. Use for: running `air` workloads, custom Docker image setup, environment configuration, and troubleshooting `air` jobs.

8k tokens
context cost
the whole folder, loaded on every use
5
files
instructions only
0
copies elsewhere
how many repositories repackaged it
236
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/databricks/databricks-agent-skills --skill databricks-ai-runtime

The instruction itself

2 sections, as written by the author

Databricks AI Runtime (air) CLI

Databricks AI Runtime (air) is a CLI tool for submitting GPU training workloads to Databricks serverless compute. It manages environment setup, distributed training configuration, and workload lifecycle — without requiring you to manage clusters or infrastructure.

A typical workload YAML looks like:

experiment_name: my-training-job
compute:
  num_accelerators: 1
  accelerator_type: GPU_1xA10
environment:
  dependencies:
    - mlflow
  version: "AI5"
command: echo "Hello World"

Submit with air run --file workload.yaml -p <databricks_config_profile>.

Bring your own custom Docker images

Use a custom Docker image instead of environment.version when your workload needs specific system libraries, CUDA extensions (flash-attn, apex, custom kernels), or dependencies that don't fit environment.dependencies.

Read docker-images.md for step-by-step guidance on:

  • Using Databricks-provided base images
  • Dockerfile patterns
  • Pre-build compatibility checklist (CUDA/driver, PyTorch, NCCL, EFA/RDMA)
  • Registering images with air register image

How to use it

Copy the folder

Take databricks/databricks-ai-runtime from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.