Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-setup
Use this skill when the user is dealing with the DOCA environment around their workload — verifying an install is healthy, preparing the build env (pkg-config, headers, LD_LIBRARY_PATH, hugepages, devlink, representors), debugging env-class failures, deciding container-vs-bare-metal deployment shape, or reaching a DOCA install from a host that doesn't have one yet via the NGC DOCA container Stage-1 fallback. Trigger even when the user does not explicitly mention "DOCA setup" — typical implicit p
Passed 18 of 21 test cases with the skill, and 10 of 21 without it.
and 8 more in the full report
9 fixed10 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are setting up hugepages on a host system for DOCA memory allocation. We plan to mount hugetlbfs at /mnt/huge. What sysctl parameter or command allocates 2MB hugepages at runtime?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies modifying vm.nr_hugepages via sysctl or sysfs hugepages parameters. | Passed | Passed |
| Requires verifying hugetlbfs mount status. | Missed | Passed |
The instructions your model reads when the skill loads.
Where to start: If the user's question is deployment-shaped
("how do I deploy", "how do I run my DOCA workload", "I just got a
BlueField, what now", "my code is built, what next"), walk
TASKS.md ## recognize first. It is the
bundle's front-door: it detects the system shape (host x86 / BlueField
Arm bare-metal / DPU-only / fresh laptop), asks the developer the
minimal set of questions needed to disambiguate, and routes to the
correct downstream skill — the container deployment path
(doca-container-deployment),
the bare-metal hardware deployment path
(doca-bare-metal-deployment),
or the no-hardware fallback
(TASKS.md ## no-install). The wrong failure
mode is to silently steer every developer onto containers because the
agent loaded that skill first; ## recognize exists to prevent that.
If the user does not have DOCA installed yet and the request is not
deployment-shaped, jump straight to
TASKS.md ## no-install for the NGC container
path. Deployment-shaped requests still enter ## recognize first,
which routes fresh-laptop cases to ## no-install. Otherwise read
## When to load this skill to confirm the
question is env-class, then route to the section below that matches the
user's intent.
The CLASSES this skill is built to handle, each with one worked example. The skill must answer the class; the worked example is illustrative.
TASKS.md ## recognize, which detects the
system shape, asks the minimum residual question, and routes to
either the container or the bare-metal deployment skill.test cases passed, vs 10 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.