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

doca-mgmt — скилл для Claude Code: управление BlueField и ConnectX

Скилл doca-mgmt для программирования управления устройствами NVIDIA BlueField DPU и ConnectX NIC прямо из кода.

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

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

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

doca-mgmt позволяет писать код, который разговаривает с устройством на уровне управления — открывает контекст на BlueField или ConnectX, читает возможности (data-direct, congestion-control), изменяет параметры ICM и отправляет сырые команды прошивке с нужным уровнем доступа (CONFIGURATION, DEBUG_READ_ONLY, DEBUG_WRITE, DEBUG_WRITE_FULL).

Скилл предполагает, что DOCA SDK уже установлен в /opt/mellanox/doca на Ubuntu 22.04/24.04 или RHEL/SLES. Скрипты используют pkg-config и читают из /opt/mellanox/doca/{lib,include,samples,applications}. Для работы нужны права root (или cap_*) и доступ к /dev/fwctl*.

Это управление состоянием устройства, не наблюдаемость — для телеметрии и снимков нужны другие скиллы. Скилл откажет, если вы просите прямую работу с mlxconfig, перепрошивку BFB, streaming telemetry или установку самой DOCA.

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

  • открыть контекст управления на BlueField-устройстве
  • запросить поддержку data-direct у конкретного репрезентатора
  • переключить флаг congestion-control с откатом при ошибке
  • отправить сырую команду прошивке с правильным уровнем доступа
  • отладить ошибку DOCA_ERROR_IO_FAILED при работе с doca_mgmt_raw_cmd

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

  • Создай doca_mgmt_dev_ctx для основного устройства и doca_mgmt_dev_rep_ctx для VF-репрезентатора
  • Проверь, поддерживает ли репрезентатор data-direct через doca_mgmt_device_caps_general_get
  • Отправь DEBUG_READ_ONLY команду прошивке через doca_mgmt_raw_cmd с нужным opcode

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

1Через Skills CLI (Vercel)

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

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

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

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

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

Вопросы о doca-mgmt

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

Запусти npx skills add NVIDIA/skills --skill doca-mgmt -a claude-code, затем открой ~/.claude/skills/doca-mgmt/SKILL.md. Нужна установленная DOCA SDK в /opt/mellanox/doca.

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

Это скилл для программирования управления BlueField и ConnectX — открытия контекстов устройства, запроса возможностей, изменения параметров и отправки команд прошивке. Для fleet-инструментов, которые должны проверить или переключить состояние на нескольких устройствах.

Чем doca-mgmt отличается от doca-telemetry и doca-caps?

doca-mgmt — для управления и изменения состояния через API; doca-telemetry — для потоковой наблюдаемости; doca-caps — для снимков возможностей из CLI. Выбери doca-mgmt, если нужно запрограммировать модификацию состояния устройства.

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

SKILL.md · Apache-2.0
---
license: Apache-2.0
name: doca-mgmt
description: >
  Use this skill when the user is doing hands-on DOCA Management
  programming against BlueField / ConnectX devices — standing up a
  management or representor context (doca_mgmt_dev_ctx /
  doca_mgmt_dev_rep_ctx), querying device caps (data-direct,
  caps-general), toggling congestion-control global status, modifying
  diagnostics-data, setting ICM quotas, or issuing a raw firmware
  command via doca_mgmt_raw_cmd with the right scope (CONFIGURATION /
  DEBUG_READ_ONLY / DEBUG_WRITE / DEBUG_WRITE_FULL). Trigger even when
  the user does not say "DOCA Management" — typical implicit phrasings
  include "fleet tool that walks every BlueField and reads device
  state", "toggle data-direct on a VF", "set an ICM quota per
  representor", "send a raw firmware command from C",
  "DOCA_ERROR_IO_FAILED from raw_cmd", or "fwctl ioctl is failing".
  Refuse and route elsewhere for mlxconfig direct operation, BFB /
  firmware reflash, streaming telemetry, doca_caps CLI snapshots, or
  DOCA install itself — those belong to other skills.
metadata:
  author: NVIDIA <[email protected]>
  kind: library
  doca_version: "3.5"
  tags:
    - doca
    - mgmt
    - firmware
