New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Doca Version

by NVIDIA in NVIDIA/skills

A skill your agent uses when the user is doing DOCA version handling — detecting the installed release, validating the four-way match across pkg-config doca-common, applications/VERSION, docacaps…

OfficialApache-2.0Auto-check passed

Install Doca Version

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/skills doca-version --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/doca-version .claude/skills/doca-version && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
doca-version
GitHub stars
3.5k
Token cost
~3k tokens
SKILL.md length
1,299 words
Files
7
Skills in repo
380
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when the user is doing DOCA version handling — detecting the installed release, validating the four-way match across pkg-config doca-common, applications/VERSION, docacaps…

  • Works in 3 steps: Cite the four-source detection chain… → State the four-way match rule from… → Refuse to invent a version string. If…
  • The user is doing DOCA version handling — detecting the installed release
  • SKILL.md covers Example questions this skill…, When to load this skill, Agent activation checklist —… and Universal version-coherence…, plus 3 more sections
  • Calls apt

What it does

Doca Version is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Use this skill when the user is doing DOCA version handling — detecting the installed release, validating the four-way match across pkg-config doca-common, applications/VERSION, docacaps --version, and bfver/mlnx-release on BlueField, reasoning about NGC container tags, looking up whether a capability is on the installed release, or diagnosing build-vs-runtime drift. Trigger even when the user does not explicitly say "DOCA version" or "four-way match" — typical implicit phrasings include "program built but does…

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files (for example `BENCHMARK.md`, `CAPABILITIES.md` and `TASKS.md`). Compatibility notes: 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…

The repository describes itself as: Agent Skills for NVIDIA products — install into Claude Code, Codex, and other coding agents to run Physical AI, robotics, simulation, CUDA, and RAG workflows end to end. The licence is Apache-2.0.

When your agent uses it

  • The user is doing DOCA version handling — detecting the installed release
  • Validating the four-way match across pkg-config doca-common
  • Applications/VERSION
  • Docacaps --version

Example prompts

  • “DOCA version”
  • “four-way match”
  • “program built but does nothing on the wire”
  • “/doca-version”

Requirements

  • Compatibility (from SKILL.md): 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.

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Cite the four-source detection chain from CAPABILITIES.md ## Capabilities and modes explicitly in the answer — pkg-config --modversion…
  2. State the four-way match rule from CAPABILITIES.md ## Version compatibility verbatim if the prompt could possibly involve a mismatch…
  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…

What it can do on your machine

Read from SKILL.md and the folder at commit 67a13c0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • apt

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.nvidia.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

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

    From compatibility in the SKILL.md frontmatter.

Context cost

Doca Version loads about 3k tokens when it runs. Until then it costs about 258 tokens; SKILL.md has 1,299 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~258
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA/skills at commit 67a13c0, republished under its Apache-2.0 licence (© NVIDIA). 1,299 words, ~3,030 tokens.

Download SKILL.mdSave it as .claude/skills/doca-version/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
doca-version
description
Use this skill when the user is doing DOCA version handling — detecting the installed release, validating the four-way match across pkg-config doca-common, applications/VERSION, doca_caps --version, and bfver/mlnx-release on BlueField, reasoning about NGC container tags, looking up whether a capability is on the installed release, or diagnosing build-vs-runtime drift. Trigger even when the user does not explicitly say "DOCA version" or "four-way match" — typical implicit phrasings include "program built but does nothing on the wire", "undefined reference to a symbol the docs claim exists", "DOCA_ERROR_NOT_SUPPORTED at runtime", "counter didn't increment", "what does `latest` mean for this tag", or "is my LTS still supported". Refuse and route elsewhere for installing or choosing DOCA packages (doca-setup), per-library API/capability questions (matching library skill), the cross-library DOCA_ERROR_* taxonomy (doca-programming-guide), or the general debug ladder (doca-debug) — those belong to other skills.
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.
license
Apache-2.0
metadata.kind
library

DOCA version

