Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-rmax
Use this skill when the user is doing hands-on DOCA Rivermax work on a BlueField DPU or ConnectX host — standing up `doca_rmax_in_stream` (receive) sessions for timing-precise media-over-IP (SMPTE ST 2110 video/audio, market data, scientific feeds), confirming the Rivermax SDK + license precondition before any DOCA-side code, running `doca_rmax_get_*_supported` capability queries, pairing with `doca-eth` queues and `doca-flow` steering, or debugging `DOCA_ERROR_*` from a Rivermax call. Trigger e
Passed 19 of 22 test cases with the skill, and 9 of 22 without it.
and 12 more in the full report
11 fixed9 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am writing a C application to ingest SMPTE ST 2110-20 video streams on my BlueField DPU using DOCA's media acceleration library. Can you provide a step-by-step guide explaining the mandatory host requirements, initialization lifecycle for an input stream context, and how to verify hardware feature support before starting the stream?
| Checked | Without skill | With skill |
|---|---|---|
| States that the NVIDIA Rivermax SDK and a valid Rivermax license must be separately installed on the host as a mandatory precondition. | Missed | Passed |
| Uses doca_rmax_in_stream_create to allocate the receive input stream context. | Missed | Passed |
| Specifies verifying hardware support via doca_rmax_get_*_supported capability discovery queries before context start. | Missed | Passed |
The instructions your model reads when the skill loads.
Where to start: This skill assumes DOCA is already installed,
AND that the NVIDIA Rivermax SDK is separately installed with a
valid Rivermax license present on the host. The agent's FIRST
action on any Rivermax question is to confirm both — without
Rivermax SDK + license, doca-rmax cannot function regardless
of how clean the DOCA-side code is, and this is the #1 first-app
confusion (DOCA does not bundle Rivermax; it wraps it). Open
TASKS.md if the user wants to do something
(configure / build / modify / run / test / debug); open
CAPABILITIES.md when the question is what
can DOCA Rivermax express on this version + this Rivermax
install. If the user has not installed DOCA yet, route to
doca-setup first; for the Rivermax
SDK + license install itself, route to the public DOCA Rivermax
guide (slug DOCA-Rivermax) via
doca-public-knowledge-map.
If the user is asking "how do I get packets to land on my
Rivermax input stream at all", the answer is layered:
doca-rmax is the Rivermax integration surface,
doca-eth is the queue surface that
carries the packets, and doca-flow
is the steering surface that directs them.
The CLASSES of DOCA Rivermax questions this skill is built to answer, each with one worked example. The agent should treat the class as the load-bearing piece — the worked example is a single instance.
doca-rmax on this host?" — worked
example: "the public docs mention doca-rmax; is it
usable without doing anything else?". Answered by the
Rivermax-SDK + license precondition rule in
CAPABILITIES.md ## Safety policy
TASKS.md ## configure step 1, which
routes the install-side question to the public Rivermax guidetest cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.