Agent skill · research science · nvidia
doca-public-knowledge-map
Use this skill to locate authoritative NVIDIA DOCA information without the source tree: the docs.nvidia.com page for a library/service/tool, which DOCA libraries are installed and at what version, a sample on disk or GitHub, a path under /opt/mellanox/doca, or a 404'd/renamed doc URL. Activate on implicit phrasing only when the conversation already names DOCA, BlueField, ConnectX, or /opt/mellanox. Do not activate for generic 'which version is installed' or 'where is the sample' questions with none of that context. Refuse and route elsewhere for hands-on programming, env prep, API tutorials, or hardware/firmware mutation — those belong to doca-programming-guide, doca-setup, the per-library skills, and doca-hardware-safety.
Why this skill is useful
Provides domain-specific knowledge about locating NVIDIA DOCA documentation and resources that the AI wouldn't reliably generate on its own.
What it needs
About 9k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
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. How to use this skill. Read this file, then search the companion file for the ## <name> heading the question needs and read that whole section. Answer completely from it, quoting only its symbols and commands. Do not browse docs; use the entry points in doca-public-knowledge-map. Give environment checks as commands for the user's DOCA host. For out-of-scope requests, name the skill that owns them and stop. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/doca-public-knowledge-map