doca-public-knowledge-map

Routes NVIDIA DOCA questions to authoritative documentation, install paths, and samples.

3.2k|370|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/NVIDIA/skills --skill doca-public-knowledge-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doca-public-knowledge-map
Source: https://github.com/NVIDIA/skills/tree/main/skills/doca-public-knowledge-map
Command: npx skills add https://github.com/NVIDIA/skills --skill doca-public-knowledge-map

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Finding the right NVIDIA DOCA documentation page, installed library version, sample location, or replacement for a broken doc URL is difficult without access to the DOCA source tree. This Skill acts as a routing table that maps user questions to the authoritative docs.nvidia.com page, on-disk path under /opt/mellanox/doca, or public GitHub source.

Core Features & Use Cases

  • Documentation Routing: Maps user intents (install, build, API reference, release notes, forum) to the correct docs.nvidia.com entry point, including umbrella pages for libraries, services, and tools.
  • Install Layout Decoding: Explains the layout of an installed DOCA package under /opt/mellanox/doca, how to identify installed libraries and versions via pkg-config, and where samples live on disk and on GitHub.
  • URL Recovery and Scope Boundaries: Recovers renamed or 404'd doc URLs (e.g., the Comm Channel to Comch rename) and routes out-of-scope requests to sibling skills like doca-setup, doca-programming-guide, and doca-hardware-safety.
  • Use Case: A developer asks "which DOCA libraries do I have installed and at what version?" The agent loads this Skill, follows the version-detection routing, and answers with concrete pkg-config commands and paths instead of guessing.

Quick Start

Ask your agent where to find authoritative documentation for a DOCA library, which DOCA version is installed, or where a specific DOCA sample lives on disk or GitHub.

Frequently Asked Questions about doca-public-knowledge-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the right NVIDIA DOCA documentation page?

Use the routing tables that map each user intent to a docs.nvidia.com entry point. Start with the DOCA Libraries, Services, or Tools umbrella pages when the specific library or service is not listed, and never guess a URL.

How do I check which DOCA libraries are installed and their versions?

Inspect the installed package layout under /opt/mellanox/doca and use pkg-config commands such as pkg-config --list-all to enumerate installed DOCA modules. The skill's version-detection sections describe where version information lives on disk.

Where are DOCA samples located on disk and on GitHub?

Installed samples live under /opt/mellanox/doca/samples/doca_<library>/ on a real DOCA install. Their public source is mirrored in the NVIDIA-DOCA/doca-samples GitHub repository, and each library's programming guide documents its shipped samples.

What do I do when a DOCA documentation URL returns 404?

Apply the URL-rename rules in the skill, such as the Comm Channel to Comch rename in DOCA 2.5, and consult the URL audit section. Archived v1.x/v2.x sample overview pages are gone, so route to per-library sample sections instead.

When should I not use the DOCA knowledge map skill?

Avoid it for hands-on programming patterns, environment setup, install verification, API tutorials, or hardware and firmware changes. Those tasks belong to doca-programming-guide, doca-setup, the per-library skills, and doca-hardware-safety respectively.

Does this skill require a DOCA installation to use?

No DOCA install is required to read the routing content, since it is a documentation map. However, the validation steps that inspect installed libraries and paths require a live DOCA install at /opt/mellanox/doca.