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

doca-comm-channel-admin — скилл для Claude Code

Скилл doca-comm-channel-admin запускает инвентаризацию DOCA Comm Channel и разбирает таблицы серверов и соединений. Пригодится, чтобы проверить, какие каналы видны со стороны хоста или DPU.

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

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

Что делает doca-comm-channel-admin

Скилл помогает вызвать doca_comm_channel_admin и прочитать его таблицы SERVERS и CONNECTIONS: в них показаны имя сервера, PID, занятость относительно максимума и PCIe-адрес. Бинарный файл сканирует все устройства doca_dev с поддержкой comch на текущей стороне через resourcedump и печатает один общий результат. Это чтение состояния, не управление каналами.

Для работы нужны Linux и установленный DOCA SDK в /opt/mellanox/doca с подкомпонентом Comm Channel tooling; resourcedump должен быть доступен. Чтобы таблицы не были пустыми, нужен активный канал host↔DPU, созданный через библиотеку doca-comch. Сам бинарный файл не принимает аргументы приложения и не умеет выбирать устройство, сбрасывать или перезапускать канал. Для смены состояния нужен другой инструмент.

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

  • перечислить видимые comch-серверы и соединения
  • проверить занятость соединений относительно максимума
  • сопоставить строки таблиц с сервером по имени и PID
  • сверить видимость канала с состоянием программы

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

  • Покажи серверы и соединения comch, видимые на этой стороне.
  • Сопоставь канал, который видит программа, с таблицами администратора.
  • Объясни, что означают строки SERVERS и CONNECTIONS для этого сервера.

Как установить doca-comm-channel-admin

1Через Skills CLI (Vercel)

npx skills add NVIDIA/skills --skill doca-comm-channel-admin -a claude-code

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

~/.claude/skills/doca-comm-channel-admin/SKILL.md

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

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

Вопросы о doca-comm-channel-admin

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

Выполните npx skills add NVIDIA/skills --skill doca-comm-channel-admin -a claude-code. Файл скилла находится по пути ~/.claude/skills/doca-comm-channel-admin/SKILL.md.

Что делает doca-comm-channel-admin?

Запускает однократное чтение всех comch-совместимых устройств на текущей стороне и выводит таблицы серверов и соединений. Скилл помогает интерпретировать эти строки.

Что нужно, чтобы таблицы содержали каналы?

Нужен активный канал host↔DPU, созданный через doca-comch, и установленный DOCA SDK с инструментами Comm Channel и доступным resourcedump.

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

SKILL.md · Apache-2.0
---
license: Apache-2.0
name: doca-comm-channel-admin
description: >
  Use this skill to enumerate host↔DPU DOCA comch (formerly Comm
  Channel) servers and connections via the shipped
  doca_comm_channel_admin binary — listing comch-capable devices and
  decoding the per-device server / connection table (server name, PID,
  in-use / max, PCIe address). The shipped binary is a SINGLE-SHOT
  SCAN-AND-PRINT tool with no registered arguments — NO list / inspect /
  drain / restart subcommands; one inventory pass over every
  comch-capable doca_dev on this side. Channel reset / drain / restart
  go to doca-comch (program side), doca-setup / doca-hardware-safety
  (driver reload), or BFB / RShim — NOT to this binary. Trigger on
  phrasings like "list comch servers", "which channels are active on
  this BlueField", or "verify admin tool sees same channel as program."
  Refuse and route elsewhere for the comch programming API, library
  install, protocol design, channel reset, or general orientation.
metadata:
  author: NVIDIA <[email protected]>
  kind: tool
  doca_version: "3.5"
  tags:
    - doca
    - comch
    - tools
compatibility: >
  Requires DOCA SDK installed at /opt/mellanox/doca on Linux (Ubuntu
  22.04/24.04 or RHEL/SLES) with the Comm Channel tooling subpackage so
  the CLI is present under /opt/mellanox/doca/tools/. Runs from either
  the x86/Arm host or the BlueField Arm side; a live host↔DPU comch
  channel created via the doca-comch library is needed for non-empty
  tables. The validation steps require a live DOCA install.
---

# DOCA Comm Channel Admin Tool

## Examples

- **"Which comch servers and connections are currently visible?"** —
  this is in scope. Stay on the admin CLI; do not open a new
  comch channel from this skill.
- **"The program reports CONNECTED but the admin tool lists zero
  channels."** — cross-check representor binding before rewriting
  the comch app.

## Instructions

Follow Loading order below. Open the tasks companion for run /
debug. Open the capabilities companion for table columns and
error layers. Do not open every companion file.

> **Actual binary contract.** `doca_comm_channel_admin` is one
> zero-application-argument, read-only scan-and-print operation.
> It scans every comch-capable `doca_dev` on the current side via
> `resourcedump` (MFT) and prints SERVERS and CONNECTIONS tables.
> It has no list, inspect, device-scope, drain, restart, or other
> application operation. This skill does not retain conceptual
> workflows under invented command names.

