Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-public-knowledge-map
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' — ty
Passed 16 of 22 test cases with the skill, and 11 of 22 without it.
and 3 more in the full report
5 fixed11 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to build a custom application on NVIDIA DOCA. I am running Ubuntu 22.04 LTS on a host equipped with a BlueField-2 DPU. What should I do first? Ask any remaining details you need.
| Checked | Without skill | With skill |
|---|---|---|
| Omit questions about OS and hardware since the user already stated Ubuntu 22.04 and BlueField-2. | Passed | Passed |
| Ask the missing orientation questions about project goal and target programming language. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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.
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.
| Question | Why it matters | What 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,
test cases passed, vs 11 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.