Skip to main content
skill CX Codex

doca-version — Claude Code skill for DOCA version detection

doca-version is a Claude Code skill that checks four DOCA version sources and detects build-to-runtime drift.

Apache-2.0 130 installs ★ 4,106 updated 2026-10-23

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add NVIDIA/skills --skill doca-version -a claude-code
Open on GitHub

What doca-version does

Its scope is strictly version handling — package installation, per-library API questions, and DOCA_ERROR_* taxonomy each belong to their own skill (doca-setup, doca-programming-guide).

The detection chain checks all four authoritative sources and flags any mismatch between them. It can parse NGC container tags, look up whether a specific capability or API is available on the current release, and trace drift between what was compiled and what is running. If apt sources are pinned to one release while a different one is installed, the skill catches that conflict before the next apt install runs.

Validation steps need a live DOCA install at /opt/mellanox/doca. The skill itself loads as an overlay on top of any artifact skill — no separate DOCA install required just to read it. Once all four sources agree, further work on the component hands off to the matching library or service skill.

What it helps with

  • Determine which DOCA version is actually installed on a host
  • Validate the four-way version match across pkg-config, applications/VERSION, doca_caps, and bfver
  • Diagnose build-vs-runtime drift when DOCA_ERROR_NOT_SUPPORTED appears at runtime
  • Check whether a specific API or capability is available on the current DOCA release
  • Verify apt-source consistency before upgrading or rolling back a BlueField BFB

Example prompts for the agent

  • What DOCA version do I actually have on this host? Run the four-source detection chain.
  • The program built fine but does nothing on the wire — check whether all four version sources match.
  • Is symmetric RSS hash mode in Flow available on DOCA 3.5?

How to install doca-version

1Skills CLI (Vercel)

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

2Manually: put the files in place

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

Copy the whole skill folder; for one project use .claude/skills/doca-version/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about doca-version

How do I install doca-version in Claude Code?

Run npx skills add NVIDIA/skills --skill doca-version -a claude-code. The skill will then be available at ~/.claude/skills/doca-version/SKILL.md.

What does the doca-version skill do?

It detects the installed DOCA release by querying four sources (pkg-config doca-common, applications/VERSION, doca_caps --version, bfver/mlnx-release) and identifies any mismatch between them. It also handles NGC tag semantics and per-release capability lookups.

Does DOCA need to be installed before loading this skill?

No DOCA install is required to load the skill itself. The validation steps inside it do require a live DOCA instance at /opt/mellanox/doca.

Source text

SKILL.md · Apache-2.0
---
license: Apache-2.0
name: doca-version
description: >
  DOCA version handling: detect the installed release and validate the
  four-way match across pkg-config doca-common, applications/VERSION,
  doca_caps --version, and bfver/mlnx-release on BlueField; reason about
  NGC tags; look up whether a capability exists on this release; diagnose
  build-vs-runtime drift. Use this skill alongside doca-debug when a symptom
  smells of version skew: "built but nothing on the wire", "undefined
  reference to a symbol the docs claim exists", "DOCA_ERROR_NOT_SUPPORTED
  at runtime", "what does latest mean for this tag", or "is my LTS still
  supported". Once all four sources match, the component's build / run
  workflow belongs to its own library, service or tool skill. Refuse
  install / package choice (doca-setup), per-library API questions
  (matching library skill), DOCA_ERROR_* taxonomy
  (doca-programming-guide), and the general debug ladder (doca-debug).
metadata:
  author: NVIDIA <[email protected]>
  kind: library
  doca_version: "3.5"
  tags:
    - doca
    - version
    - compatibility
compatibility: >
  No DOCA install required to read this skill (it is an overlay
  loaded against any DOCA artifact skill); the validation steps
  within DO require a live DOCA install at /opt/mellanox/doca.
---

# DOCA version

## Examples

- **"What DOCA version do I actually have installed?"** — run the
  four-source detection chain and require a four-way match.
- **"The program built but does nothing on the wire."** — treat
  mixed-install drift as a version problem before rewriting application
  code.

## Instructions

Follow Loading order below. Open the tasks companion for detect /
validate / diagnose, and the capabilities companion for the four-way
match and NGC tag rules. Do not open every companion file.

**Where to start:** This skill is the bundle's single source of
truth for DOCA *version handling*. Open
the tasks companion if the user wants to *do* something with the
version (detect / validate / diagnose mismatch); open
the capabilities companion when the question is *what does
version handling cover* (the four-way match, the detection chain,
NGC semantics, the per-library overlay pattern). Every other skill
in the bundle that touches version routes here — they MUST NOT
redefine the rules.

## Example questions this skill answers well

The CLASSES of version-handling 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.

- **"What DOCA version do I actually have installed?"** — worked
  example: *"the docs say 3.3 but I'm not sure what's on this
  host"*. Answered by the canonical detection chain in
  ## configure +
  ## Capabilities and modes
  source-of-truth table.
