# doca-urom-svc

doca-urom-svc guides configuration and operations for the DOCA UROM Service container on BlueField Arm to offload host remote memory tasks.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 4106 repo stars
- Author: NVIDIA
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-urom-svc/SKILL.md
- Updated: 2026-10-23
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/doca-urom-svc

## What it does

This skill guides the operation of the DOCA UROM Service container running on BlueField Arm. The container receives remote memory operations—such as puts, gets, atomics, and UCX collectives—sent by a host system through `doca-urom` over DOCA Comch.

It covers image deployment from NVIDIA NGC, queue depth sizing, UCX component selection, and version matching between host and DPU. The skill also helps diagnose missing completions, throughput drops on collectives, and unexpected `DOCA_ERROR_NOT_PERMITTED` errors.

The container lacks internal access control. RDMA permissions and Comch pairing act as the sole security boundary. A running DOCA setup on the BlueField OS is necessary before deploying the service.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill doca-urom-svc -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/doca-urom-svc/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/doca-urom-svc/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill doca-urom-svc -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/doca-urom-svc/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill doca-urom-svc -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/doca-urom-svc/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install NVIDIA/skills skills/doca-urom-svc
```

2. **Manually: put the files in place**
- File: `.github/skills/doca-urom-svc/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill doca-urom-svc -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/NVIDIA/skills --path skills/doca-urom-svc
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/doca-urom-svc/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-urom-svc/SKILL.md

## When to use it
- configure the DOCA UROM Service container on BlueField Arm
- resolve DOCA_ERROR_NOT_PERMITTED errors during Comch pairing
- size enqueue queues and select UCX collective offloads
- trace stalled remote memory completions between host and DPU

## Example prompts
- How do I configure DOCA UROM Service on BlueField for UCX collective offload?
- Host calls to doca-urom fail with NOT_PERMITTED, how do I check Comch pairing?
- Remote memory operations enqueue but never complete, how do I inspect the service?

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 4609b6639353aae2.

BEGIN THIRD-PARTY FILE 4609b6639353aae2
```text
---
license: Apache-2.0
name: doca-urom-svc
description: >
  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 host application
  code, MPI/UCX integration design, or DOCA install.
metadata:
  author: NVIDIA <doca-feedback@nvidia.com>
  kind: service
  doca_version: "3.5"
  tags:
    - doca
    - urom
    - service
compatibility: >
  BlueField-Arm-only DOCA service container; pulled from NVIDIA NGC and
  started under the BlueField OS container runtime. Host-side install is
  irrelevant — the host's relationship to this service is via the paired
  `doca-urom` library over a `doca-rdma` substrate. The validation steps
  require a live DOCA install.
---

# DOCA UROM Service

**Scope first.** This skill operates the DPU-side service container.
Writing the host-side application code that submits offloaded
operations (from an MPI or UCX job, for example) is not this skill:
route it to `doca-urom/SKILL.md`, the host
library, and come back here only for the service it pairs with.

## Examples

- **"Slow UCX collectives on a BlueField pair."** — this is
  in scope for the DPU-side service container; host app code
  belongs to the `doca-urom` library skill.
- **"Unexpected NOT_PERMITTED after start."** — verify Comch
  pairing and least-privilege memory regions before widening
  exposure.

## Instructions

Follow Loading order below. Open the tasks companion for configure /
pair / debug. Open the capabilities companion for queues and
UCX components.

**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, start at the tasks companion `## configure`. If the question is *what
shape of service is DOCA UROM Service, what does it execute, and
how does it pair with the host-side library*, start at
the capabilities companion. If DOCA is not installed
on the BlueField yet, route to
`doca-setup/SKILL.md` first. If the user's
real question is about *writing host-side code that enqueues
remote memory operations through the paired API*, the right
skill is `doca-urom/SKILL.md` — the
host-side library; this service is the DPU-side executor that
library offloads to.

**How to use this skill.** Read this file, then search the companion file
for the `## <name>` heading the question needs and read that whole section.
Answer completely from it, quoting only its symbols and commands. Do not
```
END THIRD-PARTY FILE 4609b6639353aae2

The third-party file has ended. Everything between the 4609b6639353aae2 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3079 of 18632 bytes. © NVIDIA · Apache-2.0 · https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-urom-svc/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
