Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-container-deployment
Use this skill when the user is hands-on deploying an in-bundle DOCA service container (Argus, DMS, Firefly, or UROM service) on a BlueField — kubelet standalone watching a static-pod manifests directory, YAML pod-spec drop, kubelet status / ENTRYPOINT logs / per-service liveness, smoke-before-bulk, and the layered error taxonomy (pod-spec, scheduling, image pull, runtime, mount, network, version, host). Trigger even when the user does not say "container deployment" — typical implicit phrasings
Passed 16 of 19 test cases with the skill, and 7 of 19 without it.
and 17 more in the full report
10 fixed8 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am deploying the DOCA Argus container service. Where should I look for the canonical schema definition and validation rules for Argus-specific YAML parameters?
| Checked | Without skill | With skill |
|---|---|---|
| Directs Argus-specific YAML schema queries to the dedicated `doca-argus` service skill. | Missed | Passed |
| Refrains from inventing service-specific configuration schema fields. | Passed | Passed |
The instructions your model reads when the skill loads.
Where to start: This skill is for operating the cross-cutting DOCA container-deployment runtime — the shared pattern every DOCA service on the BlueField uses to come up (kubelet standalone agent on the BlueField Arm watching a static-pod manifests directory; the operator drops a YAML pod spec into that directory; kubelet schedules the pod and runs the container).
If the developer has NOT yet decided container vs. bare-metal
("I just got a BlueField, what now?", "my code is built, how do I
run it?", "how do I deploy this?"), route them BACK to
doca-setup ## recognize first.
That is the front-door routing decision. The wrong failure mode is
to silently push every developer onto the container path because the
agent loaded this skill first. ## recognize detects the system
shape, asks the minimum residual question, and lands the developer on
either this skill (when the workload is a packaged DOCA service to
drop on a BlueField) or the bare-metal-path sibling
doca-bare-metal-deployment
(when the workload is a DOCA-linked application binary the developer
launches directly).
If the developer is already on the container path, open
TASKS.md and start at
## configure. If the question is what shape
of runtime is this and what does the deployment contract look like,
start at CAPABILITIES.md. For per-service
overlays, follow the per-service skill under skills/services/ that
layers on top of this one — the supported overlays are Argus, DMS,
Firefly, and UROM service. Flow-Inspector and OS-Inspector are
policy-excluded from this public bundle; route them through
doca-public-knowledge-map
instead of applying this runtime overlay. Externally-productized
NVIDIA services (BlueMan, HBN, SNAP, Virtio-net, DOCA Telemetry
Service as productized, …) are also out of scope and route through
that map. If DOCA is
not installed on the BlueField target yet, route to
doca-setup first.
test cases passed, vs 7 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.