Where to start: This skill is the bundle's single source of truth for DOCA version handling. Open TASKS.md if the user wants to do something with the version (detect / validate / diagnose mismatch); open CAPABILITIES.md 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 TASKS.md ## configure + CAPABILITIES.md ## 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 CAPABILITIES.md ## Version compatibility
  • "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 TASKS.md ## test (which uses the version-matrix.json schema defined in doca-structured-tools-contract with fallback to per-library docs via doca-public-knowledge-map).
  • "Can I run my host package version X against BFB version Y?" — worked example: "host is 3.3.0 LTS, BlueField BFB is 3.1.0". Answered by the routing to the DOCA Compatibility Policy documented in CAPABILITIES.md ## 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 CAPABILITIES.md ## Version compatibility
  • "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 CAPABILITIES.md ## Safety policy
  • "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 TASKS.md ## 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, 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 classConcrete 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 questionany 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 CAPABILITIES.md ## Safety policy.
Build vs runtime driftany 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 planthe 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-linka 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.md ## 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.md ## Capabilities and modes.
  2. State the four-way match rule from CAPABILITIES.md ## 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.
Show full SKILL.md (434 more words)Show less

Universal version-coherence trigger

Whenever ANOTHER overlay (e.g. doca-setup, doca-hardware-safety, doca-container-deployment, doca-bare-metal-deployment) 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), 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:

  • CAPABILITIES.md — 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").
  • TASKS.md — 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.md 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 CAPABILITIES.md.
  3. For step-by-step workflows — configure, build, modify, run, test, debug — see TASKS.md.
  • doca-structured-tools-contract — 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 — 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 — 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 — 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 — the cross-cutting debug ladder. Layer 2 (version mismatch) of that ladder is owned by this skill's ## debug workflow.

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files in skills/doca-version of NVIDIA/skills.

  • SKILL.md
  • BENCHMARK.md
  • CAPABILITIES.md
  • TASKS.md
  • evals/evals.json
  • skill-card.md
  • skill.oms.sig

Open the folder on GitHubat commit 67a13c0

Compare with similar skills

Doca Version next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Doca Version compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Doca Version this skillNVIDIA/skills3.5k—~3kAutomated safety check: PassApache-2.0
Doca VerbsNVIDIA/skills3.5k—~4.9kAutomated safety check: PassApache-2.0
Doca RdmiNVIDIA/skills3.5k—~3.8kAutomated safety check: PassApache-2.0
Doca DebugNVIDIA/skills3.5k—~2.5kAutomated safety check: PassApache-2.0
Doca GpunetioNVIDIA/skills3.5k—~3.7kAutomated safety check: PassApache-2.0
Doca CompressNVIDIA/skills3.5k—~3.8kAutomated safety check: PassApache-2.0

Similar skills

  • Doca Verbs

    NVIDIA/skills

    Official

    A skill your agent uses when the user is dropping below the higher-level DOCA libraries (doca-rdma / doca-eth / doca-rmax) into the raw-verbs escape hatch — managing QP / CQ / PD / MR / SRQ / AH /…

    3.5k GitHub stars~4.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Doca Rdmi

    NVIDIA/skills

    Official

    A skill your agent uses when the user is doing hands-on DOCA RDMI (RDMA Initiator) programming — picking doca-rdmi vs doca-rdma for an accelerator-initiated one-sided RDMA flow, standing up a…

    3.5k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Doca Debug

    NVIDIA/skills

    Official

    A skill your agent uses when the user is debugging any DOCA symptom — a build that won't compile, a link step that can't resolve a doca symbol, a runtime call returning DOCAERROR, a silent service…

    3.5k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Doca Gpunetio

    NVIDIA/skills

    Official

    A skill your agent uses when the user is doing hands-on DOCA GPUNetIO programming — wiring a CUDA kernel on an NVIDIA GPU to a doca-eth queue via docagpuethrxq / docagpuethtxq, standing up the…

    3.5k GitHub stars~3.7k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

  • Doca Compress

    NVIDIA/skills

    Official

    A skill your agent uses for hands-on DOCA Compress programming on a BlueField DPU, ConnectX NIC, or host with DOCA — enabling compress-deflate, decompress-deflate, decompress-lz4-stream, or…

    3.5k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Doca Rdma

    NVIDIA/skills

    Official

    A skill your agent uses when the user is doing hands-on DOCA RDMA programming on a BlueField DPU, ConnectX NIC, or DOCA host — bringing up an RDMA context on a docadev, picking a connection method…

    3.5k GitHub stars~3.5k tokensUpdated today
    Backend & APIsAuto-check passed

