doca-bf4-deployment SKILL.md skillA
doca-bf4-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-bf4-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-bf4-deployment/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261028.3d06e7e, committed Oct 28, 2026
- First version recorded
- Jul 17, 2026
- Size
- 12,265 bytes
- Repository stars
- 3,871
- License
- Apache-2.0
WARNING: guides IRREVERSIBLE BlueField-4 hardware operations (PLDM firmware burns, ISO reflashes, power cycles, BMC factory resets); every mutating step is governed by doca-hardware-safety (window, rollback). BlueField-4 only: BlueField-3 bring-up is doca-bf3-deployment. Use this skill for BlueField-4 (BF4) day-1 platform bring-up from the BMC: installing the BlueField/DOCA bundle ISO onto the DPU (Grace, the Arm complex) over UEFI HTTP Boot, PXE, or Redfish Virtual Media; the PLDM…
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-4 (BF4) deployment ## Examples - **"I have a BlueField-4 and a BMC — how do I bring Grace up?"** — BMC-driven day-1, not the BF3 RShim/BFB path. Do not invent credentials or skip media detach. - **"PLDM update finished but the NIC firmware did not move."** — treat it as a firmware-Task / activation failure, not a second burn by default. **BlueField-3 or any other generation is not this skill.** Name `doca-bf3-deployment` and stop; do not read further or run commands. ## Preparing a BlueField-4 host (answer from here) 1. **Platform:** confirm it is BlueField-4 and that the BMC is reachable out of band; compare the Redfish firmware inventory with the release notes' targets. 2. **Version alignment:** run the `doca-version` four-source chain on the host. Fixing any mismatch changes hardware state and follows `doca-hardware-safety`. 3. **Safest first smoke test:** read-only `doca_caps --list-devs`, then one shipped sample per `doca-bare-metal-deployment`. No firmware, mode or reset change before that is green. 4. **Say it in the answer:** every mutating step (PLDM firmware burn, ISO reflash, power cycle, BMC reset) is routed through …
Read the whole file at its exact version.
How to install
mdr add nvidia/skills/doca-bf4-deployment@sha256:4ee49509b73d73c6The 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_5w6iuv6kv4bdt2cx)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 17, 2026 and Oct 28, 2026, about one every 34 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.3d06e7e latest | 2026-10-28 | 3d06e7e | 12,265 B | A | view · diff |
| git:20261022.a4cf47e | 2026-10-22 | a4cf47e | 12,282 B | A | view · diff |
| git:20261014.bbb601a | 2026-10-14 | bbb601a | 12,795 B | A | view · diff |
| git:20260717.f64fa0e | 2026-07-17 | f64fa0e | 12,247 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 (12265 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_5w6iuv6kv4bdt2cx GET https://markdownregistry.com/api/v1/resolve?ref=nvidia/skills/doca-bf4-deployment GET https://markdownregistry.com/api/v1/blob/4ee49509b73d73c64fff034f348e1d137473ebf28024f335194b81dcf0ca460c
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.