[anshul0713]

Changes

databricks air run --help now names the databricks-ai-runtime agent skill and gives the install command, below the -h config lookup lines:

  databricks air run -h config.compute.accelerator_type   one field

To have a coding agent write the YAML and follow the run, install the
databricks-ai-runtime skill:

  databricks aitools install --skills-only --skills databricks-ai-runtime

• The install command is now a constant, skillInstallCommand, in cmd/air/runconfig.go. The -h config skill note uses it as well.
• The air -h footer in cmd/air/air.go still has its own copy of the command. I left that file alone because aitools: Hint the AI Runtime skill only on air subcommands #7622 edits the same footer. It can move to the constant after that PR lands.

Why

Coding agents read air run --help right before they write a workload YAML, so this page should point to the skill.

• On v1.26.0 the skill appears only in air run -h config.
• On main, [air] Reorganize databricks air help around the run lifecycle #7512 added it to the air -h footer too. air run --help still doesn't mention it.
• aitools: Hint the AI Runtime skill only on air subcommands #7622 makes the install hint name this skill on air subcommands. That hint runs from PersistentPreRunE, and cobra doesn't run that for --help. Help text is the only way to show the skill on help pages.

Tests

• New unit test TestRunHelpPointsToAgentSkill in cmd/air/air_test.go.
• Regenerated acceptance/air/config-help/output.txt with -update. The only diff is the 5 new lines in air run --help.
• Passing: go test ./acceptance -run 'TestAccept/air/', go vet ./cmd/air/, ./task lint-q and ./task ws.
• go test ./cmd/air/ passes except TestLogsCommandRepeatsRunLinkAfterStreaming. That test fails the same way on an unmodified origin/main checkout (bdb37ab) in this environment.

This pull request and its description were written by Isaac.

[github-actions]

Thanks for the contribution! This pull request was opened from a fork.

If you're a member of the Databricks organization, please request access to the cli-contrib team and open your pull request from a branch in this repository instead of a fork — fork PRs don't run integration tests automatically and have reduced CI access.

If you're an external contributor, no action is needed; a maintainer will review your pull request.

[anshul0713]

@anton-107 this PR is from a fork, so every task test job and validate-generated stop at the JFrog OIDC step before any test runs (same as #7639 and #7640). Locally on main + this branch, go test ./acceptance -run TestAccept/air/, ./task lint-q and ./task check-changelog pass. Could you either re-open it from a branch in this repo (as was done for #7575 → #7576) so CI can run, or trigger CI another way? I also moved the changelog fragment to .nextchanges/air/ (f5a0a06). Thanks!

[github-actions]

An authorized user can trigger integration tests manually by following the instructions below:

Trigger:
go/deco-tests-run/cli

Inputs:

• PR number: 7628
• Commit SHA: f5a0a06a7a1daa3034b6ce858a6efbc93f40155c

Checks will be approved automatically on success.