# Doca setup

> Doca setup is an open-source agent skill. Use this skill when the user is dealing with the DOCA environment around their workload — verifying an install is healthy, preparing the bui. 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-setup
- **Repository:** https://github.com/nvidia/skills
- **GitHub stars:** 4,037
- **License:** Apache-2.0
- **Skill name:** doca-setup
- **Collection:** https://github.com/NVIDIA/skills
- **Listing updated:** 2026-11-17

## About

Use this skill when the user is dealing with the DOCA environment around their workload — verifying an install is healthy, preparing the build env (pkg-config, headers, LD_LIBRARY_PATH, hugepages, devlink, representors), debugging env-class failures, deciding container-vs-bare-metal deployment shape, or reaching a DOCA install from a host that doesn't have one yet via the NGC DOCA container Stage-1 fallback. Trigger even when the user does not explicitly mention "DOCA setup" — typical implicit phrasings include "just got a BlueField, what now", "code is built, how to run it", "pkg-config can't find doca-flow", "no free 2048 kB hugepages", "representor X not found", "on a Mac and want to learn DOCA". Refuse and route elsewhere for library API specifics (Flow pipes, RDMA queues), the modify-a-sample first-app workflow or DOCA_ERROR_* program-side debugging, and "where is X documented" knowledge-map questions — those belong to other skills.

## When your agent uses it

> Use this skill when the user is dealing with the DOCA environment around their workload — verifying an install is healthy, preparing the build env (pkg-config, headers, LD_LIBRARY_PATH, hugepages, devlink, representors), debugging env-class failures, deciding container-vs-bare-metal deployment shape, or reaching a DOCA install from a host that doesn't have one yet via the NGC DOCA container Stage-1 fallback. Trigger even when the user does not explicitly mention "DOCA setup" — typical implicit phrasings include "just got a BlueField, what now", "code is built, how to run it", "pkg-config can't find doca-flow", "no free 2048 kB hugepages", "representor X not found", "on a Mac and want to learn DOCA". Refuse and route elsewhere for library API specifics (Flow pipes, RDMA queues), the modify-a-sample first-app workflow or DOCA_ERROR_* program-side debugging, and "where is X documented" knowledge-map questions — 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-setup)
- [License: Apache-2.0](https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-setup)

## Install

### Claude Code

Copy the skill folder to `~/.claude/skills/doca-setup` 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-setup &&
cp -R "$tmp/skills/doca-setup" ~/.claude/skills/doca-setup &&
rm -rf "$tmp"
```

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

### Codex

Copy the skill folder to `~/.agents/skills/doca-setup` 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-setup &&
cp -R "$tmp/skills/doca-setup" ~/.agents/skills/doca-setup &&
rm -rf "$tmp"
```

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

### Cursor

Copy the skill folder to `~/.cursor/skills/doca-setup` 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-setup &&
cp -R "$tmp/skills/doca-setup" ~/.cursor/skills/doca-setup &&
rm -rf "$tmp"
```

For one project only, put the folder in `.cursor/skills/doca-setup` 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-setup
```

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

### VS Code

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

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

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

### Other agents

Get the folder:

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

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

## FAQ

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

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

### Does Doca setup 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 setup?

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-setup
