doca-bf3-deployment SKILL.md skillA
doca-bf3-deployment 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-bf3-deployment@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-bf3-deployment/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.3d06e7e, committed Oct 28, 2026
- First version recorded
- Jul 17, 2026
- Size
- 10,645 bytes
- Repository stars
- 3,871
- License
- Apache-2.0
Use this skill for BlueField-3 (BF3) day-1 platform bring-up via the classic RShim/BFB path: pushing a BlueField bundle (BFB) to the DPU over RShim with bfb-install from the host, the host-to-DPU TMFIFO management channel (tmfifo_net0, the 192.168.100.x convention), RShim daemon state and console-over-rshim, DPU mode selection (DPU/embedded-function vs separated-host/NIC mode) via mlxconfig, post-BFB recovery, a six-state BlueField-state classifier, and verifying the install…
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 BlueField-3 (BF3) deployment ## Examples - **"I have a BlueField-3 and a BFB — how do I push it?"** — RShim plus bfb-install from the host. Exit 0 is not success until the DPU is ready. - **"bfb-install exited 0 but the DPU never came back."** — start at the six-state classifier, not a second burn. ## Instructions Follow Loading order below. Open the tasks companion for BFB push and recover. Open the capabilities companion for the RShim/BFB contract and safety overlay. Do not open every companion file. **Where to start:** This skill is the bundle's home for **BlueField-3 day-1 platform bring-up** — taking a BF3 from "powered card in the slot" (or a card that just came back broken from a BFB push) to "Arm OS healthy, TMFIFO up, host PFs bound, four-way version match closed, ready to run a workload". It owns the **classic RShim/BFB path** that BF3 uses today; the newer BMC-Redfish provisioning path is the sibling skill `doca-bf4-deployment/SKILL.md` (the BF4 equivalent). If the user has a BF3 and needs to push a BFB, recover a DPU that did not come back, or verify the install, open the tasks companion and start at `## configure`. If the question is *what shape …
Read the whole file at its exact version.
How to install
mdr add nvidia/skills/doca-bf3-deployment@sha256:d599561bedd635b2The 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_4cmjbuqu7hafbprj)
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 | 10,645 B | A | view · diff |
| git:20261022.a4cf47e | 2026-10-22 | a4cf47e | 10,649 B | A | view · diff |
| git:20261014.bbb601a | 2026-10-14 | bbb601a | 11,216 B | A | view · diff |
| git:20260727.a5736e4 | 2026-07-27 | a5736e4 | 10,972 B | A | view · diff |
| git:20260717.f64fa0e | 2026-07-17 | f64fa0e | 10,962 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 (10645 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_4cmjbuqu7hafbprj GET https://markdownregistry.com/api/v1/resolve?ref=nvidia/skills/doca-bf3-deployment GET https://markdownregistry.com/api/v1/blob/d599561bedd635b26627118a289f5bbac640bfc2a659db0be4616061d28f88b4
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.