compatibility: >
  Requires DOCA SDK installed at /opt/mellanox/doca on Linux (Ubuntu
  22.04/24.04 or RHEL/SLES) with a BlueField DPU or ConnectX NIC
  attached. Reads the user's local install via `pkg-config doca-mgmt` +
  `doca-common` and inspects
  /opt/mellanox/doca/{lib,include,samples,applications}; runtime
  operations require root (or device-admin cap_*) and an /dev/fwctl*
  character device exposed by the host kernel. The validation steps
  require a live DOCA install.
---

# DOCA Management

## Examples

- **"Toggle data-direct on a VF."** — this is in scope. Use the
  management / representor context; do not drop to raw mlxconfig.
- **"DOCA_ERROR_IO_FAILED from raw_cmd."** — the firmware rejected
  the command: re-check the four-way version match, the opcode, and the
  narrowest correct scope (CONFIGURATION, DEBUG_READ_ONLY, DEBUG_WRITE,
  DEBUG_WRITE_FULL). fwctl or permission failures surface as
  `DOCA_ERROR_OPERATING_SYSTEM` instead.

## Instructions

Follow Loading order below. Open the tasks companion for configure /
raw-cmd / debug. Open the capabilities companion for scopes and
device caps. Do not open every companion file.

**Where to start:** This skill assumes DOCA is already installed
and the user is doing **hands-on management-plane work** against
a BlueField / ConnectX device — typically a fleet-management or
orchestration tool that needs to query or modify device-level
state programmatically. Open the tasks companion if the user
wants to *do* something (install / configure / build / modify /
run / test / debug / use); open the capabilities companion
when the question is *what can doca-mgmt express on this version* —
the management context model, the raw-command scope ladder, the
sub-domain surfaces (caps-general, cc-global-status, diagnostics-
data, icm-quota), version compatibility, and the safety overlay.
If the user has not installed DOCA yet, route to
`doca-setup/SKILL.md` first.

**How to use this skill.** Read this file, then search the companion file
for the `## <name>` heading the question needs and read that whole section.
Answer completely from it, quoting only its symbols and commands. Do not
browse docs; use the entry points in `doca-public-knowledge-map`. Give
environment checks as commands for the user's DOCA host. Any change to
device state also follows `doca-hardware-safety`: say so and cite it. For
out-of-scope requests, name the skill that owns them and stop.

## Example questions this skill answers well

The CLASSES of management-plane questions this skill is built to
answer, each with one worked example. The agent should treat the
*class* as the load-bearing piece — the worked example is a
single instance.

- **"Is `doca-mgmt` even the right surface, or do I want
  telemetry / bench / caps?"** — worked example: *"I'm building a
  fleet inventory tool — do I use doca-mgmt to query each
  BlueField's data-direct capability, or doca-telemetry, or
  doca_caps?"*. Answered by the *management-plane vs
  observability-plane vs read-only-CLI* selection rule in
  ## Capabilities and modes
  surface-selection table.
- **"How do I stand up a management context on a device (and a
  representor)?"** — worked example: *"open a `doca_mgmt_dev_ctx`
  on the device, then a `doca_mgmt_dev_rep_ctx` on a specific
  VF representor for caps-general programming"*. Answered by
  the management-context lifecycle in
  ## Capabilities and modes
  + the configure walk in
  ## configure.
- **"How do I query a device capability — say, whether it
  supports data-direct?"** — worked example: *"create a
  caps-general handle, call `doca_mgmt_device_caps_general_get`
  on the representor context, read the data-direct flag"*.
  Answered by the capability-query pattern in
  ## Capabilities and modes
  + the test step in ## test.
- **"How do I modify a device-level feature flag safely?"** —
  worked example: *"toggle `data_direct` on a representor;
  capture pre-state, write, verify, prepare rollback"*.
  Answered by the apply-with-rollback workflow in
  ## modify layered on the
  bundle-wide hardware-safety meta-policy referenced from
  ## Safety policy.
- **"What does the `doca_mgmt_raw_cmd` scope mean and which
  scope should I use?"** — worked example: *"I have a vendor-
  documented opcode for a `DEBUG_READ_ONLY` query — what scope
  does that need and what is the blast radius?"*. Answered by
  the command-scope ladder in
  ## Capabilities and modes
  + the raw-command verb in ## use.