**Where to start:** This is a tool skill for invoking the DOCA Comm
Channel Admin Tool — the **read-only inventory** CLI counterpart
to the `doca-comch/SKILL.md` library. The
shipped `doca_comm_channel_admin` binary takes **no arguments
beyond ARGP defaults** (`--help`, `--version`, `--log-level`,
`--sdk-log-level`, `--json`) and performs **one inventory pass**
per invocation: it walks every `doca_dev` on this side, filters
to comch-capable devices, shells out to `resourcedump` (MFT) on
each, and prints two ASCII tables (SERVERS and CONNECTIONS).
There is no `list` subcommand, no `inspect` subcommand, no
`drain` flag, and no `restart` flag — those are not part of the
tool's surface. Open the tasks companion and start at
`## run` for the single-shot invocation, or
`## debug` when the user reports the tool sees
a different channel set than the program. Open
the capabilities companion when the question is *what
the printed tables actually mean* and *what is not in this
tool's scope*. If the user has not installed DOCA yet, route to
`doca-setup/SKILL.md` first; if the user
needs MFT (`resourcedump` on `PATH` with the privilege documented
for the installed release), `doca-setup` + `doca-public-knowledge-map`
cover that. If the user is holding pre-2.5 docs that mention
"Comm Channel", route to
`doca-comch/SKILL.md`
for the rename rule. If the user wants to *change* channel
state, route to the program-side
reconnect lifecycle in `doca-comch/SKILL.md`
or to BlueField mode / driver reload in
`doca-setup/SKILL.md` +
`doca-hardware-safety/SKILL.md` — **not**
to this tool.

## Example questions this skill answers well

The CLASSES of admin-tool 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.

- **"Which comch servers and connections are currently visible?"** —
  worked example: *"print every server and connection row visible
  on this side"*. Answered by the scan-and-print surface in
  the capabilities companion
  + the single invocation in
  the tasks companion.
- **"What does the tool report for this server or connection?"** —
  locate the matching row in the SERVERS or CONNECTIONS table;
  there is no second per-channel query. Answered by
  the capabilities companion
  + the tasks companion.
- **"How do I know the admin tool's view matches what my Comch
  program sees?"** — worked example: *"the program reports
  CONNECTED but the admin tool lists zero channels"*. Answered by
  the cross-checking pattern in
  the tasks companion and the representor-binding
  layer in
  the capabilities companion.
- **"Is this admin tool on my installed DOCA version, and does it
  match the comch library version?"** — worked example: *"is the
  tool available on DOCA 2.4"*. Answered by the overlay in
  the capabilities companion,
  which redirects to the canonical
  `doca-version/SKILL.md` rules and adds the
  Comm Channel Admin Tool specifics.
- **"The tool prints nothing — is the install broken or is there
  genuinely no channel?"** — worked example: *"`list` returned an
  empty result on a host with a known-good Comch client"*.
  Answered by the empty-output interpretation rules in
  the tasks companion +
  the capabilities companion.

## Audience

This skill serves **external operators and AI agents who need to
inventory a host-DPU comch channel from the outside**
— after the `doca-comch/SKILL.md` library
has been used to create the channel from a program. Concretely:

- A platform operator who runs a Comch-using service on BlueField
  and needs to confirm the channel is healthy before declaring the
  service ready.
- A developer of a Comch consumer who sees `DOCA_ERROR_AGAIN` or a
  silent stall on the program side and wants to read the channel's
  state from outside the program rather than guessing.
- An AI agent capturing the external server/connection rows before
  recommending a program-side code or lifecycle change.

It is **not** for users debugging the admin tool itself, **not** a
substitute for the live public DOCA Comm Channel Admin Tool guide,
and **not** the right place for users learning the comch API —
that audience belongs in
`doca-comch/SKILL.md`.

The tool is shipped as a CLI binary under
`/opt/mellanox/doca/tools/`, 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.

## When to load this skill

Load this skill when the user is — or the agent needs to — invoke
the DOCA Comm Channel Admin Tool on a real host or BlueField Arm
with DOCA installed (or inside the public NGC DOCA container with
the right device passthrough). Concretely:

- Listing currently active comch channels on a host or DPU.
- Reading the row for one named server or connection from the
  complete zero-argument scan.
- Cross-checking the admin tool's view against the program-side
  connection callback state when the two appear to disagree.
- Capturing a side-effect-free channel snapshot as prerequisite
  evidence for a later debug session that crosses program /
  channel / driver layers.

Do **not** load this skill for general DOCA orientation, the comch
programming API, library install, or comch protocol design. For
those, route to
`doca-public-knowledge-map/SKILL.md`,
`doca-comch/SKILL.md`, 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 the Comm Channel Admin Tool reports:
  the two read-only tables, the version-availability overlay
  that redirects to `doca-version/SKILL.md`,
  the layered error taxonomy (tool-not-installed / device-binding
  / channel-discovery / channel-state-stuck / permission /
  version / cross-cutting), the tool's role as an observability
  primitive for `doca-comch/SKILL.md`
  debug sessions, and the read-only safety policy.
