Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-structured-tools-contract
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 that consolidates info multiple manual commands would produce — DOCA env / version / devices / capabilities / validate / host vs DPU state. Trigger even when the user does not explicitly mention "structured tool" or "doca-env --json" — typical implicit phrasings include "is there one command that tells me everything about my DOCA install", "wha
Passed 14 of 21 test cases with the skill, and 6 of 21 without it.
and 12 more in the full report
9 fixed6 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to probe hardware capability flags for all network devices in a single call. What binary path detection command checks if the capability snapshot helper is available on $PATH?
| Checked | Without skill | With skill |
|---|---|---|
| Uses detection probe command -v doca-capability-snapshot | Missed | Passed |
| Reports fallback prefix when the executable is absent from PATH | Missed | Passed |
The instructions your model reads when the skill loads.
Where to start: Reach for this skill whenever a workflow in
another skill says "prefer the structured tool per
doca-structured-tools-contract". Read
## The agent behavior contract
first; then drill into the matching schema in ## Schemas.
If the host has the structured tool, prefer its output. If it does
not, fall back to the manual command chain in the same schema
section. Always report which path was taken so the user can fix
the gap (or so a future bundle update can detect that the structured
path was never tried).
See references/examples.md for the five
worked routing examples. Keep this loader focused on detection,
fallback behavior, and the authoritative schemas below.
Load this skill whenever another skill's workflow tells the agent to prefer the structured tool, OR whenever the user's question implies they want a single one-shot answer that consolidates information multiple manual commands would otherwise produce.
Concretely:
Do not load this skill for general DOCA orientation, for
test cases passed, vs 6 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.