AF doca-bare-metal-deployment
Use this skill for launching, supervising, debugging, OR platform lifecycle on a BlueField — BFB install, RShim/TMFIFO, host PF rebind, post-BFB recovery — taking a DOCA-linked binary to a healthy run directly on hardware (host x86 + BlueField NIC over PCIe, or BlueField Arm bare-metal). No container, no kubelet. Covers launch mode (direct, tmux, systemd), PCI/NUMA/ CPU/IRQ binding, co-tenant isolation (cgroup-v2/netns/numactl), a seven-layer error taxonomy, and a six-state BlueField lifecycle classifier. Trigger even when user does not say "bare-metal" — implicit phrasings include "binary exits 1 right after launch", "systemd keeps restarting it", "no matching device on the BF", "bfb-install exited 0 but DPU is dead", "ping 192.168.100.2 works but ssh fails", "host PFs aren't showing netdevs". Destructive firmware burn / mlxconfig set requires explicit confirmation via doca-hardware-safety; containers, library APIs, env prep, and build use other skills.
Use this skill for launching, supervising, debugging, OR platform lifecycle on a BlueField — BFB install, RShim/TMFIFO, host PF rebind, post-BFB recovery —…
As a process F 42/100 · Will not run — References files that are not bundled: ../doca-container-deployment/SKILL.md, ../doca-programming-guide/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-container-deployment/SKILL.md - warning
missing-refreference to a missing file: ../doca-programming-guide/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-setup/SKILL.md - warning
missing-refreference to a missing file: ../doca-programming-guide/TASKS.md - warning
missing-refreference to a missing file: ../doca-public-knowledge-map/references/map.md - warning
missing-refreference to a missing file: ../doca-setup/TASKS.md - warning
missing-refreference to a missing file: ../doca-public-knowledge-map/SKILL.md - warning
missing-refreference to a missing file: ../doca-hardware-safety/SKILL.md - warning
missing-refreference to a missing file: ../doca-version/SKILL.md - warning
missing-refreference to a missing file: ../doca-setup/TASKS.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 42/100
- 0Tools and files. 17 referenced file(s) missing: ../doca-container-deployment/SKILL.md, ../doca-programming-guide/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
- 30Running it twice. 18 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Failures and branches. 2 branches
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2545 tokens
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 968: 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: 22 items
- +4Has examples (0 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.