- the tasks companion — step-by-step workflows for the in-scope task verbs:
  `configure` (route to install), `build` (route to install),
  `modify` (refuse), `run` (one scan-and-print), `test`
  (cross-check the printed rows), `debug` (the layered
  diagnosis ladder), plus a `Deferred task verbs` block and a
  `Command appendix` that honors the bundle's
  `doca-structured-tools-contract/SKILL.md`
  preamble.

The skill assumes a host or BlueField where DOCA is already
installed (or the public NGC DOCA container is running with the
right device passthrough) and the operator has whatever privileges
the public DOCA Comm Channel Admin Tool guide requires.

## 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:

- **Verbatim flag inventories, subcommand names, or output column
  names.** The public DOCA Comm Channel Admin Tool guide on
  `docs.nvidia.com` and the installed `--help` on the user's
  version are the joint source of truth; copying them here pins
  the skill to one release and silently rots when the tool
  evolves. The skill routes the agent at those sources instead.
- **Pre-baked example output.** Output is install-, version-, and
  channel-state-specific. A captured example will mislead an
  operator on a different platform / state.
- **Wrappers, parsers, or scripts** in any language that consume
  the admin tool's output. The output format is documented; users
  who want to script against it should read the live guide and
  write the parser against their 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 wants to inventory a comch
   channel from the outside, not learn the comch API).
2. **For what the tool reports, version availability, the layered error surface,
   observability, and safety posture, see
   the capabilities companion.**
3. **For the single invocation and cross-check
   workflow — `configure`, `build`, `modify`, `run`, `test`,
   `debug`, plus the `Command appendix` — see
   the tasks companion.**

## Related skills

- `doca-comch/SKILL.md` — the library
  whose channels this tool inventories. Pair them in every
  triage session: the program-side connection callback and the
  admin tool's channel state are the two halves of the same
  picture.
- `doca-public-knowledge-map/SKILL.md`
  — routing to the public DOCA Comm Channel Admin Tool guide and
  the rest of the public DOCA documentation set.
- `doca-version/SKILL.md` — canonical DOCA
  version-handling rules. The `## Version compatibility` section
  in the capabilities companion is a concise overlay
  that redirects here for the body.
- `doca-structured-tools-contract/SKILL.md`
  — the bundle's detect → prefer → fall back → report contract for
  structured helper tools. The Command appendix in
  the tasks companion honors this contract.
- `doca-setup/SKILL.md` — env preparation,
  install verification, representor visibility checks, and the
  *I have no install yet* path with the public NGC DOCA
  container. This skill assumes its preconditions are satisfied.
- `doca-debug/SKILL.md` — the cross-cutting
  debug ladder. The Comm Channel Admin Tool slots in at the
  *runtime* layer as the read-only inventory surface before any
  code change is recommended.

© NVIDIA · Apache-2.0 · NVIDIA/skills

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

Каталог скиллов SKILL.md →
comm-lit-review wanshuiyin Скилл comm-lit-review собирает обзоры научной литературы по связи и беспроводным сетям. Сначала ищет статьи в личной базе Zotero и локальных PDF, а затем проверяет базы IEEE Xplore и ScienceDirect. CX Codex +1 401установок inter-agent-comm-security-detection Tencent Скилл inter-agent-comm-security-detection для Claude Code проверяет безопасность взаимодействия между агентами: утечки данных, подмену отправителя и повышение привилегий. Проверяет мультиагентные системы. CX Codex +1 ★ 7 607звёзд репо agent-comm keshrath MCP-сервер agent-comm для Claude Code связывает параллельные сессии ИИ-агентов общей памятью, блокировками файлов и сообщениями. Координирует одновременную работу над кодом в одном проекте. CX Codex +1 ★ 11звёзд репо partner-channel-program Maya-Beth Finotti Скилл partner-channel-program проектирует архитектуру B2B- или B2C-партнёрской программы с нуля: от проверки готовности бизнеса до выбора моделей сотрудничества и экономики. CX Codex +1 17 200установок partner-channel-conflict Maya-Beth Finotti Скилл partner-channel-conflict формирует правила разрешения конфликтов между прямыми продажами и партнёрами. Помогает регламентировать регистрацию сделок и нейтральность выплат репам. CX Codex +1 17 200установок tech-podcast-youtube-channel Samuel Berthe Скилл tech-podcast-youtube-channel помогает организаторам конференций вести постоянный подкаст или канал на YouTube между событиями. Задаёт регулярность, пайплайн гостей и правила передачи проекта новому владельцу. CX Codex +1 6 800установок

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

Весь набор →
doca-bf4-deployment Скилл doca-bf4-deployment для день-1 развёртывания BlueField-4 DPU через BMC: установка ISO, обновление прошивки PLDM, настройка Grace Ubuntu. Каждый мутирующий шаг требует явного подтверждения и контролируется политикой отката. CX Codex +1 155установок 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-caps Скилл doca-caps для Claude Code запускает read-only CLI и показывает, какие устройства и библиотеки DOCA видит на хосте. Он также проверяет возможности устройства и помогает сохранить снимок для отладки. CX Codex +1 147установок 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установок

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

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