- **"What does this `DOCA_ERROR_*` from a `doca_mgmt_*` call
  mean and which layer caused it?"** — worked example:
  *"`DOCA_ERROR_IO_FAILED` from `doca_mgmt_raw_cmd`"*.
  Answered by the mgmt overlay on the cross-library taxonomy
  in ## Error taxonomy
  + the layered ladder in
  ## debug that escalates to
  `doca-debug/SKILL.md` and to
  `doca-hardware-safety/SKILL.md`
  when the cause is a device-state change.

## When to load this skill

Load this skill when the user is doing **hands-on DOCA Management
work** on a host with one or more BlueField / ConnectX devices.
Concretely:

- Standing up a `doca_mgmt_dev_ctx` on a `doca_dev` to inspect
  or modify device-level state.
- Standing up a `doca_mgmt_dev_rep_ctx` on a `doca_dev_rep` (or
  via `doca_mgmt_dev_rep_ctx_create_by_pci_addr` when the
  representor is not available) to inspect or modify a VF /
  function-level configuration.
- Querying a device's general capabilities via
  `doca_mgmt_device_caps_general_*` (data-direct support and
  similar device-wide attributes).
- Programming a representor's general capabilities via the same
  `set` path.
- Querying or modifying congestion-control global status via
  `doca_mgmt_cc_global_status_*` (RP / NP protocol type,
  priority, enable / disable).
- Modifying or querying multi-domain diagnostics data via
  `doca_mgmt_diagnostics_data_*` against a specific device.
- Setting ICM quota limits per device or per representor via
  `doca_mgmt_icm_quota_*` and reading the current allocation /
  max-reached.
- Issuing a `doca_mgmt_raw_cmd` against the device's
  firmware-control endpoint, choosing the right
  `enum doca_mgmt_cmd_scope` for the operation's blast radius.
- Debugging a `DOCA_ERROR_*` returned by a `doca_mgmt_*` call
  and deciding whether the cause is a configuration mistake, a
  lifecycle ordering bug, a missing capability on the device,
  an `fwctl` ioctl failure, or a firmware-side rejection.

Do **not** load this skill for general DOCA orientation, install
of DOCA itself, live performance benchmarking, or stream-based
telemetry. For those, use
`doca-public-knowledge-map/SKILL.md`,
`doca-setup/SKILL.md`,
`doca-bench/SKILL.md`, and
`doca-telemetry/SKILL.md` respectively.

## What this skill provides

This is a **thin loader**. The body keeps only the orientation
needed to pick the right next file. The substantive
management-specific material lives in two companion files:

- the capabilities companion — what doca-mgmt can express on this
  version: the management-context object model
  (`doca_mgmt_dev_ctx` + `doca_mgmt_dev_rep_ctx`), the raw-
  command scope ladder (`DOCA_MGMT_CMD_SCOPE_CONFIGURATION`,
  `DOCA_MGMT_CMD_SCOPE_DEBUG_READ_ONLY`,
  `DOCA_MGMT_CMD_SCOPE_DEBUG_WRITE`,
  `DOCA_MGMT_CMD_SCOPE_DEBUG_WRITE_FULL`), the sub-domain
  surfaces (caps-general, cc-global-status, diagnostics-data,
  icm-quota) with their capability-query gates, the EXPERIMENTAL
  symbol-set policy (every public `doca_mgmt_*` symbol is
  tagged EXPERIMENTAL), the mgmt overlay on the cross-library
  `DOCA_ERROR_*` taxonomy, the observability surface (pre-state
  capture + post-write re-query), and the per-artifact safety
  overlay on the bundle-wide hardware-safety meta-policy.
- the tasks companion — step-by-step workflows for the eight in-scope
  verbs: `install`, `configure`, `build`, `modify`, `run`,
  `test`, `debug`, `use`. Plus a `Deferred task verbs` block
  that points out-of-scope questions at the right next skill.

The skill assumes a host or BlueField where DOCA is already
installed at the standard location and the user has the
privileges their public install profile expects (management-
plane operations typically require root or an equivalent
device-administration capability). It does not cover installing
DOCA — that path goes through
`doca-setup/SKILL.md`.

