doca-upgrade SKILL.md skillA
doca-upgrade from nvidia/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nvidia/skills/doca-upgrade@git:20261028.3d06e7ePins git:20261028.3d06e7e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nvidia/skills
- Path
skills/doca-upgrade/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.3d06e7e, committed Oct 28, 2026
- First version recorded
- Jul 17, 2026
- Size
- 15,146 bytes
- Repository stars
- 3,871
- License
- Apache-2.0
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# DOCA upgrade ## Examples - **"Should I move to the next DOCA release?"** — detect what is installed, report the gap, then STOP and ask. Never auto-upgrade. - **"apt upgrade drifted my DOCA packages."** — this is recovery, not a silent repair. Detect, report, ask, then guide. ## Quick answers (answer from this file) - **Not changing versions** (a runtime error on the current, pinned install)? This skill does not apply: name `doca-debug` and stop. These two answers are complete here; open `TASKS.md` only for a guided upgrade after the user confirms. Run only the read-only detection commands yourself. Package commands (`sudo dpkg`, `apt`, `apt-get`) need root and change the system: give them to the user to run and stop; in an agent shell `sudo` waits for a password and the session stalls. - **"Can I just `apt upgrade` to the next DOCA?"** Never upgrade automatically. Detect the installed release with the `doca-version` four-source chain (`pkg-config --modversion doca-common`, `cat /opt/mellanox/doca/applications/VERSION`, `doca_caps --version`, and the BFB version on BlueField), report the gap to the target release, then …
Read the whole file at its exact version.
How to install
mdr add nvidia/skills/doca-upgrade@sha256:2b24d93b856bf596The line at the top of this page pins the label git:20261028.3d06e7e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_nimclv34c3wtgrpp)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 17, 2026 and Oct 28, 2026, about one every 26 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.3d06e7e latest | 2026-10-28 | 3d06e7e | 15,146 B | A | view · diff |
| git:20261022.a4cf47e | 2026-10-22 | a4cf47e | 15,137 B | A | view · diff |
| git:20261014.bbb601a | 2026-10-14 | bbb601a | 15,195 B | A | view · diff |
| git:20260727.a5736e4 | 2026-07-27 | a5736e4 | 13,590 B | A | view · diff |
| git:20260717.f64fa0e | 2026-07-17 | f64fa0e | 12,236 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15146 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nvidia/skills · 3,871 stars · license Apache-2.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nimclv34c3wtgrpp GET https://markdownregistry.com/api/v1/resolve?ref=nvidia/skills/doca-upgrade GET https://markdownregistry.com/api/v1/blob/2b24d93b856bf596faf7febb1e2f6fb7dd6ed7b6eacaaa9963ece2ebc609d29a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.