New: 97,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 Public Knowledge Map

by NVIDIA in NVIDIA/skills

A skill your agent uses when the user needs to locate authoritative information about NVIDIA DOCA without access to the source tree — finding the right docs.nvidia.com page for a…

OfficialApache-2.0Auto-check passedDevelopment

Install Doca Public Knowledge Map

skills CLI
$ npx skills add NVIDIA/skills --skill doca-public-knowledge-map -a claude-code

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

GitHub CLI
$ gh skill install NVIDIA/skills doca-public-knowledge-map --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-public-knowledge-map .claude/skills/doca-public-knowledge-map && 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-public-knowledge-map
GitHub stars
3.5k
Token cost
~3.3k tokens
SKILL.md length
1,490 words
Files
6 (incl. references)
Skills in repo
380
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when the user needs to locate authoritative information about NVIDIA DOCA without access to the source tree — finding the right docs.nvidia.com page for a…

  • Identifying which DOCA libraries are installed and at what version
  • SKILL.md covers When to load this skill, First-contact discovery — the…, Topic to "where to look first"… and What this skill deliberately…, plus 12 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Locating a sample on disk

What it does

Doca Public Knowledge Map is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Use this skill when the user needs to locate authoritative information about NVIDIA DOCA without access to the source tree — finding the right docs.nvidia.com page for a library/service/tool, identifying which DOCA libraries are installed and at what version, locating a sample on disk or its public GitHub source, decoding an on-disk path under /opt/mellanox/doca, or recovering from a 404'd or renamed doc URL. Trigger even when the user does not explicitly mention 'DOCA' or 'docs.nvidia.com' — typical implicit…

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `BENCHMARK.md`, `evals/evals.json` and `references/map.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 this skill require a live…

It sits in Development. It works with NVIDIA AI Platform, GitHub and Linux. 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

  • Identifying which DOCA libraries are installed and at what version
  • Locating a sample on disk
  • Its public GitHub source
  • Decoding an on-disk path under /opt/mellanox/doca

Example prompts

  • “docs.nvidia.com”
  • “where can I read about this library”
  • “which version do I have installed”
  • “/doca-public-knowledge-map”

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 this skill require a live DOCA install at /opt/mellanox/doca.

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

    No DOCA install required to read this skill (it is an overlay loaded against any DOCA artifact skill); the validation steps within this skill require a live DOCA install at /opt/mellanox/doca.

    From compatibility in the SKILL.md frontmatter.

Context cost

Doca Public Knowledge Map loads about 3.3k tokens when it runs, and up to ~25k if it reads all its reference files. Until then it costs about 260 tokens; SKILL.md has 1,490 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~260
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~25k

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,490 words, ~3,257 tokens.

Download SKILL.mdSave it as .claude/skills/doca-public-knowledge-map/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
doca-public-knowledge-map
description
Use this skill when the user needs to locate authoritative information about NVIDIA DOCA without access to the source tree — finding the right docs.nvidia.com page for a library/service/tool, identifying which DOCA libraries are installed and at what version, locating a sample on disk or its public GitHub source, decoding an on-disk path under /opt/mellanox/doca, or recovering from a 404'd or renamed doc URL. Trigger even when the user does not explicitly mention 'DOCA' or 'docs.nvidia.com' — typical implicit phrasings include 'where can I read about this library', 'which version do I have installed', 'where is the sample for X', 'this NVIDIA URL is broken what is the new one', 'what is in /opt/mellanox/doca', or 'where can I ask NVIDIA about this'. Refuse and route elsewhere for hands-on programming patterns, env prep and install verification, library API tutorials, or hardware/firmware mutation — those belong to doca-programming-guide, doca-setup, the per-library skills, and doca-hardware-safety.
compatibility
No DOCA install required to read this skill (it is an overlay loaded against any DOCA artifact skill); the validation steps within this skill require a live DOCA install at /opt/mellanox/doca.
license
Apache-2.0 AND CC-BY-4.0
metadata.kind
knowledge

DOCA Public Knowledge Map

Where to start: Reach for this skill whenever the question is "where does the authoritative answer live?" — a docs page, the on-disk install layout, a sample, or an NGC catalog entry. Read ## Public documentation entry points first; then jump to the routing-table section that matches the user's intent.

When to load this skill

Load this skill whenever the user asks anything about NVIDIA DOCA where the agent needs to locate authoritative information without access to the DOCA source tree. That includes documentation-routing questions about installing DOCA, building a sample, learning a DOCA library (Flow, DPA, Comm Channel, GPUNetIO, …), debugging an error, finding an API or error reference, finding a sample, release notes, or the developer forum. This skill locates the authoritative answer; hands-on installation, building, tutorials, and debugging route to the workflow-owning skills named in the frontmatter and ## Related skills.

This skill is intentionally a routing table, not a tutorial. Pick the entry that matches the user's intent, fetch the URL or inspect the local install path, and only then answer.

First-contact discovery — the four questions to ask before any drill-down

When a user opens with an open-ended orientation question ("I'm new with DOCA, how do I start?", "can you guide me?", "what's the easiest way to try DOCA?"), the agent does not have enough information yet to pick a path. Asking these four questions before drilling avoids wasted recommendations that the user cannot actually execute on their setup. Ask them as a single short message; do not interrogate one-at-a-time.

QuestionWhy it mattersWhat it routes
1. What OS are you on? macOS, Windows, Linux laptop, cloud VM, lab Linux box, BlueField OS itself?DOCA installs natively only on supported Linux distributions; macOS / Windows users cannot install it at all.Picks between the four DOCA acquisition paths in doca-setup ## no-install. macOS / Windows / no-Linux → Path 0 (NGC container). Supported Linux → Path A or B per the Installation Guide.
2. What hardware do you have? No NVIDIA hardware, ConnectX SmartNIC, BlueField as a SmartNIC in a host, BlueField as a standalone DPU, not sure?Real-traffic runtime needs a real NIC; build / read / learn does not. The user's hardware decides which DOCA libraries are even relevant.Picks the runtime story (container is build-only without hardware). Filters which libraries make sense to learn (Flow needs a real port to do anything visible; Comch needs a host ↔ DPU pair).
3. What's your goal? Just exploring, building a small first app on a specific library (Flow / RDMA / Comch / Telemetry / GPUNetIO / DPA / …), running an existing reference application, operating a service (DMS / DTS / BlueMan / Firefly), or something else?The bundle's first-app workflow (doca-programming-guide ## modify) starts from a shipped C sample and edits down. The right sample depends on the library the user is targeting.Picks which library skill (if any) to load next. If the user does not yet know which library — that itself is a routing answer (see the Library- and module-specific guides table above and let the user pick).
4. Which language do you plan to write the program in? C / C++, Rust, Go, Python, other?DOCA's public surface is a C ABI. Non-C consumers go through FFI / language bindings (doca-programming-guide CAPABILITIES.md ## Capabilities and modes and the per-library skill). The C samples are the reference even when the user's language is not C.Picks whether the agent's first-app guidance is direct C build or FFI / bindings against the C ABI. Does not change which sample the agent points at first.

The four-question gate applies when an open-ended orientation, install, build, or run recommendation depends on the user's environment. For that class, never recommend a specific install path, container tag, or runnable sample without first having the answers to questions 1–3 (question 4 is needed for the first-app workflow but not for orientation itself). Pure documentation lookups — a URL, API reference, sample location, version reference, or stale-link recovery — skip this gate and route directly. If the user cannot or will not answer a required question, state which environment-dependent recommendation cannot be made, give only the safe version-agnostic umbrella documentation route, and do not guess the missing value. Volunteering specific commands before this is the single most common failure mode for DOCA orientation.

If the user has already volunteered some of the information in their first message, mark those questions answered and only ask the rest. Do not re-ask what the user has already told you.

Show full SKILL.md (757 more words)Show less

Topic to "where to look first" routing table

When the user asks something, route as follows:

User intentFirst place to look
"How do I install DOCA?"Installation Guide + Downloads page (Public documentation entry points).
"How do I start with DOCA — what's the very first thing?"Developer Quick Start Guide if the user has BlueField + host hardware; otherwise doca-setup ## no-install Path 0 (NGC container). Use the four questions in First-contact discovery to pick.
"Do I need a BlueField? A SmartNIC? Or just DOCA-Host?"Overview page (doca-overview/index.html) plus the Installation Guide's DOCA installation profiles section. The bundle does not pick the hardware for the user — these two pages do.
"Which package gives me library X?"Installation Guide section on package matrix; then verify on the user's system with pkg-config --list-all.
"Show me a sample that uses library X."/opt/mellanox/doca/samples/doca_<X>/ if installed; otherwise the per-library guide on docs.nvidia.com/doca/sdk/ (each library guide documents the samples shipped with it).
"How do I build a DOCA sample?"Library guide + the sample's own meson.build inside /opt/mellanox/doca/samples/....
"What is the API for X?"Library guide; confirm by inspecting headers under $(pkg-config --variable=includedir doca-common) (commonly /opt/mellanox/doca/include/ on DOCA 3.3+; /opt/mellanox/doca/infrastructure/include/ on legacy / split-profile installs).
"Why does my build fail with pkg-config not finding doca-...?""Layout of an installed DOCA package" (PKG_CONFIG_PATH), then load doca-setup for environment preparation and debugging; do not silently mutate the environment.
"What is the latest version / what changed?"Release Notes.
"Is there a newer DOCA — should I upgrade / downgrade / roll back?"doca-upgrade for the detect → report → ASK → guided-upgrade discipline (never auto-upgrade); Release Notes for what the target release contains.
"Is the component I depend on being sunset / deprecated?"Release Notes (lifecycle / deprecation notices), reached via the doca-upgrade sunset-awareness check; do not assert deprecation from memory.
"What does the DOCA version number mean? Is LTS still supported?"Compatibility Policy (Public documentation entry points table).
"How do I run DOCA on Kubernetes / provision a DPU?"DOCA Platform Framework on GitHub.
"I have a behavior I cannot explain."Release Notes (known issues) first; then the DOCA Developer Forum. Never go to the forum first.
Any intent not matched aboveStart at the DOCA SDK index and the Libraries / Services / Tools umbrella page in references/map.md. If the authoritative route remains unresolved, say so and use the Developer Forum; do not invent a URL or component name.

What this skill deliberately does not cover

This file is intentionally a map, not a tutorial. It does not contain:

  • DOCA library tutorials (those live in the per-library guides).
  • API reference (lives in headers and the per-library guides).
  • Build-system deep-dives (lives in the Installation Guide and the sample meson.build files).
  • Performance tuning, driver-level setup, OFED interaction (lives in the Installation Guide and library-specific guides).

When the agent needs those, it should fetch the matching public document or read the matching installed file. As more focused skills are added, they should appear in SKILLS.md and link back here for the "where to look" lookups.

For env preparation — install verification, build environment (pkg-config, headers, hugepages, devlink), env-class debugging, and the I have no install yet path with the public NGC DOCA container (nvcr.io/nvidia/doca/doca) as the universal Stage-1 fallback for any user on macOS, Windows, or Linux without DOCA — load doca-setup. That skill stops at "the install is healthy and the env is ready".

For general DOCA programming patterns shared across every library — the canonical pkg-config doca-<library> build pattern (C/C++ direct or non-C via FFI), the universal derive a custom first app from a shipped sample workflow, the universal lifecycle (cfg-create → init → start → use → stop → destroy), the cross-library DOCA_ERROR_* taxonomy, and the program-side debug order — load doca-programming-guide. Each library skill extends its ## modify (first-app derivation) with library-specific overrides.

For DOCA Flow internals — port and representor setup, pipe creation, match/action specifications, pipe validation before hardware programming, Flow counters and traces, Flow version compatibility, and debugging DOCA_ERROR_* failures from the Flow API — load doca-flow. That skill assumes this one is available for shared documentation routing and install-layout lookups, doca-setup for environment preparation, and doca-programming-guide for the cross-library programming patterns it layers on top of.

Example questions this skill answers well

See references/map.md.

Library- and module-specific guides

See references/map.md.

DOCA services

See references/map.md.

DOCA tools

See references/map.md.

Externally-productized DOCA software — not in this bundle, but here is where to route

See references/map.md.

Public source code: GitHub

See references/map.md.

Layout of an installed DOCA package

See references/map.md.

Where to find the version

See references/map.md.

URL audit

See references/map.md.

Ground rules for any agent using this skill

See references/map.md.

Public documentation entry points

See references/map.md.

© 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 5 other files (references) in skills/doca-public-knowledge-map of NVIDIA/skills.

  • SKILL.md
  • BENCHMARK.md
  • evals/evals.json
  • references/map.md
  • skill-card.md
  • skill.oms.sig

Open the folder on GitHubat commit 0e0d506

Compare with similar skills

Doca Public Knowledge Map 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 Public Knowledge Map compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Doca Public Knowledge Map this skillNVIDIA/skills3.5k—~3.3kAutomated safety check: PassApache-2.0
Update .NET OS Packagesdotnet/core22k—~2.3kAutomated safety check: PassMIT
Cut Releasejfernandez/bpftop2.7k—~2kAutomated safety check: PassApache-2.0
Prepare Releaseneetly/figma-agent-linux394—~833Automated safety check: PassMIT
GitHub Activity Analyzerchangkun/dotfiles151—~1.6kAutomated safety check: PassMIT
LangBot Environment Setuplangbot-app/LangBot18k—~496Automated safety check: NotesApache-2.0

Similar skills

  • Update .NET OS Packages

    dotnet/core

    Official

    Audits and updates os-packages.json files listing the Linux packages each .NET release needs per distro, then regenerates the Markdown from the JSON.

    22k GitHub stars~2.3k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Cut Release

    jfernandez/bpftop

    Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.

    2.7k GitHub stars~2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Prepare Release

    neetly/figma-agent-linux

    Prepare a new figma-agent-linux release by updating the package version, changelog, and release links, then validating the changes.

    394 GitHub stars~833 tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • GitHub Activity Analyzer

    changkun/dotfiles

    Comprehensive GitHub contribution analysis for any time period.

    151 GitHub stars~1.6k tokensUpdated 10 days ago
    DevelopmentAuto-check passed

  • LangBot Environment Setup

    langbot-app/LangBot

    Prepares a LangBot development and testing environment for an agent, covering service startup, proxy settings and browser access through Computer Use or Playwright MCP.

    18k GitHub stars~496 tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Setup

    Prorise-cool/Claude-Code-Multi-Agent

    Complete guide to installing Git and performing basic configuration across all platforms (Windows, macOS, Linux, WSL).

    305 GitHub stars~3k tokensUpdated 22 days ago
    DevelopmentAuto-check: notes

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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    Auto-check: notes

Works with

Categories

Questions about Doca Public Knowledge Map

What does Doca Public Knowledge Map do?

A skill your agent uses when the user needs to locate authoritative information about NVIDIA DOCA without access to the source tree — finding the right docs.nvidia.com page for a…. Doca Public Knowledge Map is an agent skill from NVIDIA/skills, published by the product's own GitHub organization.com page for a library/service/tool, identifying which DOCA libraries are installed and at what version, locating a sample on disk or its public GitHub source, decoding an on-disk path under /opt/mellanox/doca, or recovering from a 404'd or renamed doc URL.

When should I use Doca Public Knowledge Map?

Doca Public Knowledge Map fits situations like: identifying which DOCA libraries are installed and at what version; locating a sample on disk; its public GitHub source; decoding an on-disk path under /opt/mellanox/doca.

How do I install Doca Public Knowledge Map in Claude Code?

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

How do I install Doca Public Knowledge Map in Codex?

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

Can I use Doca Public Knowledge Map 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-public-knowledge-map -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-public-knowledge-map, .gemini/skills/doca-public-knowledge-map, .github/skills/doca-public-knowledge-map and .opencode/skills/doca-public-knowledge-map in your project.

What does Doca Public Knowledge Map need to run?

SKILL.md names no scripts, command-line tools or credentials: Doca Public Knowledge Map is instructions for the agent only. 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 this skill require a live DOCA install at /opt/mellanox/doca. .

Does Doca Public Knowledge Map 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 Public Knowledge Map 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 Public Knowledge Map use?

Doca Public Knowledge Map 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 Public Knowledge Map use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 21k tokens, read only when the agent opens those files.

What are the alternatives to Doca Public Knowledge Map?

Skills that share tags, products or a category with Doca Public Knowledge Map: Update .NET OS Packages (dotnet/core, 22k stars), Cut Release (jfernandez/bpftop, 2.7k stars), Prepare Release (neetly/figma-agent-linux, 394 stars) and GitHub Activity Analyzer (changkun/dotfiles, 151 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Doca Public Knowledge Map?

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.