- **"My program built but does nothing on the wire — is my install
  consistent?"** — worked example: *"`pkg-config --modversion`
  says 3.3.0; `doca_caps --version` says 3.2.0"*. Answered by the
  four-way match rule in
  ## Version compatibility
  + the partial-install diagnosis in
  ## debug.
- **"Is this DOCA capability / API / sample on the version I
  have?"** — worked example: *"is the symmetric-RSS hash mode in
  Flow 2.6.0"*. Answered by the version-matrix lookup procedure in
  ## test (which uses the
  `version-matrix.json` schema defined in
  `doca-structured-tools-contract/SKILL.md#schemas`
  with fallback to per-library docs via
  `doca-public-knowledge-map/SKILL.md`).
- **"Can I run my host package version X against BFB version Y?"** —
  worked example: *"host is 3.5.0 GA, BlueField BFB is 3.2.3 LTS"*.
  Answered by the routing to the
  [DOCA Compatibility Policy](https://docs.nvidia.com/doca/sdk/doca-compatibility-policy/index.html)
  documented in
  ## Version compatibility.
- **"I'm inside the NGC DOCA container — what does the version
  match look like?"** — worked example: *"do I still need to check
  pkg-config / applications/VERSION / doca_caps separately?"*.
  Answered by the NGC container rule in
  ## Version compatibility
  + the container path in
  ## configure.
- **"How do I write a per-library version-compatibility section
  for a new skill?"** — worked example: *"adding `doca-comch` to
  the bundle, what does its `## Version compatibility` look
  like?"*. Answered by the per-library overlay pattern in
  ## Safety policy
  + the worked-example template in
  ## modify.
- **"My `apt list` shows DOCA `3.3.0109`, but `/etc/apt/sources.list.d/doca.list`
  is pinned at `latest` / a different release — is the next
  `apt install doca-*` going to silently upgrade me?"** — worked
  example: *"I rolled back BFB to 3.1.0105 but my sources still
  point at the latest channel."* Answered by the apt-source
  consistency precheck in
  ## apt-source consistency,
  which enumerates the three legitimate shapes of a configured
  DOCA apt source (network URL, local file-repo, RHEL/OEL
  equivalent) and the *do-not-install-until-the-source-matches*
  rule that protects pinned installs from accidental drift.

## When to load this skill

Load this skill whenever version handling is the load-bearing
concern. The decision must be made **before** the agent composes
its first sentence — the activation checklist below is the same
one referenced from
`AGENTS.md ## Cross-cutting overlay activation triggers` (bundle `AGENTS.md#cross-cutting-overlay-activation-triggers`),
mirrored here so the activation rule is at hand whenever this skill
is consulted.

## Agent activation checklist — load this skill at the START of the answer when any cell below is true

| Trigger class | Concrete prompt-side signals (any one fires the overlay) |
| --- | --- |
| Direct version question | *"what DOCA version do I have"*, *"is X consistent"*, *"is feature Y supported on version Z"*, *"can I mix host package version A with BFB version B"*, *"is my LTS still supported"*, *"what does the version string mean"* |
| Container tag question | any prompt that mentions a specific NGC container tag, or asks about `latest`, or asks how to pin a tag in a Dockerfile / pod spec / Compose file. The agent MUST also cite the *"never invent a tag string from memory, never quote `latest` without confirming it"* rule from ## Safety policy. |
| Build vs runtime drift | any debug session where the symptom is *"the program built fine but DOCA_ERROR_NOT_SUPPORTED at runtime"*, *"undefined reference to a symbol the docs say exists"*, *"my code does nothing on the wire"*, *"counter didn't increment"* — these are the canonical partial-install symptoms |
| Upgrade / downgrade plan | the user is planning to upgrade or downgrade DOCA on a host already running other DOCA workloads, or to refresh the BFB on a BlueField pair already attached to a host |
| Per-artifact cross-link | a per-artifact skill's `## Version compatibility` section cross-links here for the rule body, OR the agent is about to author a new per-artifact skill and needs the overlay template |

When any cell above fires, the agent MUST:

1. Cite the **four-source detection chain** from ## Capabilities and modes explicitly in the answer — `pkg-config --modversion doca-common` → `cat /opt/mellanox/doca/applications/VERSION` → `doca_caps --version` → `bfver` plus `cat /etc/mlnx-release` (BlueField hosts). Do not paraphrase or summarize the chain; cite the commands by name. Do NOT substitute `mlxprivhost` or `bfb-info` for the BFB leg — those are common hallucinations and the bundle explicitly bans them in ## Capabilities and modes.
2. State the **four-way match rule** from ## Version compatibility verbatim if the prompt could possibly involve a mismatch (every deploy-shape question and every debug-shape question can; orientation-shape questions usually cannot).
3. Refuse to invent a version string. If the agent doesn't have the actual `pkg-config --modversion` output from the user's host, the answer must say so and route to the detection chain — not assert a version from training-data recall.

## Universal version-coherence trigger

Whenever ANOTHER overlay (e.g. `doca-setup/SKILL.md`, `doca-hardware-safety/SKILL.md`, `doca-container-deployment/SKILL.md`, `doca-bare-metal-deployment/SKILL.md`) calls a `## test` / `## configure` / `## modify` step that requires *"the install is healthy"* or *"versions are consistent"*, that step MUST resolve to a citation of this skill's four-source detection chain and four-way match rule. The agent does NOT redefine the rule per-overlay — every step that needs a version verification must route here. This is the *only* place in the bundle that owns the rule body.

Do **not** load this skill for general DOCA orientation, for
install procedures (use `doca-setup/SKILL.md`),
or for library-specific API questions (use the matching library
skill).

## What this skill provides

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

- the capabilities companion — the version-handling surface: the canonical
  source-of-truth table for version detection, the four-way match
  rule, NGC container semantics, the per-library overlay pattern,
  the routing to the DOCA Compatibility Policy, the error
  taxonomy for version-related failures (pkg-config missing,
  partial install, BFB/host mismatch, NGC mixing), the
  observability surface (which command to read for which version
  source), and the safety policy ("never invent a version, never
  quote `latest`").
- the tasks companion — step-by-step workflows for the six in-scope
  version verbs: `configure` (detect on this host), `build`
  (build-time match), `modify` (update a version pin in a build
  manifest), `run` (runtime check), `test` (four-way validation +
  version-matrix lookup), `debug` (diagnose mismatch / partial
  install). Plus a `Deferred task verbs` block.

## Loading order

1. Read this skill first to confirm the user's question is in
   scope.
2. **For the version-detection sources, four-way match rule, NGC
   semantics, per-library overlay pattern, error taxonomy,
   observability, and safety policy, see the capabilities companion.**
3. **For step-by-step workflows — configure, build, modify, run,
   test, debug — see the tasks companion.**

## Related skills

- `doca-structured-tools-contract/SKILL.md` —
  the JSON schemas for the helper tools the agent should prefer
  when present. This skill's `## test` workflow uses the
  `version-matrix.json` schema defined there; do not redefine the
  schema here.
- `doca-public-knowledge-map/SKILL.md` —
  the routing table to public DOCA docs, including the
  Compatibility Policy. This skill cites the Compatibility Policy
  URL once via that map; it does not duplicate the routing.
- `doca-setup/SKILL.md` — env-side install /
  verify / NGC container path. This skill assumes its
  preconditions are satisfied (i.e., something is installed
  somewhere; the version question is *what was installed and is
  it consistent*).
- `doca-programming-guide/SKILL.md` —
  program-side guidance (quote the version observed, header-wins,
  capability-discovery rules). The program-side `## Version
  compatibility` section there is now a 3-5 line redirect to this
  skill plus the program-side overlay (quote vs assume; never use
  agent-memory version).
- `doca-debug/SKILL.md` — the cross-cutting
  debug ladder. Layer 2 (*version mismatch*) of that ladder is
  owned by this skill's `## debug` workflow.

© NVIDIA · Apache-2.0 · NVIDIA/skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set312

The whole set →
doca-compress doca-compress is a Claude Code skill for moving DEFLATE compression and DEFLATE or LZ4 decompression to DOCA Compress. It activates for task setup, buffer checks, and accelerator errors. CX Codex +1 140installs doca-dms doca-dms is a Claude Code skill for managing NVIDIA DOCA Management Service on BlueField, hosts, and Kubernetes, with local dms-cli and remote gNMI/gNOI operations. CX Codex +1 138installs doca-eth Guides DOCA Ethernet packet queue setup on BlueField DPUs and ConnectX NICs, covering RX queue selection, buffer sizing, and error diagnosis. CX Codex +1 137installs doca-sha The doca-sha skill guides SHA acceleration through DOCA on BlueField-2. Use it to choose a hashing mode, inspect capabilities, and diagnose API errors. CX Codex +1 131installs doca-mgmt doca-mgmt — a skill for programming device management on NVIDIA BlueField DPU and ConnectX NIC from your code. Build fleet tools that query device state, toggle flags like data-direct, and send firmware commands. CX Codex +1 128installs doca-pcc-counters doca-pcc-counters — a skill for Claude Code and Codex that arms and reads firmware PCC diagnostic counters (CNP, RTT, WRED-drop) on ConnectX / BlueField devices via pcc_counters.sh. CX Codex +1 128installs nvidia-skills This plugin finds NVIDIA skills for GPU acceleration, CUDA, AI agents, model training, robotics, Physical AI, Omniverse, and simulation. ★ 4,106repo stars doca-telemetry Skill for reading DOCA hardware counters from BlueField DPU or ConnectX NIC via doca_telemetry_pcc, doca_telemetry_dpa, doca_telemetry_diag and other per-domain libraries. CX Codex +1 ★ 4,106repo stars

Project sponsors

Companies that keep this analytics open