# Doca version

> Doca version is an open-source agent skill. DOCA version handling: detect the installed release and validate the four-way match across pkg-config doca-common, applications/VERSION, doc. 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-version
- **Repository:** https://github.com/nvidia/skills
- **GitHub stars:** 4,037
- **License:** Apache-2.0
- **Skill name:** doca-version
- **Collection:** https://github.com/NVIDIA/skills
- **Listing updated:** 2026-11-17

## About

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).

## When your agent uses it

> 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).

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

## Install

### Claude Code

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

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

### Codex

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

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

### Cursor

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

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

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

### VS Code

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

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

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

### Other agents

Get the folder:

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

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

## FAQ

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

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

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

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