doca-urom-svc
Operate the DOCA UROM Service container on BlueField Arm for remote memory operations (puts, gets, atomics, collectives) enqueued by a paired host using `doca-urom`: pull the NGC image, choose the UCX component, size queues, configure Comch pairing, and align host and service versions. SECURITY: the service has no standalone access control; Comch pairing and RDMA permissions are the boundary. Pair only intended hosts, expose least-privilege memory regions, and verify both views before start. Trigger for slow UCX collectives, unexpected NOT_PERMITTED, or missing completions. Do not use for ho
npx skills add NVIDIA/skills --skill doca-urom-svc --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Operates the DOCA UROM Service container on BlueField Arm to execute remote memory operations (puts, gets, atomics, collectives) enqueued by a paired host using the doca-urom library. It pulls an NGC image, selects the UCX component, sizes queues, configures Comch pairing, and aligns host and service versions. It enforces security boundaries by relying on Comch pairing and RDMA permissions, and instructs to pair only intended hosts, expose least-privilege memory regions, and verify both views before start. It triggers for slow UCX collectives, unexpected NOT_PERMITTED, or missing completions. It does not apply to host application code, MPI/UCX integration design, or DOCA install.
How it works
The skill describes operating steps for deploying and configuring the service container: pull the image from NVIDIA NGC, choose UCX components and collectives to expose, determine enqueue queue depths, set up Comch pairing with the host library, and ensure host/service version compatibility. It emphasizes pre-start verification of Comch and RDMA permissions, and ongoing monitoring of service logs and RDMA counters to confirm correct operation. It defines error taxonomy around NOT_PERMITTED and completions, and guides debugging by separating service queue issues from substrate transport problems, then evaluating offload performance against host baseline as part of safety policy.
When to use it
Load this skill for hands-on DOCA UROM Service deployment work on BlueField where DOCA is already installed. Use when deciding if DOCA UROM Service is appropriate, deploying the service container, choosing configuration axes, pairing host and service, verifying the paired contract, and validating logs and RDMA counters before scaling workloads. It is not intended for general DOCA orientation, DOCA installation, host-side library API questions, or non-UROM HPC topics.
What it can touch
The skill references interacting with the DOCA UROM service container, the host doca-urom library, the doca-rdma transport substrate, and the published configuration surface (flags/env like SERVICE_ARGS, UROM_PLUGIN_PATH, and mounting plugins/). It also mentions observing the service logs and RDMA counters.
Caveats
License: Apache-2.0. It requires BlueField-Arm-only DOCA service container pulled from NVIDIA NGC and started under the BlueField OS container runtime; host-side install is irrelevant. There is no service-side host-endpoint authorization list; access is governed by Comch pairing and underlying RDMA permissions. The skill explicitly warns not to load for host-side library APIs, or pre-baked production bundles, and cautions about version pairing between host library and service.
# DOCA UROM Service **Where to start:** This skill is for *operating the DOCA UROM Service container* on the BlueField Arm side. It is *not* for *linking against* a library, and it is *not* the host-side enqueue surface. If the user wants to *deploy* or *run* the service container, open [`TASKS.md`](TASKS.md) and start at [`## configure`](TASKS.md#configure). If the question is *what shape of serv
What does the doca-urom-svc skill do?
Operate the DOCA UROM Service container on BlueField Arm for remote memory operations (puts, gets, atomics, collectives) enqueued by a paired host using `doca-urom`: pull the NGC image, choose the UCX component, size queues, configure Comch pairing, and align host and service versions. SECURITY: the service has no standalone access control; Comch pairing and RDMA permissions are the boundary. Pair only intended hosts, expose least-privilege memory regions, and verify both views before start. Trigger for slow UCX collectives, unexpected NOT_PERMITTED, or missing completions. Do not use for ho
How do I install it?
Run `npx skills add NVIDIA/skills --skill doca-urom-svc --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From NVIDIA/skills, a repository with 2,789 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
