BC 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 include "how do I run my built service on the BlueField?", "where do I drop the pod-spec YAML?", "pod stuck in Pending / ImagePullBackOff / CrashLoopBackOff", "container Running but service isn't ready", "pod restart-loops after edit", or "DMS and Firefly together". Refuse and route elsewhere for per-service config schemas, DOCA install, library-API questions, external NVIDIA services (BlueMan, HBN, SNAP, Virtio-net), or full Kubernetes-cluster ops — those belong to other skills.
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…
As a process C 51/100 · Has gaps — References files that are not bundled: ../doca-setup/TASKS.md, ../doca-bare-metal-deployment/SKILL.md, TASKS.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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-refreference to a missing file: ../doca-setup/TASKS.md - warning
missing-refreference to a missing file: ../doca-bare-metal-deployment/SKILL.md - warning
missing-refreference to a missing file: TASKS.md - warning
missing-refreference to a missing file: TASKS.md - warning
missing-refreference to a missing file: CAPABILITIES.md - warning
missing-refreference to a missing file: ../doca-public-knowledge-map/SKILL.md - warning
missing-refreference to a missing file: ../doca-setup/SKILL.md - warning
missing-refreference to a missing file: references/details.md - warning
missing-refreference to a missing file: references/details.md - warning
missing-refreference to a missing file: references/details.md - warning
missing-refreference to a missing file: references/details.md
Process rating: all ten parameters 51/100
- 0Tools and files. 11 referenced file(s) missing: ../doca-setup/TASKS.md, ../doca-bare-metal-deployment/SKILL.md, TASKS.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 55Failures and branches. 1 branches
- 100Steps. 10 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2182 tokens
- 100Running it twice. Mutating operations check current state
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 984: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +4Structure: 8 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (0 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.