Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-bf4-deployment
WARNING: guides potentially IRREVERSIBLE BlueField-4 hardware operations (PLDM firmware burns, ISO reflashes, power cycles, BMC factory resets) that can brick firmware, corrupt boot media, or cause outages — a maintenance window and rollback plan are required, and every mutating step is governed by doca-hardware-safety, loaded alongside.
Passed 21 of 25 test cases with the skill, and 11 of 25 without it.
and 10 more in the full report
10 fixed11 passed either way4 still failing0 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.
After completing the bundle installation on the BlueField-4 DPU, what command should be executed on the Grace OS shell to inspect the exact installed release build number?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies inspecting /etc/mlnx-release to verify the installed OS build version. | Missed | Passed |
The instructions your model reads when the skill loads.
⚠️ WARNING — irreversible hardware operations. This skill guides operators through potentially destructive, irreversible BlueField-4 hardware operations: PLDM firmware burns, ISO reflashes, power cycles, and BMC factory resets. These can brick firmware, corrupt boot media, or cause production outages. Do not proceed without a maintenance window and a tested rollback plan. Every mutating step is governed by
doca-hardware-safety, which MUST be loaded alongside this skill before any destructive action.Before executing any mutating step — PLDM firmware burn, ISO reflash, power cycle, or BMC factory reset — the agent MUST show the exact command and its blast radius (which device, what becomes unavailable, whether it is reversible) and obtain the user's explicit confirmation for that specific action. Never chain destructive steps or run them speculatively as a side effect of another task.
Where to start: This skill is the bundle's deliberate in-bundle
home for day-1 platform bring-up of a BlueField-4 DPU via the
BMC — getting a powered-but-bare BF4 to "Grace OS installed,
firmware at the target level, ready to deploy a workload." It is the
upstream of the two application-deployment skills
(doca-container-deployment
and
doca-bare-metal-deployment):
those skills assume a working BlueField; this skill is how the
BlueField-4 GETS to working. If the user has a fresh BF4 and wants to
install the OS or update firmware, open TASKS.md and
start at ## configure. If the question is
what bring-up methods even exist and what is the contract for each,
start at CAPABILITIES.md.
Scope note — BF4 day-1 is in scope by directive. The bundle's
AGENTS.md ## Non-goalsitem 7 lists the BlueField BSP / BFB / RShim / TMFIFO layer and the BlueField BMC software as externally-productized. BlueField-4 day-1 bring-up via the BMC is carved into scope for this skill by directive because day-1 has no other home in the bundle. The
test cases passed, vs 11 / 25 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.