# Doca caps

> Doca caps is an open-source agent skill. Use this skill when the user wants to invoke the read-only doca_caps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe. 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-caps
- **Repository:** https://github.com/nvidia/skills
- **GitHub stars:** 4,037
- **License:** Apache-2.0
- **Skill name:** doca-caps
- **Collection:** https://github.com/NVIDIA/skills
- **Listing updated:** 2026-11-17

## About

Use this skill when the user wants to invoke the read-only doca_caps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking which DOCA libraries are available on the current OS, checking per-device per-library capabilities, scoping output to a specific PCIe address, or capturing a side-effect-free capability snapshot for debug or install smoke-test. Trigger even when the user does not explicitly mention "doca_caps" or "capabilities print tool" — typical implicit phrasings include "what does DOCA actually see on this box", "is my BlueField PF visible to DOCA", "is Flow available on my RHEL host", "enumerate VF representors for pf0", "doca_caps: command not found", or "empty output for RDMA, is the tool broken". Refuse and route elsewhere for DOCA installation (doca-setup owns it; never walk the steps), library-internal capability matrices (Flow pipe creation, RDMA verbs features), streaming telemetry / DTS, or modifying the shipped binary.

## When your agent uses it

> Use this skill when the user wants to invoke the read-only doca_caps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking which DOCA libraries are available on the current OS, checking per-device per-library capabilities, scoping output to a specific PCIe address, or capturing a side-effect-free capability snapshot for debug or install smoke-test. Trigger even when the user does not explicitly mention "doca_caps" or "capabilities print tool" — typical implicit phrasings include "what does DOCA actually see on this box", "is my BlueField PF visible to DOCA", "is Flow available on my RHEL host", "enumerate VF representors for pf0", "doca_caps: command not found", or "empty output for RDMA, is the tool broken". Refuse and route elsewhere for DOCA installation (doca-setup owns it; never walk the steps), library-internal capability matrices (Flow pipe creation, RDMA verbs features), streaming telemetry / DTS, or modifying the shipped binary.

## 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-caps)
- [License: Apache-2.0](https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-caps)

## Install

### Claude Code

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

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

### Codex

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

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

### Cursor

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

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

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

### VS Code

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

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

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

### Other agents

Get the folder:

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

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

## FAQ

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

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

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

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