What problem does it solve?
Upgrading or downgrading NVIDIA DOCA across host packages, BlueField BFB images, and NGC container tags is risky: partial upgrades, apt-source drift, and host/BFB version skew can leave systems in a broken state. This Skill enforces a detect → report → ASK → only-then guided upgrade discipline so no upgrade command ever runs without explicit user confirmation.
Core Features & Use Cases
- Gap detection and reporting: Detects the installed DOCA release (via doca-version), discovers the current target release from public release notes, and reports the installed → target gap before any action.
- Confirmation-gated guided upgrades: Walks host apt upgrades, BFB reflashes, container tag bumps, and rollbacks only after explicit confirmation, with rollback-first and maintenance-window gates.
- Failed-upgrade recovery: Diagnoses partial upgrades, aborted dpkg transactions, apt-source drift, and host/BFB skew through a documented recovery ladder.
- Use Case: A user on DOCA 3.1.0 asks whether a newer release exists and how to move safely. The Skill detects the installed version, reports the gap and cost, then stops and waits for explicit confirmation before any upgrade step.
Quick Start
Ask your agent: "I'm on DOCA 3.1.0 — is there a newer release, and how do I move to it safely?"
The agent will load this Skill, detect the installed version, report the gap, and wait for your confirmation before proposing any upgrade command.