SKILLEMALL.ai
GitHub ↗ RU Sign in

BF doca-bf3-deployment

Use this skill for BlueField-3 (BF3) day-1 platform bring-up via the classic RShim/BFB path: pushing a BlueField bundle (BFB) to the DPU over RShim with bfb-install from the host, the host-to-DPU TMFIFO management channel (tmfifo_net0, the 192.168.100.x convention), RShim daemon state and console-over-rshim, DPU mode selection (DPU/embedded-function vs separated-host/NIC mode) via mlxconfig, post-BFB recovery, a six-state BlueField-state classifier, and verifying the install (cat /etc/mlnx-release plus version checks). Trigger even when the user does not say "BF3" — typical phrasings include {push a BFB to my BlueField-3}, {bfb-install exited 0 but the DPU never came back}, {ping 192.168.100.2 works but ssh fails}, or {is DOCA on the host or the Arm side?}. BFB reflash, mlxconfig set, mode changes, and firmware burns are destructive: require explicit target-bound confirmation and load doca-hardware-safety. App launch, container deploy, env install, and the BF4 BMC-Redfish path route elsewhere.

ClawHub Agent Skills author: NVIDIA 1 file body ≈ 2 359 tokens Open the sourceclawhub.ai↗ analyzed 32 h ago

Use this skill for BlueField-3 (BF3) day-1 platform bring-up via the classic RShim/BFB path: pushing a BlueField bundle (BFB) to the DPU over RShim with…

As a process F 49/100 · Will not run — References files that are not bundled: ../doca-bf4-deployment/SKILL.md, TASKS.md, TASKS.md

AnalyzerInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
F
49/100
Will not run
References files that are not bundled: ../doca-bf4-deployment/SKILL.md, TASKS.md, TASKS.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
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: ../doca-bf4-deployment/SKILL.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-bare-metal-deployment/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-container-deployment/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-hardware-safety/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-setup/TASKS.md
  • warning missing-ref reference to a missing file: ../doca-public-knowledge-map/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-bare-metal-deployment/TASKS.md
  • warning missing-ref reference to a missing file: ../doca-version/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-setup/SKILL.md
  • warning missing-ref reference to a missing file: references/details.md
  • warning missing-ref reference to a missing file: references/details.md
  • warning missing-ref reference to a missing file: references/details.md
  • warning missing-ref reference to a missing file: references/details.md

Process rating: all ten parameters 49/100

Will not run. References files that are not bundled: ../doca-bf4-deployment/SKILL.md, TASKS.md, TASKS.md
  • 0Tools and files. 16 referenced file(s) missing: ../doca-bf4-deployment/SKILL.md, TASKS.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. 36 mutating operations with no state check
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 22 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2359 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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 1008: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +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: 70.