doca-hardware-safety SKILL.md skillA
doca-hardware-safety 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-hardware-safety@git:20261022.a4cf47ePins git:20261022.a4cf47e 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-hardware-safety/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261022.a4cf47e, committed Oct 22, 2026
- First version recorded
- Jul 17, 2026
- Size
- 17,376 bytes
- Repository stars
- 3,871
- License
- Apache-2.0
Use this skill whenever the agent is about to recommend or apply a change that touches DPU / NIC hardware state on a live system — mlxconfig firmware-parameter write, NIC firmware burn, BFB reflash, NIC ↔ DPU mode flip, SR-IOV or device-emulation slot enable, kernel boot-parameter change (IOMMU, hugepages, VFIO), PCIe rebind / rescan / link-state flip, BlueField cold reboot, or remediation of a BlueField thermal shutdown. Wrap the change in pre-flight inventory, OOB reachability, a maintenance…
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 hardware safety ## Examples - **"Enable SR-IOV and reboot."** — this is in scope. Inventory first, require out-of-band reachability, a maintenance window, replica rehearsal, then apply. - **"Flip BlueField mode over SSH."** — refuse if the host has no out-of-band path. A link-breaking change without BMC / RShim / console is a hard stop. ## Quick answers (answer from this file) - **Thermal shutdown or hardware safety limits.** Treat it as a hardware event: capture read-only evidence first (BMC/Redfish chassis thermal sensors and event log, the out-of-band console, `dmesg | grep -i mlx5`, and `mget_temp -d <mst device>` from MFT). Never disable or raise thermal protection; airflow and cooling are facility fixes. Any remediation that is a firmware update, an `mlxconfig` write or a cold power cycle goes through the contract below; with no root cause or no rollback, refuse and escalate to NVIDIA support. - **Read-only inventory or version questions** do not need this skill: name `doca-version` (four-source chain) or `doca-caps` (`doca_caps --list-devs`) and answer there. - Name sibling skills (`doca-version`, `doca-setup`, …
Read the whole file at its exact version.
How to install
mdr add nvidia/skills/doca-hardware-safety@sha256:90711945a24efad8The line at the top of this page pins the label git:20261022.a4cf47e, 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_lvux4zivbkablbct)
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 22, 2026, about one every 32 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261022.a4cf47e latest | 2026-10-22 | a4cf47e | 17,376 B | A | view · diff |
| git:20261014.bbb601a | 2026-10-14 | bbb601a | 17,884 B | A | view · diff |
| git:20260727.a5736e4 | 2026-07-27 | a5736e4 | 17,022 B | A | view · diff |
| git:20260717.f64fa0e | 2026-07-17 | f64fa0e | 16,438 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 (17376 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_lvux4zivbkablbct GET https://markdownregistry.com/api/v1/resolve?ref=nvidia/skills/doca-hardware-safety GET https://markdownregistry.com/api/v1/blob/90711945a24efad866c47db5332f4e1804db78a0af2fb73f01e14739c9f26b4b
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.