## What this skill deliberately does not ship

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

- **Pre-written DOCA Management application source code, in any
  language.** Management-plane code touches device state and a
  wrong write can take the device offline; authoring it from
  documentation prose, especially against an EXPERIMENTAL
  symbol set whose shape can change between releases, is
  forbidden by this skill. The agent's job is to route the user
  to verified reference code (the shipped DOCA samples on the
  installed package set are the canonical worked examples) and
  to prescribe a minimum-diff modification via the universal
  modify-a-sample workflow in
  `doca-programming-guide/SKILL.md`.
- **Standalone build manifests** parked inside the skill. The
  agent constructs the build manifest *in the user's project
  directory* against the user's installed DOCA, where
  `pkg-config --modversion doca-mgmt` is the source of truth.
- **Raw-command opcode catalogs.** The `doca_mgmt_raw_cmd`
  in-payload and out-payload are device / firmware specific;
  the skill names the *scope* of a command class and the
  *discipline* the agent applies (pre-state capture, scope
  ladder, rollback path) but it does NOT enumerate opcodes —
  those are vendor / device documentation and looked up via
  `doca-public-knowledge-map/SKILL.md`.
- **A `samples/`, `bindings/`, or `reference/` subtree** of any
  kind. A mock or incomplete artifact in this skill's tree,
  even one labeled "reference", is misleading: users will read
  it as buildable.

## Loading order

1. Read this skill first to confirm the user's question is
   in scope.
2. **For the management-context object model, the raw-command
   scope ladder, the sub-domain surfaces, version
   compatibility, the error taxonomy, observability, and the
   per-artifact safety overlay, see
   the capabilities companion.**
3. **For step-by-step workflows — install, configure, build,
   modify, run, test, debug, use — see the tasks companion.**

Both companion files cross-link to each other and to
`doca-public-knowledge-map/SKILL.md`
whenever the right answer is "look it up in the public docs or
the installed package layout" rather than "mgmt-specific
guidance".

## Related skills

- `doca-hardware-safety/SKILL.md` —
  the bundle-wide hardware-safety meta-policy. Because
  doca-mgmt is the surface through which agents most commonly
  *modify* device state programmatically, the safety overlay
  in the capabilities companion cross-links the meta-policy
  load-bearingly and the agent walks the hardware-safety
  ladder whenever a write is recommended.
- `doca-telemetry/SKILL.md` and
  `doca-telemetry-exporter/SKILL.md` —
  the observability surfaces for *streaming* telemetry from the
  device. Use those when the user wants live metrics; use
  doca-mgmt when the user wants point-in-time programmatic
  query or modification.
- `doca-caps/SKILL.md` — the
  read-only CLI for inspecting device capabilities. Use the
  tool when the user wants an interactive snapshot; use
  doca-mgmt when the user wants the same information through
  the C API in a fleet tool.
- `doca-bench/SKILL.md` — the
  live-performance benchmarking tool. Out of scope for
  doca-mgmt; the skill names the boundary.
- `doca-pcc/SKILL.md` and
  `doca-pcc-counters/SKILL.md` —
  programmable congestion control. doca-mgmt's
  `doca_mgmt_cc_global_status_*` surface is the *global
  enable/disable + protocol selection* control plane that
  layers on the deeper programmable-CC surface owned by
  doca-pcc.
- `doca-public-knowledge-map/SKILL.md` — the
  routing table for every public DOCA documentation source and
  the on-disk layout of an installed DOCA package.
- `doca-setup/SKILL.md` — env preparation,
  install verification, and the *I have no install yet* path
  with the public NGC DOCA container.
- `doca-programming-guide/SKILL.md` —
  general DOCA programming patterns shared by every library:
  the canonical `pkg-config` + meson build pattern, the
  universal modify-a-shipped-sample first-app workflow, the
  cross-library `DOCA_ERROR_*` taxonomy. This skill layers
  management-plane specifics on top.
- `doca-debug/SKILL.md` — the cross-cutting
  debug ladder. Management-specific debug overlays on top of
  it.
