К основному содержанию
скилл CX Codex

doca-caps — скилл для Claude Code: проверка DOCA

Скилл doca-caps для Claude Code запускает read-only CLI и показывает, какие устройства и библиотеки DOCA видит на хосте. Он также проверяет возможности устройства и помогает сохранить снимок для отладки.

Apache-2.0 147 установок ★ 4 106 обновлён 2026-10-23

Установить в Claude Code · Через Skills CLI (Vercel) Все способы и платформы ↓
npx skills add NVIDIA/skills --skill doca-caps -a claude-code
Открыть на GitHub

Что делает doca-caps

doca-caps вызывает утилиту doca_caps, чтобы перечислить устройства DOCA и их PCIe-адреса, доступные библиотеки и представительства сетевых устройств. Для конкретного устройства можно запросить возможности отдельной библиотеки или сохранить снимок состояния для отладки и проверки установки.

Нужны Linux, DOCA SDK версии 2.6.0 или выше в /opt/mellanox/doca и устройство BlueField DPU либо ConnectX NIC. Скилл работает на хосте или на Arm-стороне BlueField. Он только проверяет установку: установку DOCA и настройку пакетов передаёт другому скиллу.

Какие задачи решает

  • перечислить устройства DOCA и их PCIe-адреса
  • проверить, какие библиотеки DOCA доступны в системе
  • узнать возможности библиотеки для конкретного устройства
  • собрать снимок возможностей для отладки

Примеры запросов агенту

  • Покажи, какие устройства DOCA видит этот хост.
  • Проверь, доступна ли Flow на этом узле.
  • Сохрани снимок устройств и возможностей DOCA для отладки.

Как установить doca-caps

1Через Skills CLI (Vercel)

npx skills add NVIDIA/skills --skill doca-caps -a claude-code

2Вручную: положить файлы

~/.claude/skills/doca-caps/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/doca-caps/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы о doca-caps

Как установить doca-caps в Claude Code?

Запусти npx skills add NVIDIA/skills --skill doca-caps -a claude-code. Файл скилла находится по пути ~/.claude/skills/doca-caps/SKILL.md.

Что делает doca-caps?

Он запускает read-only CLI doca_caps, чтобы перечислить устройства, представительства и доступные библиотеки DOCA, а также проверить возможности устройства.

Что нужно для работы doca-caps?

Нужны Linux, DOCA SDK версии 2.6.0 или выше, установленный в /opt/mellanox/doca, и BlueField DPU либо ConnectX NIC.

Исходный текст

SKILL.md · Apache-2.0
---
license: Apache-2.0
name: doca-caps
description: >
  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.
metadata:
  author: NVIDIA <[email protected]>
  kind: tool
  doca_version: "3.5"
  tags:
    - doca
    - caps
    - tools
compatibility: >
  Requires DOCA SDK ≥ 2.6.0 installed at /opt/mellanox/doca on Linux
  (Ubuntu 22.04/24.04 or RHEL/SLES) with a BlueField DPU or ConnectX
  NIC; runs identically on the host or on the BlueField Arm side.
  Invokes /opt/mellanox/doca/tools/doca_caps and reads `pkg-config
  doca-common` to confirm the install. The validation steps require a
  live DOCA install.
---

# DOCA Capabilities Print Tool (`doca_caps`)

## Examples

- **"What DOCA devices does this host see?"** — this is in
  scope. Stay on `doca_caps`; do not start a library-internal
  capability matrix here.
- **"Is Flow available on my RHEL host?"** — list libraries
  then scope per-device if needed.

## Instructions

Follow Loading order below. Open the tasks companion for run /
test. Open the capabilities companion for what the CLI reports.
Do not open every companion file.

**Where to start:** This is a tool skill for invoking `doca_caps`,
a side-effect-free CLI. Open the tasks companion and start at
`## run` for the documented invocations, or
`## test` when using `doca_caps` as an install
smoke-test. Open the capabilities companion when the
question is *what kinds of capability families `doca_caps` reports*.

> **Boundary: this skill never installs DOCA.** `doca_caps`
> *verifies* an install and never performs one. A request to install
> DOCA — choosing packages, adding repositories, running a package
> manager — is out of scope here, and stays out of scope even though
> this skill's `## test` verb uses the tool as an install smoke-test
> *afterwards*. Hand the whole request to
> `doca-setup/SKILL.md` by name. Naming the owner
> and then listing the steps anyway is the failure mode to avoid: do
> not walk the installation, not even as a summary or a caveat.
>
> This narrows *installation only*. It is not a reason to answer
> narrowly about tooling: when the user's question reaches past
> `doca_caps` — what else can I ask this hardware, how do I measure it,
> how do I inspect a running pipeline — name the sibling tool that owns
> it (`doca_bench`, `doca_flow_tune`, `pcc_counters.sh`,
> `doca_comm_channel_admin`, …) and tie it to the question. Pointing at
> the rest of the catalog is this skill's job, not a boundary breach.

