doca-structured-tools-contract SKILL.md skillA
doca-structured-tools-contract 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-structured-tools-contract@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-structured-tools-contract/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.3d06e7e, committed Oct 28, 2026
- First version recorded
- Jul 17, 2026
- Size
- 15,667 bytes
- Repository stars
- 3,871
- License
- Apache-2.0
Not for writing library code (name that library skill). Use this skill whenever another DOCA skill says "prefer the structured tool per doca-structured-tools-contract", or when the user wants a one-shot answer consolidating what multiple manual commands would produce — DOCA env / version / devices / capabilities / validate / host vs DPU state. Trigger even without the phrases "structured tool" or "doca-env --json" — typical phrasings include "is there one command that tells me everything about…
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 structured-tools contract **Where to start:** Reach for this skill whenever a workflow says *“prefer the structured tool per `doca-structured-tools-contract`”*. Read [`## The agent behavior contract`](#the-agent-behavior-contract) first, then the matching schema in [`## Schemas`](#schemas). If the host has the structured tool, prefer its output; if not, fall back to the manual chain in the same section and **always report which path was taken**. **Scope boundary.** Writing library code is not a structured-tools question: name the library skill and stop. Checking a spec before commit IS in scope: apply the validate-before-commit schema. ## Example questions this skill answers well See [`references/examples.md`](references/examples.md). ## When to load this skill Load this skill whenever another skill's workflow says *prefer the structured tool*, OR the user wants a one-shot answer consolidating multiple manual commands. Concretely: - A per-artifact skill's Command appendix references this skill. - The user asks "is there one command that tells me X about my DOCA install". - The user asks "how do I know X is valid before I commit" for a …
Read the whole file at its exact version.
How to install
mdr add nvidia/skills/doca-structured-tools-contract@sha256:3f72c6ace8c070e6The 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_gjq2bzn4jlgkf5vj)
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,667 B | A | view · diff |
| git:20261022.a4cf47e | 2026-10-22 | a4cf47e | 15,791 B | A | view · diff |
| git:20261014.bbb601a | 2026-10-14 | bbb601a | 19,761 B | A | view · diff |
| git:20260727.a5736e4 | 2026-07-27 | a5736e4 | 19,870 B | A | view · diff |
| git:20260717.f64fa0e | 2026-07-17 | f64fa0e | 19,243 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 (15667 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_gjq2bzn4jlgkf5vj GET https://markdownregistry.com/api/v1/resolve?ref=nvidia/skills/doca-structured-tools-contract GET https://markdownregistry.com/api/v1/blob/3f72c6ace8c070e6ee0c9db45877859def9ae769e90066f3c16e392738e539ce
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.