- `doca-version/SKILL.md` — the version
  detection / four-way match rule every per-artifact `##
  Version compatibility` anchor builds on. This skill quotes
  the management-specific overlay only.
- `doca-structured-tools-contract/SKILL.md` —
  the JSON-schema contracts for the agent-preferred structured
  helpers; the `## Command appendix` in the tasks companion defers to
  them before falling back to the manual chain.

© NVIDIA · Apache-2.0 · NVIDIA/skills

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

Все скиллы по теме «DevOps и инфраструктура» →
service-itsm-incident-mgmt-configure forcedotcom Скилл service-itsm-incident-mgmt-configure для Claude Code читает и переключает главную настройку Incident Management в Salesforce ITSM на уровне организации. Включает или выключает режим без ручных походов в Setup. CX Codex +1 1 200установок azure-mgmt-mongodbatlas-dotnet Microsoft Скилл azure-mgmt-mongodbatlas-dotnet для Claude Code управляет организациями MongoDB Atlas в Azure через .NET-библиотеку Azure.ResourceManager.MongoDBAtlas. Настраивает подписки и биллинг в Azure Marketplace. CX Codex +1 ★ 3 232звёзд репо azure-mgmt-arizeaiobservabilityeval-dotnet Microsoft Скилл azure-mgmt-arizeaiobservabilityeval-dotnet помогает управлять ресурсами Arize AI в Azure через .NET SDK Azure.ResourceManager.ArizeAIObservabilityEval. Он нужен для настройки мониторинга ML-моделей в Azure. CX Codex +1 ★ 3 232звёзд репо esp32-firmware-engineer adamlipecz Скилл esp32-firmware-engineer помогает писать, проверять и отлаживать прошивки ESP32 на ESP-IDF. При работе с железом сначала выясняет плату, вариант чипа и подключённые устройства. CX Codex +1 1 500установок iot-firmware ruvnet Скилл iot-firmware для Claude Code разворачивает прошивки на парке устройств через канареечный релиз и блокирует выкатку при аномалиях. Обновляет IoT-устройства через агент. CX Codex +1 903установок iot-fleet ruvnet Скилл iot-fleet управляет флотами устройств Cognitum Seed через CLI-утилиту cognitum-iot. Помогает создавать группы оборудования, добавлять устройства и контролировать удаление. CX Codex +1 766установок

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

Весь набор →
doca-dms Скилл doca-dms для Claude Code управляет NVIDIA DOCA Management Service на BlueField, хосте или в Kubernetes. Выполняет локальные операции через dms-cli и удалённые gNMI/gNOI-операции. CX Codex +1 138установок doca-eth Помогает настроить очереди пакетов DOCA Ethernet на сетевых картах ConnectX и DPU BlueField, выбрать тип RX-очереди и разобрать ошибки передачи. CX Codex +1 137установок doca-sha Скилл doca-sha для Claude Code помогает работать с аппаратным ускорением SHA на BlueField-2 через DOCA. Выбирает режим хеширования и разбирает ошибки. CX Codex +1 131установок doca-version Скилл doca-version для Claude Code сверяет четыре источника версии DOCA и выявляет расхождения между сборкой и рантаймом. CX Codex +1 130установок doca-pcc-counters Скилл doca-pcc-counters для Claude Code и Codex, который помогает вооружить и считать аппаратные PCC-счётчики (CNP, RTT, WRED-drop) на устройствах ConnectX / BlueField через pcc_counters.sh. CX Codex +1 128установок nvidia-skills Плагин подбирает NVIDIA-скиллы для CUDA, GPU, AI-агентов, обучения моделей, робототехники и симуляции. ★ 4 106звёзд репо doca-telemetry Скилл для чтения аппаратных счётчиков DOCA с BlueField DPU или ConnectX NIC через библиотеки doca_telemetry_pcc, doca_telemetry_dpa, doca_telemetry_diag и других. CX Codex +1 ★ 4 106звёзд репо nvshmem-configure-nic-pe-mapping Скилл nvshmem-configure-nic-pe-mapping подбирает привязку сетевых адаптеров к процессам NVSHMEM и готовит переменные окружения по топологии узла. CX Codex +1 ★ 4 106звёзд репо

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

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