# Doca upgrade

> Doca upgrade is an open-source agent skill. Changing DOCA versions safely: upgrading or downgrading the host DOCA packages, refreshing the BlueField BFB, bumping the NGC DOCA container. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.

- **Kind:** Skill
- **Pricing:** Open source
- **Platforms:** Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
- **Website:** https://github.com/NVIDIA/skills/tree/main/skills/doca-upgrade
- **Repository:** https://github.com/nvidia/skills
- **GitHub stars:** 4,037
- **License:** Apache-2.0
- **Skill name:** doca-upgrade
- **Collection:** https://github.com/NVIDIA/skills
- **Listing updated:** 2026-11-17

## About

Changing DOCA versions safely: upgrading or downgrading the host DOCA packages, refreshing the BlueField BFB, bumping the NGC DOCA container tag, or rolling back, with the discipline detect -> report -> ASK -> only then a guided upgrade. Trigger on "is there a newer DOCA", "I want the newest DOCA features, can I just apt upgrade in place", "should I move to the next release", "the upgrade stopped midway and dpkg is in a broken state", "my component is being deprecated, what now", or "roll me back", even without the word upgrade. Detect what is installed, find the newer release, report the gap, then STOP and ask for explicit confirmation; never upgrade automatically. Do not use it for a runtime error on an unchanged install (doca-debug). Version detection alone belongs to doca-version, first-time install to doca-setup, any hardware / firmware / reboot step to doca-hardware-safety, and public-docs or sunset routing to doca-public-knowledge-map.

## When your agent uses it

> Changing DOCA versions safely: upgrading or downgrading the host DOCA packages, refreshing the BlueField BFB, bumping the NGC DOCA container tag, or rolling back, with the discipline detect -> report -> ASK -> only then a guided upgrade. Trigger on "is there a newer DOCA", "I want the newest DOCA features, can I just apt upgrade in place", "should I move to the next release", "the upgrade stopped midway and dpkg is in a broken state", "my component is being deprecated, what now", or "roll me back", even without the word upgrade. Detect what is installed, find the newer release, report the gap, then STOP and ask for explicit confirmation; never upgrade automatically. Do not use it for a runtime error on an unchanged install (doca-debug). Version detection alone belongs to doca-version, first-time install to doca-setup, any hardware / firmware / reboot step to doca-hardware-safety, and public-docs or sunset routing to doca-public-knowledge-map.

## What it can access

From a static check of the files on GitHub; nothing was run.

- [Instructions only, no scripts](https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-upgrade)
- [License: Apache-2.0](https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-upgrade)

## Install

### Claude Code

Copy the skill folder to `~/.claude/skills/doca-upgrade` to use it in all your projects:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/NVIDIA/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/doca-upgrade &&
cp -R "$tmp/skills/doca-upgrade" ~/.claude/skills/doca-upgrade &&
rm -rf "$tmp"
```

For one project only, put the folder in `.claude/skills/doca-upgrade` inside it instead.

### Codex

Copy the skill folder to `~/.agents/skills/doca-upgrade` to use it in every repository:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/NVIDIA/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/doca-upgrade &&
cp -R "$tmp/skills/doca-upgrade" ~/.agents/skills/doca-upgrade &&
rm -rf "$tmp"
```

For one repository only, put the folder in `.agents/skills/doca-upgrade` inside it instead.

### Cursor

Copy the skill folder to `~/.cursor/skills/doca-upgrade` to use it in every project:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/NVIDIA/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/doca-upgrade &&
cp -R "$tmp/skills/doca-upgrade" ~/.cursor/skills/doca-upgrade &&
rm -rf "$tmp"
```

For one project only, put the folder in `.cursor/skills/doca-upgrade` inside it instead.

### Gemini CLI

Run in a terminal (add `--scope workspace` to install it for the current workspace only):

```sh
gemini skills install https://github.com/NVIDIA/skills.git --path skills/doca-upgrade
```

Or copy the folder to `~/.gemini/skills/doca-upgrade` yourself.

### VS Code

For GitHub Copilot in VS Code, copy the skill folder to `~/.copilot/skills/doca-upgrade`:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/NVIDIA/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/doca-upgrade &&
cp -R "$tmp/skills/doca-upgrade" ~/.copilot/skills/doca-upgrade &&
rm -rf "$tmp"
```

For one project only, put the folder in `.github/skills/doca-upgrade` inside it instead.

### Other agents

Get the folder:

```sh
git clone --depth 1 https://github.com/NVIDIA/skills.git
```

Then copy `skills/skills/doca-upgrade` into your agent's skills folder as `doca-upgrade`. Agents that support SKILL.md read one folder per skill.

## FAQ

### How do I install Doca upgrade in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/doca-upgrade to use it in all your projects, or to .claude/skills/doca-upgrade in one project.

### Does Doca upgrade run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

### Which AI agents can use Doca upgrade?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

---
Source: https://ai-powered.com/skills/doca-upgrade
