# Doca devemu

> Doca devemu is an open-source agent skill. Use this skill when the user is doing hands-on DOCA Device Emulation on a BlueField DPU — exposing a custom emulated PCIe device the host se. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.

- **Kind:** Skill
- **Pricing:** Open source
- **Platforms:** Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
- **Website:** https://github.com/NVIDIA/skills/tree/main/skills/doca-devemu
- **Repository:** https://github.com/nvidia/skills
- **GitHub stars:** 4,037
- **License:** Apache-2.0
- **Skill name:** doca-devemu
- **Collection:** https://github.com/NVIDIA/skills
- **Listing updated:** 2026-11-17

## About

Use this skill when the user is doing hands-on DOCA Device Emulation on a BlueField DPU — exposing a custom emulated PCIe device the host sees as a real peripheral while DPU-side code runs the backend, picking the sub-library (PCI Generic, virtio-net, virtio-fs), wiring the per-sub-library Core context plus doorbell / DMA primitives, querying `doca_devemu_*_cap_*`, or debugging DOCA_ERROR_* from a `doca_devemu_*` call. Trigger even when the user does not say "devemu" — typical implicit phrasings include "expose a custom PCIe device from BlueField to the host", "host should see a virtio NIC backed by my DPU code", "lspci does not show my emulated device", "device enumerated but no driver binds", "DPU sees nothing when host kicks the queue", or "virtio feature negotiation failed at bind". Refuse and route elsewhere for the packaged DOCA SNAP / Virtio-net Services, host-side virtio kernel drivers, backend body design, or standard BlueField NIC behavior — those belong to other skills.

## When your agent uses it

> Use this skill when the user is doing hands-on DOCA Device Emulation on a BlueField DPU — exposing a custom emulated PCIe device the host sees as a real peripheral while DPU-side code runs the backend, picking the sub-library (PCI Generic, virtio-net, virtio-fs), wiring the per-sub-library Core context plus doorbell / DMA primitives, querying `doca_devemu_*_cap_*`, or debugging DOCA_ERROR_* from a `doca_devemu_*` call. Trigger even when the user does not say "devemu" — typical implicit phrasings include "expose a custom PCIe device from BlueField to the host", "host should see a virtio NIC backed by my DPU code", "lspci does not show my emulated device", "device enumerated but no driver binds", "DPU sees nothing when host kicks the queue", or "virtio feature negotiation failed at bind". Refuse and route elsewhere for the packaged DOCA SNAP / Virtio-net Services, host-side virtio kernel drivers, backend body design, or standard BlueField NIC behavior — those belong to other skills.

## What it can access

From a static check of the files on GitHub; nothing was run.

- [Instructions only, no scripts](https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-devemu)
- [License: Apache-2.0](https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-devemu)

## Install

### Claude Code

Copy the skill folder to `~/.claude/skills/doca-devemu` to use it in all your projects:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/NVIDIA/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/doca-devemu &&
cp -R "$tmp/skills/doca-devemu" ~/.claude/skills/doca-devemu &&
rm -rf "$tmp"
```

For one project only, put the folder in `.claude/skills/doca-devemu` inside it instead.

### Codex

Copy the skill folder to `~/.agents/skills/doca-devemu` to use it in every repository:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/NVIDIA/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/doca-devemu &&
cp -R "$tmp/skills/doca-devemu" ~/.agents/skills/doca-devemu &&
rm -rf "$tmp"
```

For one repository only, put the folder in `.agents/skills/doca-devemu` inside it instead.

### Cursor

Copy the skill folder to `~/.cursor/skills/doca-devemu` to use it in every project:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/NVIDIA/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/doca-devemu &&
cp -R "$tmp/skills/doca-devemu" ~/.cursor/skills/doca-devemu &&
rm -rf "$tmp"
```

For one project only, put the folder in `.cursor/skills/doca-devemu` inside it instead.

### Gemini CLI

Run in a terminal (add `--scope workspace` to install it for the current workspace only):

```sh
gemini skills install https://github.com/NVIDIA/skills.git --path skills/doca-devemu
```

Or copy the folder to `~/.gemini/skills/doca-devemu` yourself.

### VS Code

For GitHub Copilot in VS Code, copy the skill folder to `~/.copilot/skills/doca-devemu`:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/NVIDIA/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/doca-devemu &&
cp -R "$tmp/skills/doca-devemu" ~/.copilot/skills/doca-devemu &&
rm -rf "$tmp"
```

For one project only, put the folder in `.github/skills/doca-devemu` inside it instead.

### Other agents

Get the folder:

```sh
git clone --depth 1 https://github.com/NVIDIA/skills.git
```

Then copy `skills/skills/doca-devemu` into your agent's skills folder as `doca-devemu`. Agents that support SKILL.md read one folder per skill.

## FAQ

### How do I install Doca devemu in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/doca-devemu to use it in all your projects, or to .claude/skills/doca-devemu in one project.

### Does Doca devemu run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

### Which AI agents can use Doca devemu?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

---
Source: https://ai-powered.com/skills/doca-devemu
