Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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
Passed 13 of 22 test cases with the skill, and 4 of 22 without it.
and 11 more in the full report
10 fixed3 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
When evaluating whether to upgrade from DOCA 2.0 to 2.5, where should the assistant pull the list of feature changes, API breaking changes, and current public release targets?
| Checked | Without skill | With skill |
|---|---|---|
| routes release target and feature delta lookups to doca-public-knowledge-map | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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.
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 totest cases passed, vs 4 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.