## Example questions this skill answers well

The CLASSES of `doca_caps` questions this skill is built to answer,
each with one worked example. The class is the load-bearing piece;
the worked example is one instance.

- **"What DOCA devices does this host see?"** — worked example: *"is
  my BlueField PF visible to DOCA"*. Answered by the device
  enumeration in
  the capabilities companion
  + the `--list-devs` invocation in
  the tasks companion.
- **"Which DOCA libraries are available on this OS?"** — worked
  example: *"is Flow available on my RHEL host"*. Answered by the
  library-availability surface in
  the capabilities companion
  + the library-listing invocation in
  the tasks companion.
- **"Does this device support library X capability Y?"** — worked
  example: *"does this device support Flow hairpin?"*. Answered by
  the per-device per-library capability matrix in
  the capabilities companion
  + the `--pci-addr`-scoped invocation in
  the tasks companion.
- **"What representors are visible to DOCA?"** — worked example:
  *"enumerate VF representors for pf0"*. Answered by the representor
  enumeration in
  the capabilities companion
  + the `--list-rep-devs` invocation in
  the tasks companion.
- **"I want a snapshot of state to attach to my debug session."** —
  worked example: *"save device + library + capability output to a
  file"*. Answered by the snapshot workflow in
  the tasks companion and consumed by
  `doca-debug/SKILL.md` step 3
  (read-only triple) and
  `doca-programming-guide/SKILL.md`.
- **"`doca_caps` returned nothing for capability Y — what does that
  mean?"** — worked example: *"empty output for RDMA"*. Answered by
  the empty-output interpretation rules in
  the tasks companion +
  the capabilities companion.

## Audience

This skill serves **external operators, developers, and AI agents who
need a side-effect-free way to ask "what does DOCA see on this host?"**
before doing anything that changes state. Concretely:

- An external developer who installed DOCA (or is using the public NGC
  DOCA container per `doca-setup/SKILL.md`)
  and wants to confirm the install can see hardware before writing code.
- A platform operator deploying a DOCA service who wants a documented,
  read-only snapshot of *which DOCA libraries this host actually
  supports* and *which capabilities each DOCA device offers*.
- An AI agent producing a *capability snapshot* artifact during the
  documented setup or programming-guide debug procedures (it's listed
  as the canonical first step in
  `doca-setup/SKILL.md` and
  `doca-programming-guide/SKILL.md`).

It is **not** for users debugging `doca_caps` itself, and **not** a
substitute for the live public Capabilities Print Tool guide.

`doca_caps` is shipped as a **tool** (a single CLI binary), not a
library you link against. The skill uses the same `kind: tool`
three-file shape as the rest of the bundle so the agent's task-verb
contract (`configure / build / modify / run / test / debug`) is uniform
across libraries, services, and tools — even when individual verbs
collapse to a routing stub for a shipped read-only binary.

## When to load this skill

Load this skill when the user is — or the agent needs to — invoke
`doca_caps` on a real host with DOCA installed (or inside the public
NGC DOCA container). Concretely:

- Running `doca_caps --list-devs` to enumerate DOCA devices.
- Running `doca_caps --list-rep-devs` to enumerate representor
  devices.
- Scoping output to a specific PCIe address with `--pci-addr`.
- Listing the DOCA libraries the install reports as available on the
  current OS.
- Listing the available DOCA logger names.
- Capturing a documented, side-effect-free **capability snapshot** as
  prerequisite evidence for later `## debug` workflows.

Do **not** load this skill for general DOCA orientation, library API
work, or installation. For those, use
`doca-public-knowledge-map/SKILL.md`,
the matching `libs/<library>` skill, or
`doca-setup/SKILL.md`.

## What this skill provides

This is a **thin loader**. Substantive material lives in two companion
files:

- the capabilities companion — what `doca_caps` reports (the five documented
  capability families: devices, representors, libraries, library
  capabilities, loggers), version availability and execution
  environment, the tool's narrow error surface, its observability role
  inside other skills' workflows, and its read-only safety posture.
- the tasks companion — step-by-step workflows for the in-scope task verbs:
  `configure` (route to install), `build` (route to install), `modify`
  (refuse), `run` (the documented invocations), `test` (capability
  snapshot as install smoke-test), `debug` (what to do when the tool
  reports nothing or fails), plus a `Deferred task verbs` block routing
  out-of-scope questions.

The skill assumes a host where DOCA is already installed (or the public
NGC DOCA container is running) and the operator has whatever
permissions the public guide requires for `doca_caps` to enumerate
devices on their platform.

## What this skill deliberately does not ship

This skill is **agent guidance**, not a samples or scripts bundle. To
keep the boundary clean, it deliberately does not contain — and pull
requests should not add:

- **Pre-baked example output.** Output is install- and
  hardware-specific. A captured example pinned to one platform and
  one DOCA version misleads operators on a different platform / version.