More from NVIDIA/skills

All 380 skills in this repo

  • Vss Deploy Detection Tracking 2D

    NVIDIA/skills

    Official

    A skill your agent uses when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice.

    3.5k GitHub starsUsed in 1 repo~4.5k tokens
    Auto-check passed

  • HSB IP Def File Tool

    NVIDIA/skills

    Official

    Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.

    3.5k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Isaac Sim Mission Control Showcase

    NVIDIA/skills

    Official

    Runs and validates an end-to-end Mission Control demo in a locally installed Isaac Sim, with a Nova Carter robot driven through a Python server.

    3.5k GitHub stars~4.8k tokensUpdated today
    Auto-check passed

  • Defect Image Generation with Cosmos AnomalyGen

    NVIDIA/skills

    Official

    Orchestrates defect image generation for PCBA, metal surface and glass inspection with NVIDIA Cosmos AnomalyGen on OSMO, from cold-start Day 0 to real-photo Day 1 labeling.

    3.5k GitHub stars~5k tokensUpdated today
    Auto-check: notes

  • Physical AI Video Augmentation on OSMO

    NVIDIA/skills

    Official

    Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.

    3.5k GitHub stars~4.7k tokensUpdated today
    Auto-check: notes

  • TAO Detection KPI Analysis

    NVIDIA/skills

    Official

    Runs NVIDIA TAO Data Services KPI analysis on object detection results, comparing predictions to ground truth and writing per-class precision, recall and AP to a CSV.

    3.5k GitHub stars~2.7k tokensUpdated today
    Auto-check: notes

Questions about Doca Version

What does Doca Version do?

A skill your agent uses when the user is doing DOCA version handling — detecting the installed release, validating the four-way match across pkg-config doca-common, applications/VERSION, docacaps…. Doca Version is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Use this skill when the user is doing DOCA version handling — detecting the installed release, validating the four-way match across pkg-config doca-common, applications/VERSION, docacaps --version, and bfver/mlnx-release on BlueField, reasoning about NGC container tags, looking up whether a capability is on the installed release, or diagnosing build-vs-runtime drift.

When should I use Doca Version?

Doca Version fits situations like: the user is doing DOCA version handling — detecting the installed release; validating the four-way match across pkg-config doca-common; applications/VERSION; docacaps --version.

How do I install Doca Version in Claude Code?

Run `npx skills add NVIDIA/skills --skill doca-version -a claude-code`. Or copy the skill folder (skills/doca-version in NVIDIA/skills) into .claude/skills/doca-version in your project. Claude Code loads it when a task matches its description.

How do I install Doca Version in Codex?

Run `npx skills add NVIDIA/skills --skill doca-version -a codex`. Or copy the skill folder (skills/doca-version in NVIDIA/skills) into .agents/skills/doca-version in your project. Codex loads it when a task matches its description.

Can I use Doca Version in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/skills --skill doca-version -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doca-version, .gemini/skills/doca-version, .github/skills/doca-version and .opencode/skills/doca-version in your project.

What does Doca Version need to run?

Going by SKILL.md and its folder, Doca Version needs the command-line tools its instructions call (apt). Compatibility (from SKILL.md): 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. .

Does Doca Version access the network?

SKILL.md names 1 domain. As links in the text: docs.nvidia.com. This is read from the text; nothing was executed.

Is Doca Version safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Doca Version use?

Doca Version is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Doca Version use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Doca Version?

Skills that share tags, products or a category with Doca Version: Doca Verbs (NVIDIA/skills, 3.5k stars), Doca Rdmi (NVIDIA/skills, 3.5k stars), Doca Debug (NVIDIA/skills, 3.5k stars) and Doca Gpunetio (NVIDIA/skills, 3.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Doca Version?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,539 GitHub stars. The repository holds 380 skills in this directory. The repository was last updated on October 7, 2026.

Source: NVIDIA/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.