Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-version
Use this skill when the user is doing DOCA version handling — detecting the installed release, validating the four-way match across pkg-config doca-common, applications/VERSION, doca_caps --version, and bfver/mlnx-release on BlueField, reasoning about NGC container tags, looking up whether a capability is on the installed release, or diagnosing build-vs-runtime drift. Trigger even when the user does not explicitly say "DOCA version" or "four-way match" — typical implicit phrasings include "progr
Passed 20 of 21 test cases with the skill, and 4 of 21 without it.
and 21 more in the full report
17 fixed4 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
List the four official commands that compose the system inspection chain for detecting installed DOCA software components across host and DPU target.
| Checked | Without skill | With skill |
|---|---|---|
| mentions pkg-config --modversion doca-common | Missed | Passed |
| mentions cat /opt/mellanox/doca/applications/VERSION | Missed | Passed |
| mentions doca_caps --version | Missed | Passed |
| mentions bfver | Missed | Passed |
The instructions your model reads when the skill loads.
Where to start: This skill is the bundle's single source of
truth for DOCA version handling. Open
TASKS.md if the user wants to do something with the
version (detect / validate / diagnose mismatch); open
CAPABILITIES.md when the question is what does
version handling cover (the four-way match, the detection chain,
NGC semantics, the per-library overlay pattern). Every other skill
in the bundle that touches version routes here — they MUST NOT
redefine the rules.
The CLASSES of version-handling questions this skill is built to answer, each with one worked example. The agent should treat the class as the load-bearing piece — the worked example is a single instance.
TASKS.md ## configure +
CAPABILITIES.md ## Capabilities and modes
source-of-truth table.pkg-config --modversion
says 3.3.0; doca_caps --version says 3.2.0". Answered by the
four-way match rule in
CAPABILITIES.md ## Version compatibility
TASKS.md ## debug.TASKS.md ## test (which uses the
version-matrix.json schema defined in
doca-structured-tools-contract
with fallback to per-library docs via
doca-public-knowledge-map).test cases passed, vs 4 / 21 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.