- **Wrappers, parsers, or scripts** in any language that consume
  `doca_caps` output. The output format is documented; if a user
  wants to script against it, the right answer is "read the live
  guide, write the parser against your installed version".
- **A `samples/` or `reference/` subtree.** This is a thin loader for
  a documented CLI; substantive material lives on the public page and
  in `--help`.

## Loading order

1. Read this skill first to confirm the user's question is in
   scope (the user actually wants to invoke `doca_caps`, not learn
   about DOCA in general).
2. **For what `doca_caps` reports, version availability, error
   surface, and safety posture, see the capabilities companion.**
3. **For the documented invocations and the capability-snapshot
   workflow — `configure`, `build`, `modify`, `run`, `test`, `debug` —
   see the tasks companion.**

## Related skills

- `doca-public-knowledge-map/SKILL.md`
  — routing to the public Capabilities Print Tool guide and the rest
  of the public DOCA documentation set.
- `doca-setup/SKILL.md` — env preparation, install
  verification (`doca_caps` is the canonical first step there), and
  the *I have no install yet* path with the public NGC DOCA container.
- `doca-programming-guide/SKILL.md` —
  cross-library programming patterns, including the `## debug`
  procedure where the saved `doca_caps` snapshot is consumed.
- The matching `libs/<library>` skill — for fine-grained,
  library-specific capability questions that go beyond what
  `doca_caps` exposes.

© NVIDIA · Apache-2.0 · NVIDIA/skills

Похожие скиллы

Все скиллы по теме «DevOps и инфраструктура» →
openshell-cli NVIDIA Скилл openshell-cli для Claude Code и других агентов: проводит по командам openshell — гейтвеи, песочницы, провайдеры, профили, политики, BYOC. Поднимает песочницу руками агента без опоры на память. CX Codex +1 790установок debug-openshell-cluster NVIDIA Скилл debug-openshell-cluster помогает диагностировать сбои шлюза OpenShell, проблемы со средами Docker, Podman и Kubernetes, а также ошибки запуска песочниц. CX Codex +1 739установок aiq-deploy официальный NVIDIA AI-Q Blueprint Team Скилл aiq-deploy разворачивает и проверяет инфраструктуру NVIDIA AI-Q Blueprint, а также помогает остановить сервисы и разобрать сбои. CX Codex GP ChatGPT +1 ★ 8 052звёзд репо spark-training-gotchas Seth Hobson Скилл spark-training-gotchas диагностирует 10 частых сбоев при обучении моделей на NVIDIA DGX Spark. Помогает найти утечки памяти, троттлинг и ошибки CUDA перед долгими запусками. CX Codex +1 2 500установок spark-memory-thermal-ops Seth Hobson Скилл spark-memory-thermal-ops помогает планировать память и отслеживать нагрев NVIDIA DGX Spark во время долгих ML-запусков. Пригодится при OOM и падении производительности. CX Codex +1 2 500установок profile-model modular Скилл profile-model для Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI и OpenCode профилирует модели на MAX — находит, какие ядра едят время и насколько загружен GPU. CX Codex +1 1 300установок

Из того же набора312

Весь набор →
doca-common Скилл doca-common разбирает базовые примитивы DOCA для BlueField DPU и ConnectX NIC: контексты, устройства, буферы, завершение задач и логи. CX Codex +1 155установок doca-programming-guide Скилл doca-programming-guide для Claude Code помогает писать приложения на DOCA: выбирать образец, собирать проект и разбирать ошибки. Отвечает на общие вопросы по DOCA, не связанные с конкретной библиотекой. CX Codex +1 152установок doca-argp Помогает настраивать CLI DOCA Arg Parser: добавлять флаги, разбирать ошибки и сохранять стандартные параметры в приложениях на DOCA. CX Codex +1 151установок doca-comm-channel-admin Скилл doca-comm-channel-admin запускает инвентаризацию DOCA Comm Channel и разбирает таблицы серверов и соединений. Пригодится, чтобы проверить, какие каналы видны со стороны хоста или DPU. CX Codex +1 150установок doca-devemu Скилл doca-devemu помогает писать и отлаживать DPU-бэкенд для эмулируемых PCIe-устройств DOCA Device Emulation. Поддерживает PCI Generic, virtio-net и virtio-fs. CX Codex +1 146установок doca-container-deployment Скилл doca-container-deployment для Claude Code развёртывает DOCA-сервисы в контейнерах на BlueField через kubelet standalone. Запускает Argus, DMS, Firefly и UROM в pod-спеках и диагностирует сбои. CX Codex +1 145установок doca-gpunetio Скилл помогает писать и отлаживать DOCA GPUNetIO: связывать CUDA-ядро с сетевой очередью и проверять поддержку GPU. CX Codex +1 144установок doca-dma Скилл помогает писать и отлаживать код для копирования данных через DOCA DMA. Он пригодится при настройке memcpy между памятью хоста и DPU. CX Codex +1 143установок

Спонсоры проекта

Компании, которые помогают держать аналитику открытой