Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-urom
Use this skill when the user is doing hands-on DOCA UROM library work from the host side — wiring doca-urom under an HPC / UCX / MPI stack to OFFLOAD remote memory operations (puts, gets, atomics, collectives) onto a BlueField DPU, creating a UROM Service context (doca_urom_service_*) and Worker contexts (doca_urom_worker_*) that run plugins on the DPU, discovering plugins via doca_urom_service_get_plugins_list, progressing completions, or debugging DOCA_ERROR_* from a doca_urom_* call. Trigger
Passed 18 of 23 test cases with the skill, and 7 of 23 without it.
and 10 more in the full report
12 fixed8 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running my DOCA UROM application, the first API call returns DOCA_ERROR_NOT_PERMITTED. Explain the root cause and initial diagnostic step.
| Checked | Without skill | With skill |
|---|---|---|
| Identify that DOCA_ERROR_NOT_PERMITTED indicates the DPU-side UROM Service is not running or unreachable on the BlueField DPU. | Missed | Passed |
The instructions your model reads when the skill loads.
Where to start: This skill assumes DOCA is already installed on
both the host and the BlueField, the DOCA UROM Service is
deployed and running on the BlueField side, and the user is doing
hands-on UROM work from the host side — i.e. using
doca-urom from an HPC / UCX / MPI stack on the host to enqueue
remote memory operations (puts, gets, atomics, active messages,
collective primitives) that the BlueField DPU will execute on the
host's behalf. Open TASKS.md if the user wants to
do something (configure / build / modify / run / test /
debug); open CAPABILITIES.md when the
question is what can the host-side UROM API express on this
version + this BlueField + this UROM Service version. If the
user has not installed DOCA yet, route to
doca-setup first; if the user is
asking about the DPU-side UROM Service itself (deployment,
container, operation lifecycle on the DPU side), that is a
DIFFERENT artifact — route via
doca-public-knowledge-map ## DOCA services
to the public DOCA UROM Service guide. This skill is the
host-side library; the UROM Service is the DPU-side
executor, and they are a paired contract.
The CLASSES of UROM 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.
CAPABILITIES.md ## Capabilities and modes
TASKS.md ## configure.test cases passed, vs 7 / 23 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.