Reproduce Chat States
different-ai/openwork
Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.
A skill your agent uses when the user wants to invoke the read-only docacaps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking…
Install Doca Caps
$ npx skills add NVIDIA/skills --skill doca-caps -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/skills doca-caps --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/doca-caps .claude/skills/doca-caps && rm -rf skills-srcUse ~/.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/
Install the "doca-caps" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/doca-caps into .claude/skills/doca-caps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doca-caps", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NVIDIA/skills/tree/main/skills/doca-capsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NVIDIA/skills --skill doca-caps -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/skills doca-caps --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/doca-caps .agents/skills/doca-caps && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "doca-caps" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/doca-caps into .agents/skills/doca-caps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doca-caps", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/skills --skill doca-caps -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/skills doca-caps --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/doca-caps .cursor/skills/doca-caps && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "doca-caps" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/doca-caps into .cursor/skills/doca-caps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doca-caps", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NVIDIA/skills.git --path skills/doca-caps--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NVIDIA/skills --skill doca-caps -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/skills doca-caps --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/doca-caps .gemini/skills/doca-caps && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "doca-caps" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/doca-caps into .gemini/skills/doca-caps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doca-caps", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NVIDIA/skills doca-capsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NVIDIA/skills --skill doca-caps -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/doca-caps .github/skills/doca-caps && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "doca-caps" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/doca-caps into .github/skills/doca-caps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doca-caps", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/skills --skill doca-caps -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA/skills doca-caps --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/doca-caps .opencode/skills/doca-caps && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "doca-caps" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/doca-caps into .opencode/skills/doca-caps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doca-caps", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
doca-caps- GitHub stars
- 3.5k
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,001 words
- Files
- 8
- Skills in repo
- 380
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when the user wants to invoke the read-only docacaps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking…
- Works in 3 steps: Read this SKILL.md first to confirm the… → **For what doca_caps reports, version… → **For the documented invocations and the…
- The user wants to invoke the read-only docacaps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses
- SKILL.md covers Example questions this skill…, Audience, When to load this skill and What this skill provides, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Doca Caps is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Use this skill when the user wants to invoke the read-only docacaps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking which DOCA libraries are available on the current OS, checking per-device per-library capabilities, scoping output to a specific PCIe address, or capturing a side-effect-free capability snapshot for a debug session or install smoke-test. Trigger even when the user does not explicitly mention "docacaps" or "capabilities print tool"…
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files (for example `BENCHMARK.md`, `CAPABILITIES.md` and `SKILLCARD.yaml`). Compatibility notes: Requires DOCA SDK ≥ 2.6.0 installed at /opt/mellanox/doca on Linux (Ubuntu 22.04/24.04 or RHEL/SLES) with a BlueField DPU or ConnectX NIC; runs identically on…
It sits in Testing & QA, covering QA and bug reports. 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 wants to invoke the read-only docacaps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses
- Listing representor devices
- Asking which DOCA libraries are available on the current OS
- Checking per-device per-library capabilities
Example prompts
- “docacaps”
- “capabilities print tool”
- “what does DOCA actually see on this box”
- “/doca-caps”
Requirements
- Compatibility (from SKILL.md): Requires DOCA SDK ≥ 2.6.0 installed at /opt/mellanox/doca on Linux (Ubuntu 22.04/24.04 or RHEL/SLES) with a BlueField DPU or ConnectX NIC; runs identically on the host or on the BlueField Arm side. Invokes /opt/mellanox/doca/tools/doca_caps and reads `pkg-config doca-common` to confirm the install.
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Read this SKILL.md first to confirm the user's question is in
- **For what doca_caps reports, version availability, error
- **For the documented invocations and the capability-snapshot
What it can do on your machine
Read from SKILL.md and the folder at commit 0e0d506. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Requires DOCA SDK ≥ 2.6.0 installed at /opt/mellanox/doca on Linux (Ubuntu 22.04/24.04 or RHEL/SLES) with a BlueField DPU or ConnectX NIC; runs identically on the host or on the BlueField Arm side. Invokes /opt/mellanox/doca/tools/doca_caps and reads `pkg-config doca-common` to confirm the install.
From compatibility in the SKILL.md frontmatter.
Context cost
Doca Caps loads about 2.4k tokens when it runs. Until then it costs about 256 tokens; SKILL.md has 1,001 words of instructions outside code blocks.
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 0e0d506, republished under its Apache-2.0 licence (© NVIDIA). 1,001 words, ~2,424 tokens.
Download SKILL.mdSave it as
.claude/skills/doca-caps/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- doca-caps
- description
- Use this skill when the user wants to invoke the read-only doca_caps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking which DOCA libraries are available on the current OS, checking per-device per-library capabilities, scoping output to a specific PCIe address, or capturing a side-effect-free capability snapshot for a debug session or install smoke-test. Trigger even when the user does not explicitly mention "doca_caps" or "capabilities print tool" — typical implicit phrasings include "what does DOCA actually see on this box", "is my BlueField PF visible to DOCA", "is Flow available on my RHEL host", "enumerate VF representors for pf0", "doca_caps: command not found", or "empty output for RDMA, is the tool broken". Refuse and route elsewhere for DOCA installation, library-internal capability matrices (Flow pipe creation, RDMA verbs features), streaming telemetry / DTS, or modifying the shipped binary — those belong to other skills.
- compatibility
- Requires DOCA SDK ≥ 2.6.0 installed at /opt/mellanox/doca on Linux (Ubuntu 22.04/24.04 or RHEL/SLES) with a BlueField DPU or ConnectX NIC; runs identically on the host or on the BlueField Arm side. Invokes /opt/mellanox/doca/tools/doca_caps and reads `pkg-config doca-common` to confirm the install.
- license
- Apache-2.0
- metadata.kind
- tool
DOCA Capabilities Print Tool (doca_caps)
Where to start: This is a tool skill for invoking doca_caps,
a side-effect-free CLI. Open TASKS.md and start at
## run for the documented invocations, or
## test when using doca_caps as an install
smoke-test. Open CAPABILITIES.md when the
question is what kinds of capability families doca_caps reports.
If DOCA is not installed yet, route to
doca-setup first.
Example questions this skill answers well
The CLASSES of doca_caps 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.
- "What DOCA devices does this host see?" — worked example: "is
my BlueField PF visible to DOCA". Answered by the device
enumeration in
CAPABILITIES.md ## Capabilities and modes- the
--list-devsinvocation inTASKS.md ## run.
- the
- "Which DOCA libraries are available on this OS?" — worked
example: "is Flow available on my RHEL host". Answered by the
library-availability surface in
CAPABILITIES.md ## Capabilities and modes- the library-listing invocation in
TASKS.md ## run.
- the library-listing invocation in
- "Does this device support library X capability Y?" — worked
example: "does this device support Flow hairpin?". Answered by
the per-device per-library capability matrix in
CAPABILITIES.md ## Capabilities and modes- the
--pci-addr-scoped invocation inTASKS.md ## run.
- the
- "What representors are visible to DOCA?" — worked example:
"enumerate VF representors for pf0". Answered by the representor
enumeration in
CAPABILITIES.md ## Capabilities and modes- the
--list-rep-devsinvocation inTASKS.md ## run.
- the
- "I want a snapshot of state to attach to my debug session." —
worked example: "save device + library + capability output to a
file". Answered by the snapshot workflow in
TASKS.md ## testand consumed bydoca-debug ## teststep 3 (read-only triple) anddoca-programming-guide ## debug. - "
doca_capsreturned nothing for capability Y — what does that mean?" — worked example: "empty output for RDMA". Answered by the empty-output interpretation rules inTASKS.md ## debug+CAPABILITIES.md ## Error taxonomy.
Audience
This skill serves external operators, developers, and AI agents who need a side-effect-free way to ask "what does DOCA see on this host?" before doing anything that changes state. Concretely:
- An external developer who installed DOCA (or is using the public NGC
DOCA container per
doca-setup ## no-install) and wants to confirm the install can see hardware before writing code. - A platform operator deploying a DOCA service who wants a documented, read-only snapshot of which DOCA libraries this host actually supports and which capabilities each DOCA device offers.
- An AI agent producing a capability snapshot artifact during the
documented setup or programming-guide debug procedures (it's listed
as the canonical first step in
doca-setup ## testanddoca-programming-guide ## debug).
It is not for users debugging doca_caps itself, and not a
substitute for the live public Capabilities Print Tool guide.
doca_caps is shipped as a tool (a single CLI binary), 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 — even when individual verbs
collapse to a routing stub for a shipped read-only binary.
When to load this skill
Load this skill when the user is — or the agent needs to — invoke
doca_caps on a real host with DOCA installed (or inside the public
NGC DOCA container). Concretely:
- Running
doca_caps --list-devsto enumerate DOCA devices. - Running
doca_caps --list-rep-devsto enumerate representor devices. - Scoping output to a specific PCIe address with
--pci-addr. - Listing the DOCA libraries the install reports as available on the current OS.
- Listing the available DOCA logger names.
- Capturing a documented, side-effect-free capability snapshot as
prerequisite evidence for later
## debugworkflows.
Do not load this skill for general DOCA orientation, library API
work, or installation. For those, use
doca-public-knowledge-map,
the matching libs/<library> skill, or
doca-setup.
Show full SKILL.md (395 more words)Show less
What this skill provides
This is a thin loader. Substantive material lives in two companion files:
CAPABILITIES.md— whatdoca_capsreports (the five documented capability families: devices, representors, libraries, library capabilities, loggers), version availability and execution environment, the tool's narrow error surface, its observability role inside other skills' workflows, and its read-only safety posture.TASKS.md— step-by-step workflows for the in-scope task verbs:configure(route to install),build(route to install),modify(refuse),run(the documented invocations),test(capability snapshot as install smoke-test),debug(what to do when the tool reports nothing or fails), plus aDeferred task verbsblock routing out-of-scope questions.
The skill assumes a host where DOCA is already installed (or the public
NGC DOCA container is running) and the operator has whatever
permissions the public guide requires for doca_caps to enumerate
devices on their platform.
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:
- Pre-baked example output. Output is install- and hardware-specific. A captured example pinned to one platform and one DOCA version misleads operators on a different platform / version.
- Wrappers, parsers, or scripts in any language that consume
doca_capsoutput. The output format is documented; if a user wants to script against it, the right answer is "read the live guide, write the parser against your installed version". - A
samples/orreference/subtree. This is a thin loader for a documented CLI; substantive material lives on the public page and in--help.
Loading order
- Read this
SKILL.mdfirst to confirm the user's question is in scope (the user actually wants to invokedoca_caps, not learn about DOCA in general). - For what
doca_capsreports, version availability, error surface, and safety posture, see CAPABILITIES.md. - For the documented invocations and the capability-snapshot
workflow —
configure,build,modify,run,test,debug— see TASKS.md.
Related skills
doca-public-knowledge-map— routing to the public Capabilities Print Tool guide and the rest of the public DOCA documentation set.doca-setup— env preparation, install verification (doca_capsis the canonical first step there), and the I have no install yet path with the public NGC DOCA container.doca-programming-guide— cross-library programming patterns, including the## debugprocedure where the saveddoca_capssnapshot is consumed.- The matching
libs/<library>skill — for fine-grained, library-specific capability questions that go beyond whatdoca_capsexposes.
© 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 7 other files in skills/doca-caps of NVIDIA/skills.
- SKILL.md
- BENCHMARK.md
- CAPABILITIES.md
- SKILLCARD.yaml
- TASKS.md
- evals/evals.json
- skill-card.md
- skill.oms.sig
Open the folder on GitHubat commit 0e0d506
Compare with similar skills
Doca Caps 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Doca Caps this skillNVIDIA/skills | 3.5k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Reproduce Chat Statesdifferent-ai/openwork | 24k | — | ~673 | Automated safety check: Pass | Custom licence | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Minimal Run And Auditlllllllama/RigorPilot-Skills | 497 | 2 repos | ~691 | Automated safety check: Pass | MIT | |
| Moav E2EMotherofallVPNs/MoaV | 448 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Creating A Coral TaskHuman-Agent-Society/CORAL | 1k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Minimal Run And Audit
lllllllama/RigorPilot-Skills
Rigor Run skill for README-first deep learning repo reproduction.
Moav E2E
MotherofallVPNs/MoaV
Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.
Creating A Coral Task
Human-Agent-Society/CORAL
Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…
Launch Rl
marin-community/marin
Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main.
More from NVIDIA/skills
All 380 skills in this repo- Official
Vss Deploy Detection Tracking 2D
NVIDIA/skills
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.
- Official
HSB IP Def File Tool
NVIDIA/skills
Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.
- Official
Isaac Sim Mission Control Showcase
NVIDIA/skills
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.
- Official
Defect Image Generation with Cosmos AnomalyGen
NVIDIA/skills
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.
- Official
Physical AI Video Augmentation on OSMO
NVIDIA/skills
Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.
- Official
TAO Detection KPI Analysis
NVIDIA/skills
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.
Related
Categories
Questions about Doca Caps
What does Doca Caps do?
A skill your agent uses when the user wants to invoke the read-only docacaps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking…. Doca Caps is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Use this skill when the user wants to invoke the read-only docacaps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking which DOCA libraries are available on the current OS, checking per-device per-library capabilities, scoping output to a specific PCIe address, or capturing a side-effect-free capability snapshot for a debug session or install smoke-test.
When should I use Doca Caps?
Doca Caps fits situations like: the user wants to invoke the read-only docacaps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses; listing representor devices; asking which DOCA libraries are available on the current OS; checking per-device per-library capabilities.
How do I install Doca Caps in Claude Code?
Run `npx skills add NVIDIA/skills --skill doca-caps -a claude-code`. Or copy the skill folder (skills/doca-caps in NVIDIA/skills) into .claude/skills/doca-caps in your project. Claude Code loads it when a task matches its description.
How do I install Doca Caps in Codex?
Run `npx skills add NVIDIA/skills --skill doca-caps -a codex`. Or copy the skill folder (skills/doca-caps in NVIDIA/skills) into .agents/skills/doca-caps in your project. Codex loads it when a task matches its description.
Can I use Doca Caps 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-caps -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-caps, .gemini/skills/doca-caps, .github/skills/doca-caps and .opencode/skills/doca-caps in your project.
What does Doca Caps need to run?
SKILL.md names no scripts, command-line tools or credentials: Doca Caps is instructions for the agent only. Compatibility (from SKILL.md): Requires DOCA SDK ≥ 2.6.0 installed at /opt/mellanox/doca on Linux (Ubuntu 22.04/24.04 or RHEL/SLES) with a BlueField DPU or ConnectX NIC; runs identically on the host or on the BlueField Arm side. Invokes /opt/mellanox/doca/tools/doca_caps and reads `pkg-config doca-common` to confirm the install. .
Does Doca Caps access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Doca Caps 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 Caps use?
Doca Caps 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 Caps use?
About 2.4k tokens (SKILL.md is roughly 9.7k 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 Caps?
Skills that share tags, products or a category with Doca Caps: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Minimal Run And Audit (lllllllama/RigorPilot-Skills, 497 stars) and Moav E2E (MotherofallVPNs/MoaV, 448 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Doca Caps?
NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,534 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.