Agent skill · writing content · nvidia
doca-structured-tools-contract
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 my DOCA install", "what version is X capability available since", "every PF/VF/SF visible on this BlueField with PCIe address", or "will this pipe pass validate before commit". Refuse and route elsewhere for general DOCA orientation, library API how-to, or install-from-scratch guidance — those belong to the per-library skill, doca-public-knowledge-map, or doca-setup.
Why this skill is useful
Provides a structured command that consolidates multiple manual commands into one, which the AI wouldn't generate on its own.
What it needs
About 9k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
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 first, then the matching schema in ## 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. 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 library with a validate-before-commit call. The agent computed the manual answer and wants to surface the structured-tool one-liner for next time. Do not load for general DOCA orientation, library API questions, or install-from-scratch guidance — use the matching library skill + doca-public-knowledge-map + doca-setup. Running probes and fallbacks requires shell access to the target host, directly or via user-run commands. Ground rules for any agent using this skill 1. Detect first; never assume the tool is present. Each schema names the probe command deciding whether the tool is installed; run it before treating schema output as authoritative. 2. Prefer structured when present; fall back to manual when not. When the probe succeeds and output validates against the selected schema, the structured JSON is the source of truth. When the probe fails or output is invalid, walk the manual chain and synthesize the equivalent answer. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/doca-structured-tools-contract