Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-argp
Use this skill for hands-on DOCA Arg Parser CLI work on a shipped sample or new DOCA-using app — adding / removing / renaming flags; wiring `doca_argp_init` → register params → `doca_argp_start` → `doca_argp_destroy` in order; picking a parameter type from the full public enum (`DOCA_ARGP_TYPE_STRING`, `_INT`, `_BOOLEAN`, `_DEVICE`, `_DEVICE_REP`, `_DOUBLE` — six values, not three); preserving the standard `--device` / `--representor` / `--json` (`-j`; real flag is `--json`, NOT `--json-config`)
Passed 19 of 23 test cases with the skill, and 9 of 23 without it.
and 12 more in the full report
10 fixed9 passed either way4 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.
Which CLI flags are provided by doca-argp to specify network representor ports or list available representors?
| Checked | Without skill | With skill |
|---|---|---|
| Names --representor for specifying a target representor. | Missed | Passed |
| Names --rep-list for enumerating available representors. | Missed | Passed |
The instructions your model reads when the skill loads.
Where to start: This skill assumes DOCA is already installed
and the user is doing hands-on CLI work on a DOCA sample or
new DOCA-using app. 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 the Arg Parser express on this version. If
the user has not installed DOCA yet, route to
doca-setup first. If the user is
about to rewrite a sample's CLI with getopt / argparse /
custom parsing instead of reusing the Arg Parser, read the
load-bearing rule in
CAPABILITIES.md ## Capabilities and modes
before any code change.
The CLASSES of Arg Parser 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.
--my-flag to
/opt/mellanox/doca/samples/doca_dma/dma_local_copy/ so the
sample still accepts --device <PCI> and --sdk-log-level <level> the same way it did before". Answered by the
reuse-the-Arg-Parser rule in
CAPABILITIES.md ## Capabilities and modes
TASKS.md ## modify.doca_argp_param_set_* return BAD_STATE on my
second call?" — worked example: "registering a new param
after doca_argp_start has already parsed argv". Answered by
the lifecycle order in
CAPABILITIES.md ## Capabilities and modes
CAPABILITIES.md ## Error taxonomy
for DOCA_ERROR_BAD_STATE.test cases passed, vs 9 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.