SKILLEMALL.ai

AF doca-gpunetio-ib-write-bw

Use this skill when the user is building, running, or interpreting the doca/tools/gpunetio_ib_write_bw client+server benchmark — a CUDA kernel on the client posts RDMA WRITE work requests through the doca-gpunetio device-side surface to measure sustained GPU-driven WRITE bandwidth on a GPU+IB-device pair. Trigger even when the user does not explicitly mention "doca-gpunetio-ib-write-bw" or "GPUNetIO" — typical implicit phrasings include "measure WRITE BW when the GPU posts the WRs", "BW swings between runs on the same flags", "is the NIC saturated or am I CPU-bound on the CUDA kernel", "meson compile fails for the GPUNetIO bw tool", "nvidia_peermem isn't picking up my GPU buffer", or "GPU-initiated WRITE throughput vs CPU-initiated perftest". Refuse and route elsewhere for general doca-gpunetio library work, DOCA install, the GPU-initiated WRITE latency analog, the CPU-initiated upstream perftest, or application-level end-to-end throughput — those belong to other skills.

ClawHub Agent Skills author: NVIDIA 1 file body ≈ 3 842 tokens Open the sourceclawhub.ai analyzed 2 d ago

Use this skill when the user is building, running, or interpreting the doca/tools/gpunetioibwritebw client+server benchmark — a CUDA kernel on the client…

As a process F 56/100 · Will not run — References files that are not bundled: TASKS.md, TASKS.md, TASKS.md

GeneratorSoftware developmentMarketingtype and topics are labelled automatically from the skill text
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
F
56/100
Will not run
References files that are not bundled: TASKS.md, TASKS.md, TASKS.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: TASKS.md
  • warning missing-ref reference to a missing file: TASKS.md
  • warning missing-ref reference to a missing file: TASKS.md
  • warning missing-ref reference to a missing file: CAPABILITIES.md
  • warning missing-ref reference to a missing file: ../../doca-setup/SKILL.md
  • warning missing-ref reference to a missing file: ../../libs/doca-gpunetio/CAPABILITIES.md
  • warning missing-ref reference to a missing file: ../../libs/doca-gpi/CAPABILITIES.md
  • warning missing-ref reference to a missing file: CAPABILITIES.md
  • warning missing-ref reference to a missing file: CAPABILITIES.md
  • warning missing-ref reference to a missing file: TASKS.md
  • warning missing-ref reference to a missing file: TASKS.md
  • warning missing-ref reference to a missing file: CAPABILITIES.md
  • warning missing-ref reference to a missing file: CAPABILITIES.md
  • warning missing-ref reference to a missing file: ../../doca-version/SKILL.md
  • warning missing-ref reference to a missing file: ../../libs/doca-gpunetio/SKILL.md
  • warning missing-ref reference to a missing file: ../../libs/doca-gpi/SKILL.md
  • warning missing-ref reference to a missing file: ../../doca-public-knowledge-map/SKILL.md
  • warning missing-ref reference to a missing file: ../../doca-programming-guide/SKILL.md
  • warning missing-ref reference to a missing file: ../../libs/doca-rdma/SKILL.md
  • warning missing-ref reference to a missing file: ../../libs/doca-verbs/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-gpunetio-ib-write-lat/SKILL.md
  • warning missing-ref reference to a missing file: ../../doca-debug/SKILL.md
  • warning missing-ref reference to a missing file: ../../doca-hardware-safety/SKILL.md

Process rating: all ten parameters 56/100

Will not run. References files that are not bundled: TASKS.md, TASKS.md, TASKS.md
  • 0Tools and files. 23 referenced file(s) missing: TASKS.md, TASKS.md, TASKS.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 4 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 65Failures and branches. 3 branches
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 36 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3842 tokens
  • 100Progress reporting. Reports progress

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 985: 120–800 characters recommended
  • +2Single-language instructions
  • +5Description quotes 8 example trigger phrases
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 36 items
  • +3Output format is stated explicitly
  • +4Has examples (0 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.