Agent skill · NVIDIA
doca-upgrade
Use this skill when the user is contemplating a DOCA upgrade or downgrade — moving a host to a newer DOCA release, refreshing the BlueField BFB, bumping the NGC DOCA container tag, or rolling back. The discipline is detect → report → ASK → only-then guided upgrade: detect what is installed, discover what newer release exists, report the gap, then STOP and ask for explicit confirmation — never upgrade automatically. Trigger even without the word "upgrade": "is there a newer DOCA", "should I move to the next release", "I want the latest features", "my component is being deprecated, what now", or "roll me back". Route elsewhere for version detection (doca-version), first-time install (doca-setup), any hardware/firmware/reboot step (doca-hardware-safety), and public-docs / sunset routing (doca-public-knowledge-map).
What it needs
About 7k tokens when loaded.
What this skill does
DOCA upgrade Where to start: This skill is the bundle's single source of truth for the discipline that wraps a DOCA upgrade or downgrade. Open TASKS.md when the user wants to do something with an upgrade (detect the gap, ask for confirmation, walk the guided upgrade, verify it, or diagnose a failed one); open CAPABILITIES.md when the question is what does an upgrade even cover (the host apt-upgrade vs BFB reflash vs container-tag bump vs downgrade/rollback modes, the never-auto rule, the confirmation gate, the sunset-awareness concern, the error taxonomy, and the upgrade-specific safety overlay). For a planned move, the single most important rule this skill exists to enforce is detect → report → ASK → only-then guided upgrade. Never upgrade automatically. The skill detects the installed DOCA env and what newer release is available, reports the gap clearly, then STOPS and asks the user for explicit confirmation. Only on an explicit "yes" does it walk a guided upgrade. A failed or partial move instead enters the recovery ladder without presenting a new target move. In both paths every hardware / firmware / reboot step is delegated to doca-hardware-safety, never redefined here. Version detection itself is owned by doca-version; this skill routes there and does not restate the detection chain. Example questions this skill answers well The CLASSES of upgrade questions this skill is built to answer, each with one worked example. The agent should treat the class as the load-bearing piece — the worked example is a single instance. "Is there a newer DOCA than what I have, and how far behind am I?" — worked example: "pkg-config --modversion doca-common says 3.1.0; what's current and what does moving cost me?". Answered by the detect-and-report-the-gap workflow in TASKS.md ## configure, which routes the detection to doca-version and the what is current lookup to doca-public-knowledge-map. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/doca-upgrade