[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-nvidia-doca-bf3-deployment":3,"mdc--x9d6oi-key":31,"related-repo-nvidia-doca-bf3-deployment":1095,"related-org-nvidia-doca-bf3-deployment":1197},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":20,"repoUrl":21,"updatedAt":22,"license":23,"forks":24,"topics":25,"repo":26,"sourceUrl":29,"mdContent":30},"doca-bf3-deployment","deploy BlueField-3 platform bundles","Use this skill for BlueField-3 (BF3) day-1 platform bring-up via the classic RShim\u002FBFB 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\u002Fembedded-function vs separated-host\u002FNIC mode) via mlxconfig, post-BFB recovery, a six-state BlueField-state classifier, and verifying the install (cat \u002Fetc\u002Fmlnx-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.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},"nvidia","NVIDIA","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fnvidia.png",[12,16,17],{"name":13,"slug":14,"type":15},"Deployment","deployment","tag",{"name":9,"slug":8,"type":15},{"name":18,"slug":19,"type":15},"Infrastructure","infrastructure",2473,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fskills","2026-07-30T05:28:35.406002","Apache-2.0",281,[],{"repoUrl":21,"stars":20,"forks":24,"topics":27,"description":28},[],"AI agent skills published by NVIDIA","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fskills\u002Ftree\u002FHEAD\u002Fskills\u002Fdoca-bf3-deployment","---\nlicense: Apache-2.0\nname: doca-bf3-deployment\ndescription: >\n  Use this skill for BlueField-3 (BF3) day-1 platform bring-up via\n  the classic RShim\u002FBFB path: pushing a BlueField bundle (BFB) to\n  the DPU over RShim with bfb-install from the host, the host-to-DPU\n  TMFIFO management channel (tmfifo_net0, the 192.168.100.x\n  convention), RShim daemon state and console-over-rshim, DPU mode\n  selection (DPU\u002Fembedded-function vs separated-host\u002FNIC mode) via\n  mlxconfig, post-BFB recovery, a six-state BlueField-state\n  classifier, and verifying the install (cat \u002Fetc\u002Fmlnx-release plus\n  version checks). Trigger even when the user does not say \"BF3\" —\n  typical phrasings include {push a BFB to my BlueField-3},\n  {bfb-install exited 0 but the DPU never came back}, {ping\n  192.168.100.2 works but ssh fails}, or {is DOCA on the host or\n  the Arm side?}. BFB reflash, mlxconfig set, mode changes, and\n  firmware burns are destructive: require explicit target-bound\n  confirmation and load doca-hardware-safety. App launch, container\n  deploy, env install, and the BF4 BMC-Redfish path route elsewhere.\nmetadata:\n  kind: library\ncompatibility: >\n  No DOCA install required to read this skill (it is a\n  platform-lifecycle overlay loaded against BF3 hardware); the\n  bring-up and validation steps within DO require a real\n  BlueField-3, host-side RShim access (PCIe or USB), the matching\n  DOCA-Host install, and a BlueField bundle (BFB) image downloaded\n  from the public DOCA Downloads page.\n---\n\n# DOCA BlueField-3 (BF3) deployment\n\n**Where to start:** This skill is the bundle's home for **BlueField-3\nday-1 platform bring-up** — taking a BF3 from \"powered card in the\nslot\" (or a card that just came back broken from a BFB push) to\n\"Arm OS healthy, TMFIFO up, host PFs bound, four-way version match\nclosed, ready to run a workload\". It owns the **classic RShim\u002FBFB\npath** that BF3 uses today; the newer BMC-Redfish provisioning path\nis the sibling skill\n[`doca-bf4-deployment`](..\u002Fdoca-bf4-deployment\u002FSKILL.md) (the BF4\nequivalent). If the user has a BF3 and needs to push a BFB, recover\na DPU that did not come back, or verify the install, open\n[`TASKS.md`](TASKS.md) and start at\n[`## configure`](TASKS.md#configure). If the question is *what shape\ndoes the BF3 platform-bring-up surface even have*, start at\n[`CAPABILITIES.md`](CAPABILITIES.md). Once the BF3 is healthy, this\nskill routes **onward** to the deployment skills — running a binary\ngoes to\n[`doca-bare-metal-deployment`](..\u002Fdoca-bare-metal-deployment\u002FSKILL.md);\ndeploying a service container goes to\n[`doca-container-deployment`](..\u002Fdoca-container-deployment\u002FSKILL.md).\n\nEvery **mutating** burn invoked from a bring-up step — the BFB\nreflash itself, any `mlxconfig set` (including a DPU\u002Fseparated-host\nmode flip), a firmware burn, or a kernel-boot-parameter change — is\ngoverned by the change-application meta-policy in\n[`doca-hardware-safety`](..\u002Fdoca-hardware-safety\u002FSKILL.md), which\nthe agent loads ALONGSIDE this skill. This skill adds only the\n**BF3-specific operational sequencing** on top; it does NOT redefine\nthe preflight \u002F OOB-console \u002F maintenance-window \u002F rollback\ndiscipline that meta-policy owns.\n\n## Audience\n\nThis skill serves **external DOCA operators bringing up a real\nBlueField-3** — i.e. people who already have:\n\n- a physical BlueField-3 in a host (or a standalone BF3 they can\n  reach over its console \u002F management network),\n- host-side RShim access to the DPU (the RShim userspace daemon and\n  the `\u002Fdev\u002Frshim*` character-device tree present over the PCIe or\n  USB RShim interface), and\n- a matching DOCA-Host install on the host plus a BlueField bundle\n  (BFB) image downloaded from the public DOCA Downloads page.\n\nIt is **not** for:\n\n- BlueField-4 bring-up (the BMC-Redfish provisioning path) — route\n  to [`doca-bf4-deployment`](..\u002Fdoca-bf4-deployment\u002FSKILL.md), the\n  BF4 equivalent of this skill,\n- kernel-driver or BlueField-OS developers contributing to `mlx5_*`\n  or the BFB image itself (that is internal-tree work, not a\n  field deployment),\n- operators who already have a healthy BF3 and just want to *run a\n  binary* (route to\n  [`doca-bare-metal-deployment`](..\u002Fdoca-bare-metal-deployment\u002FSKILL.md))\n  or *deploy a service container* (route to\n  [`doca-container-deployment`](..\u002Fdoca-container-deployment\u002FSKILL.md)),\n- fresh-no-hardware users with no DOCA install — route to\n  [`doca-setup ## no-install`](..\u002Fdoca-setup\u002FTASKS.md#no-install).\n\nThe skill teaches the agent the BF3 bring-up *procedure* and the\nrules for quoting documented commands from the public BlueField\nPlatform Software Manual, the public DOCA Installation Guide, and\nthe MFT manual via\n[`doca-public-knowledge-map`](..\u002Fdoca-public-knowledge-map\u002FSKILL.md);\nit does **not** invent `bfb-install` flag sets, BFB image filenames,\nRShim character-device paths, `bf.cfg` schema keys, `mlxconfig`\nparameter names, or TMFIFO subnets from memory. Where a fact is\nalready vetted in\n[`doca-bare-metal-deployment ## bluefield-lifecycle`](..\u002Fdoca-bare-metal-deployment\u002FTASKS.md#bluefield-lifecycle),\nthis skill reuses that exact fact rather than restating a new one.\n\n## When to load this skill\n\nLoad this skill when the user is doing **hands-on BlueField-3\nplatform bring-up over the RShim\u002FBFB path**, or asking a\ncross-cutting BF3 lifecycle question that is not specific to one\nlibrary's API. Concretely:\n\n- Pushing a BFB image to a BF3 for the first time (or re-pushing\n  after a failed install), from the host over the RShim interface\n  with `bfb-install`.\n- Bringing up or recovering the host-to-DPU TMFIFO management\n  channel (`tmfifo_net0`, the documented `192.168.100.x`\n  convention) and the RShim console.\n- Confirming RShim driver\u002Fdaemon state on the host (the userspace\n  `rshim` daemon and the `\u002Fdev\u002Frshim*` tree) before any push or\n  console capture.\n- Deciding (and routing) a DPU-mode change — DPU \u002F embedded-function\n  mode vs separated-host \u002F NIC mode — knowing the actual `mlxconfig\n  set` burn leaves this skill for\n  [`doca-hardware-safety`](..\u002Fdoca-hardware-safety\u002FSKILL.md).\n- Recovering a BF3 that did not come back after a BFB push:\n  `bfb-install` exited 0 but the DPU never reached the documented\n  `DPU is ready` marker; `ping 192.168.100.2` works but SSH refuses;\n  host PFs are present in `lspci -d 15b3:` but their netdevs are\n  gone.\n- Verifying a BF3 install — `cat \u002Fetc\u002Fmlnx-release` on the Arm side,\n  the four-way version match per\n  [`doca-version`](..\u002Fdoca-version\u002FSKILL.md) — and distinguishing\n  the host-side DOCA install from the BlueField-Arm-side DOCA\n  install.\n- Cross-cutting questions: *\"is DOCA on the host or on the Arm\n  side, and which one do I install?\"*, *\"my BF3 was fine last week\n  and after a BFB push it never came back — where do I start?\"*,\n  *\"how do I tell which `\u002Fdev\u002Frshim\u003CN>` is which BlueField on a\n  multi-DPU host?\"*.\n\nDo **not** load this skill for: BlueField-4 bring-up (route to\n[`doca-bf4-deployment`](..\u002Fdoca-bf4-deployment\u002FSKILL.md), the BF4\nequivalent); running a DOCA-linked binary on a healthy BF3 (route to\n[`doca-bare-metal-deployment`](..\u002Fdoca-bare-metal-deployment\u002FSKILL.md));\ndeploying a DOCA service container (route to\n[`doca-container-deployment`](..\u002Fdoca-container-deployment\u002FSKILL.md));\nenv-preparation including hugepages, IOMMU, pkg-config, and devlink\nmode flips (use [`doca-setup`](..\u002Fdoca-setup\u002FSKILL.md)); the body of\nthe version-match rule (use [`doca-version`](..\u002Fdoca-version\u002FSKILL.md));\nor any hardware-state-changing burn itself — the change-application\ndiscipline is meta-policy owned by\n[`doca-hardware-safety`](..\u002Fdoca-hardware-safety\u002FSKILL.md), loaded\nALONGSIDE this skill.\n\n## What this skill provides\n\nThis is a **thin loader**. Substantive material lives in two\ncompanion files:\n\n- `CAPABILITIES.md` — the BF3 platform-bring-up contract: the\n  RShim\u002FBFB transport surface (the userspace RShim daemon, the\n  `\u002Fdev\u002Frshim*` tree, console-over-rshim, the BFB image as the unit\n  of input), the TMFIFO management-channel surface (`tmfifo_net0` \u002F\n  `tm-br`, the documented `192.168.100.x` convention, the\n  `ip route get`-before-`ping` loopback gotcha), the DPU-mode\n  surface (DPU \u002F embedded-function vs separated-host \u002F NIC mode, set\n  via `mlxconfig` at BFB-install time — a MUTATING burn routed to\n  [`doca-hardware-safety`](..\u002Fdoca-hardware-safety\u002FSKILL.md)), the\n  host-side-vs-Arm-side DOCA install distinction, the\n  BF3-version overlay on the four-way match owned by\n  [`doca-version`](..\u002Fdoca-version\u002FSKILL.md), the cross-cutting error\n  taxonomy, the observability surface, and the safety policy\n  (overlay on\n  [`doca-hardware-safety`](..\u002Fdoca-hardware-safety\u002FSKILL.md)).\n- `TASKS.md` — step-by-step workflows for the in-scope BF3\n  lifecycle verbs: `configure`, `build` (routing stub), `modify`,\n  `run` (the BFB-install + RShim\u002FTMFIFO bring-up sequence), `test`\n  (the post-BFB readiness smoke), `debug` (the six-state\n  `bluefield-state-classifier`), and the `Deferred task verbs`\n  block routing app-launch \u002F container \u002F install \u002F library-API \u002F\n  hardware-state-change \u002F BF4 questions out to their owning skills.\n\nThe skill assumes a target where:\n\n- a BlueField-3 is physically present and powered, reachable from a\n  host that has the RShim daemon and `\u002Fdev\u002Frshim*` tree available,\n- the operator has a BFB image downloaded from the public DOCA\n  Downloads page (route via\n  [`doca-public-knowledge-map`](..\u002Fdoca-public-knowledge-map\u002FSKILL.md)),\n  and\n- the operator has an out-of-band path (BMC console, serial-over-LAN,\n  or physical UART) to reach the BF3 if a push breaks the Arm OS.\n\nIt does **not** cover installing DOCA on a host from scratch (that\ngoes through [`doca-setup`](..\u002Fdoca-setup\u002FSKILL.md)), and it does\n**not** cover BlueField-4 (that goes through\n[`doca-bf4-deployment`](..\u002Fdoca-bf4-deployment\u002FSKILL.md)).\n\n## Loading order\n\n1. Read this `SKILL.md` first to confirm the user's question is in\n   scope (BF3 platform bring-up over the RShim\u002FBFB path; NOT BF4,\n   NOT app-launch, NOT a library-API question).\n2. **For the bring-up contract (RShim\u002FBFB transport, TMFIFO\n   channel, DPU-mode surface, host-vs-Arm install distinction,\n   BF3-version overlay, error taxonomy, observability surface, BF3\n   safety overlay), see [CAPABILITIES.md](CAPABILITIES.md).**\n3. **For step-by-step workflows — `configure`, `build` (routing\n   stub), `modify`, `run` (BFB install + RShim\u002FTMFIFO bring-up),\n   `test` (post-BFB readiness smoke), `debug` (the six-state\n   `bluefield-state-classifier`), plus the `Deferred task verbs`\n   block — see [TASKS.md](TASKS.md).**\n\n## Example questions this skill answers well\n\nSee [`references\u002Fdetails.md`](references\u002Fdetails.md#example-questions-this-skill-answers-well).\n## What this skill deliberately does not ship\n\nSee [`references\u002Fdetails.md`](references\u002Fdetails.md#what-this-skill-deliberately-does-not-ship).\n## Related skills\n\nSee [`references\u002Fdetails.md`](references\u002Fdetails.md#related-skills).\n",{"data":32,"body":36},{"license":23,"name":4,"description":6,"metadata":33,"compatibility":35},{"kind":34},"library","No DOCA install required to read this skill (it is a platform-lifecycle overlay loaded against BF3 hardware); the bring-up and validation steps within DO require a real BlueField-3, host-side RShim access (PCIe or USB), the matching DOCA-Host install, and a BlueField bundle (BFB) image downloaded from the public DOCA Downloads page.\n",{"type":37,"children":38},"root",[39,48,161,200,207,219,247,259,344,410,416,428,598,671,677,689,855,860,895,931,937,1033,1039,1055,1061,1075,1081],{"type":40,"tag":41,"props":42,"children":44},"element","h1",{"id":43},"doca-bluefield-3-bf3-deployment",[45],{"type":46,"value":47},"text","DOCA BlueField-3 (BF3) deployment",{"type":40,"tag":49,"props":50,"children":51},"p",{},[52,58,60,65,67,72,74,86,88,97,99,109,111,117,119,128,130,135,137,147,149,159],{"type":40,"tag":53,"props":54,"children":55},"strong",{},[56],{"type":46,"value":57},"Where to start:",{"type":46,"value":59}," This skill is the bundle's home for ",{"type":40,"tag":53,"props":61,"children":62},{},[63],{"type":46,"value":64},"BlueField-3\nday-1 platform bring-up",{"type":46,"value":66}," — taking a BF3 from \"powered card in the\nslot\" (or a card that just came back broken from a BFB push) to\n\"Arm OS healthy, TMFIFO up, host PFs bound, four-way version match\nclosed, ready to run a workload\". It owns the ",{"type":40,"tag":53,"props":68,"children":69},{},[70],{"type":46,"value":71},"classic RShim\u002FBFB\npath",{"type":46,"value":73}," that BF3 uses today; the newer BMC-Redfish provisioning path\nis the sibling skill\n",{"type":40,"tag":75,"props":76,"children":78},"a",{"href":77},"..\u002Fdoca-bf4-deployment\u002FSKILL.md",[79],{"type":40,"tag":80,"props":81,"children":83},"code",{"className":82},[],[84],{"type":46,"value":85},"doca-bf4-deployment",{"type":46,"value":87}," (the BF4\nequivalent). If the user has a BF3 and needs to push a BFB, recover\na DPU that did not come back, or verify the install, open\n",{"type":40,"tag":75,"props":89,"children":91},{"href":90},"TASKS.md",[92],{"type":40,"tag":80,"props":93,"children":95},{"className":94},[],[96],{"type":46,"value":90},{"type":46,"value":98}," and start at\n",{"type":40,"tag":75,"props":100,"children":102},{"href":101},"TASKS.md#configure",[103],{"type":40,"tag":80,"props":104,"children":106},{"className":105},[],[107],{"type":46,"value":108},"## configure",{"type":46,"value":110},". If the question is ",{"type":40,"tag":112,"props":113,"children":114},"em",{},[115],{"type":46,"value":116},"what shape\ndoes the BF3 platform-bring-up surface even have",{"type":46,"value":118},", start at\n",{"type":40,"tag":75,"props":120,"children":122},{"href":121},"CAPABILITIES.md",[123],{"type":40,"tag":80,"props":124,"children":126},{"className":125},[],[127],{"type":46,"value":121},{"type":46,"value":129},". Once the BF3 is healthy, this\nskill routes ",{"type":40,"tag":53,"props":131,"children":132},{},[133],{"type":46,"value":134},"onward",{"type":46,"value":136}," to the deployment skills — running a binary\ngoes to\n",{"type":40,"tag":75,"props":138,"children":140},{"href":139},"..\u002Fdoca-bare-metal-deployment\u002FSKILL.md",[141],{"type":40,"tag":80,"props":142,"children":144},{"className":143},[],[145],{"type":46,"value":146},"doca-bare-metal-deployment",{"type":46,"value":148},";\ndeploying a service container goes to\n",{"type":40,"tag":75,"props":150,"children":152},{"href":151},"..\u002Fdoca-container-deployment\u002FSKILL.md",[153],{"type":40,"tag":80,"props":154,"children":156},{"className":155},[],[157],{"type":46,"value":158},"doca-container-deployment",{"type":46,"value":160},".",{"type":40,"tag":49,"props":162,"children":163},{},[164,166,171,173,179,181,191,193,198],{"type":46,"value":165},"Every ",{"type":40,"tag":53,"props":167,"children":168},{},[169],{"type":46,"value":170},"mutating",{"type":46,"value":172}," burn invoked from a bring-up step — the BFB\nreflash itself, any ",{"type":40,"tag":80,"props":174,"children":176},{"className":175},[],[177],{"type":46,"value":178},"mlxconfig set",{"type":46,"value":180}," (including a DPU\u002Fseparated-host\nmode flip), a firmware burn, or a kernel-boot-parameter change — is\ngoverned by the change-application meta-policy in\n",{"type":40,"tag":75,"props":182,"children":184},{"href":183},"..\u002Fdoca-hardware-safety\u002FSKILL.md",[185],{"type":40,"tag":80,"props":186,"children":188},{"className":187},[],[189],{"type":46,"value":190},"doca-hardware-safety",{"type":46,"value":192},", which\nthe agent loads ALONGSIDE this skill. This skill adds only the\n",{"type":40,"tag":53,"props":194,"children":195},{},[196],{"type":46,"value":197},"BF3-specific operational sequencing",{"type":46,"value":199}," on top; it does NOT redefine\nthe preflight \u002F OOB-console \u002F maintenance-window \u002F rollback\ndiscipline that meta-policy owns.",{"type":40,"tag":201,"props":202,"children":204},"h2",{"id":203},"audience",[205],{"type":46,"value":206},"Audience",{"type":40,"tag":49,"props":208,"children":209},{},[210,212,217],{"type":46,"value":211},"This skill serves ",{"type":40,"tag":53,"props":213,"children":214},{},[215],{"type":46,"value":216},"external DOCA operators bringing up a real\nBlueField-3",{"type":46,"value":218}," — i.e. people who already have:",{"type":40,"tag":220,"props":221,"children":222},"ul",{},[223,229,242],{"type":40,"tag":224,"props":225,"children":226},"li",{},[227],{"type":46,"value":228},"a physical BlueField-3 in a host (or a standalone BF3 they can\nreach over its console \u002F management network),",{"type":40,"tag":224,"props":230,"children":231},{},[232,234,240],{"type":46,"value":233},"host-side RShim access to the DPU (the RShim userspace daemon and\nthe ",{"type":40,"tag":80,"props":235,"children":237},{"className":236},[],[238],{"type":46,"value":239},"\u002Fdev\u002Frshim*",{"type":46,"value":241}," character-device tree present over the PCIe or\nUSB RShim interface), and",{"type":40,"tag":224,"props":243,"children":244},{},[245],{"type":46,"value":246},"a matching DOCA-Host install on the host plus a BlueField bundle\n(BFB) image downloaded from the public DOCA Downloads page.",{"type":40,"tag":49,"props":248,"children":249},{},[250,252,257],{"type":46,"value":251},"It is ",{"type":40,"tag":53,"props":253,"children":254},{},[255],{"type":46,"value":256},"not",{"type":46,"value":258}," for:",{"type":40,"tag":220,"props":260,"children":261},{},[262,277,290,328],{"type":40,"tag":224,"props":263,"children":264},{},[265,267,275],{"type":46,"value":266},"BlueField-4 bring-up (the BMC-Redfish provisioning path) — route\nto ",{"type":40,"tag":75,"props":268,"children":269},{"href":77},[270],{"type":40,"tag":80,"props":271,"children":273},{"className":272},[],[274],{"type":46,"value":85},{"type":46,"value":276},", the\nBF4 equivalent of this skill,",{"type":40,"tag":224,"props":278,"children":279},{},[280,282,288],{"type":46,"value":281},"kernel-driver or BlueField-OS developers contributing to ",{"type":40,"tag":80,"props":283,"children":285},{"className":284},[],[286],{"type":46,"value":287},"mlx5_*",{"type":46,"value":289},"\nor the BFB image itself (that is internal-tree work, not a\nfield deployment),",{"type":40,"tag":224,"props":291,"children":292},{},[293,295,300,302,310,312,317,318,326],{"type":46,"value":294},"operators who already have a healthy BF3 and just want to ",{"type":40,"tag":112,"props":296,"children":297},{},[298],{"type":46,"value":299},"run a\nbinary",{"type":46,"value":301}," (route to\n",{"type":40,"tag":75,"props":303,"children":304},{"href":139},[305],{"type":40,"tag":80,"props":306,"children":308},{"className":307},[],[309],{"type":46,"value":146},{"type":46,"value":311},")\nor ",{"type":40,"tag":112,"props":313,"children":314},{},[315],{"type":46,"value":316},"deploy a service container",{"type":46,"value":301},{"type":40,"tag":75,"props":319,"children":320},{"href":151},[321],{"type":40,"tag":80,"props":322,"children":324},{"className":323},[],[325],{"type":46,"value":158},{"type":46,"value":327},"),",{"type":40,"tag":224,"props":329,"children":330},{},[331,333,343],{"type":46,"value":332},"fresh-no-hardware users with no DOCA install — route to\n",{"type":40,"tag":75,"props":334,"children":336},{"href":335},"..\u002Fdoca-setup\u002FTASKS.md#no-install",[337],{"type":40,"tag":80,"props":338,"children":340},{"className":339},[],[341],{"type":46,"value":342},"doca-setup ## no-install",{"type":46,"value":160},{"type":40,"tag":49,"props":345,"children":346},{},[347,349,354,356,366,368,372,374,380,382,388,390,396,398,408],{"type":46,"value":348},"The skill teaches the agent the BF3 bring-up ",{"type":40,"tag":112,"props":350,"children":351},{},[352],{"type":46,"value":353},"procedure",{"type":46,"value":355}," and the\nrules for quoting documented commands from the public BlueField\nPlatform Software Manual, the public DOCA Installation Guide, and\nthe MFT manual via\n",{"type":40,"tag":75,"props":357,"children":359},{"href":358},"..\u002Fdoca-public-knowledge-map\u002FSKILL.md",[360],{"type":40,"tag":80,"props":361,"children":363},{"className":362},[],[364],{"type":46,"value":365},"doca-public-knowledge-map",{"type":46,"value":367},";\nit does ",{"type":40,"tag":53,"props":369,"children":370},{},[371],{"type":46,"value":256},{"type":46,"value":373}," invent ",{"type":40,"tag":80,"props":375,"children":377},{"className":376},[],[378],{"type":46,"value":379},"bfb-install",{"type":46,"value":381}," flag sets, BFB image filenames,\nRShim character-device paths, ",{"type":40,"tag":80,"props":383,"children":385},{"className":384},[],[386],{"type":46,"value":387},"bf.cfg",{"type":46,"value":389}," schema keys, ",{"type":40,"tag":80,"props":391,"children":393},{"className":392},[],[394],{"type":46,"value":395},"mlxconfig",{"type":46,"value":397},"\nparameter names, or TMFIFO subnets from memory. Where a fact is\nalready vetted in\n",{"type":40,"tag":75,"props":399,"children":401},{"href":400},"..\u002Fdoca-bare-metal-deployment\u002FTASKS.md#bluefield-lifecycle",[402],{"type":40,"tag":80,"props":403,"children":405},{"className":404},[],[406],{"type":46,"value":407},"doca-bare-metal-deployment ## bluefield-lifecycle",{"type":46,"value":409},",\nthis skill reuses that exact fact rather than restating a new one.",{"type":40,"tag":201,"props":411,"children":413},{"id":412},"when-to-load-this-skill",[414],{"type":46,"value":415},"When to load this skill",{"type":40,"tag":49,"props":417,"children":418},{},[419,421,426],{"type":46,"value":420},"Load this skill when the user is doing ",{"type":40,"tag":53,"props":422,"children":423},{},[424],{"type":46,"value":425},"hands-on BlueField-3\nplatform bring-up over the RShim\u002FBFB path",{"type":46,"value":427},", or asking a\ncross-cutting BF3 lifecycle question that is not specific to one\nlibrary's API. Concretely:",{"type":40,"tag":220,"props":429,"children":430},{},[431,442,463,483,504,540,565],{"type":40,"tag":224,"props":432,"children":433},{},[434,436,441],{"type":46,"value":435},"Pushing a BFB image to a BF3 for the first time (or re-pushing\nafter a failed install), from the host over the RShim interface\nwith ",{"type":40,"tag":80,"props":437,"children":439},{"className":438},[],[440],{"type":46,"value":379},{"type":46,"value":160},{"type":40,"tag":224,"props":443,"children":444},{},[445,447,453,455,461],{"type":46,"value":446},"Bringing up or recovering the host-to-DPU TMFIFO management\nchannel (",{"type":40,"tag":80,"props":448,"children":450},{"className":449},[],[451],{"type":46,"value":452},"tmfifo_net0",{"type":46,"value":454},", the documented ",{"type":40,"tag":80,"props":456,"children":458},{"className":457},[],[459],{"type":46,"value":460},"192.168.100.x",{"type":46,"value":462},"\nconvention) and the RShim console.",{"type":40,"tag":224,"props":464,"children":465},{},[466,468,474,476,481],{"type":46,"value":467},"Confirming RShim driver\u002Fdaemon state on the host (the userspace\n",{"type":40,"tag":80,"props":469,"children":471},{"className":470},[],[472],{"type":46,"value":473},"rshim",{"type":46,"value":475}," daemon and the ",{"type":40,"tag":80,"props":477,"children":479},{"className":478},[],[480],{"type":46,"value":239},{"type":46,"value":482}," tree) before any push or\nconsole capture.",{"type":40,"tag":224,"props":484,"children":485},{},[486,488,493,495,503],{"type":46,"value":487},"Deciding (and routing) a DPU-mode change — DPU \u002F embedded-function\nmode vs separated-host \u002F NIC mode — knowing the actual ",{"type":40,"tag":80,"props":489,"children":491},{"className":490},[],[492],{"type":46,"value":178},{"type":46,"value":494}," burn leaves this skill for\n",{"type":40,"tag":75,"props":496,"children":497},{"href":183},[498],{"type":40,"tag":80,"props":499,"children":501},{"className":500},[],[502],{"type":46,"value":190},{"type":46,"value":160},{"type":40,"tag":224,"props":505,"children":506},{},[507,509,514,516,522,524,530,532,538],{"type":46,"value":508},"Recovering a BF3 that did not come back after a BFB push:\n",{"type":40,"tag":80,"props":510,"children":512},{"className":511},[],[513],{"type":46,"value":379},{"type":46,"value":515}," exited 0 but the DPU never reached the documented\n",{"type":40,"tag":80,"props":517,"children":519},{"className":518},[],[520],{"type":46,"value":521},"DPU is ready",{"type":46,"value":523}," marker; ",{"type":40,"tag":80,"props":525,"children":527},{"className":526},[],[528],{"type":46,"value":529},"ping 192.168.100.2",{"type":46,"value":531}," works but SSH refuses;\nhost PFs are present in ",{"type":40,"tag":80,"props":533,"children":535},{"className":534},[],[536],{"type":46,"value":537},"lspci -d 15b3:",{"type":46,"value":539}," but their netdevs are\ngone.",{"type":40,"tag":224,"props":541,"children":542},{},[543,545,551,553,563],{"type":46,"value":544},"Verifying a BF3 install — ",{"type":40,"tag":80,"props":546,"children":548},{"className":547},[],[549],{"type":46,"value":550},"cat \u002Fetc\u002Fmlnx-release",{"type":46,"value":552}," on the Arm side,\nthe four-way version match per\n",{"type":40,"tag":75,"props":554,"children":556},{"href":555},"..\u002Fdoca-version\u002FSKILL.md",[557],{"type":40,"tag":80,"props":558,"children":560},{"className":559},[],[561],{"type":46,"value":562},"doca-version",{"type":46,"value":564}," — and distinguishing\nthe host-side DOCA install from the BlueField-Arm-side DOCA\ninstall.",{"type":40,"tag":224,"props":566,"children":567},{},[568,570,575,577,582,584,597],{"type":46,"value":569},"Cross-cutting questions: ",{"type":40,"tag":112,"props":571,"children":572},{},[573],{"type":46,"value":574},"\"is DOCA on the host or on the Arm\nside, and which one do I install?\"",{"type":46,"value":576},", ",{"type":40,"tag":112,"props":578,"children":579},{},[580],{"type":46,"value":581},"\"my BF3 was fine last week\nand after a BFB push it never came back — where do I start?\"",{"type":46,"value":583},",\n",{"type":40,"tag":112,"props":585,"children":586},{},[587,589,595],{"type":46,"value":588},"\"how do I tell which ",{"type":40,"tag":80,"props":590,"children":592},{"className":591},[],[593],{"type":46,"value":594},"\u002Fdev\u002Frshim\u003CN>",{"type":46,"value":596}," is which BlueField on a\nmulti-DPU host?\"",{"type":46,"value":160},{"type":40,"tag":49,"props":599,"children":600},{},[601,603,607,609,617,619,627,629,637,639,649,651,659,661,669],{"type":46,"value":602},"Do ",{"type":40,"tag":53,"props":604,"children":605},{},[606],{"type":46,"value":256},{"type":46,"value":608}," load this skill for: BlueField-4 bring-up (route to\n",{"type":40,"tag":75,"props":610,"children":611},{"href":77},[612],{"type":40,"tag":80,"props":613,"children":615},{"className":614},[],[616],{"type":46,"value":85},{"type":46,"value":618},", the BF4\nequivalent); running a DOCA-linked binary on a healthy BF3 (route to\n",{"type":40,"tag":75,"props":620,"children":621},{"href":139},[622],{"type":40,"tag":80,"props":623,"children":625},{"className":624},[],[626],{"type":46,"value":146},{"type":46,"value":628},");\ndeploying a DOCA service container (route to\n",{"type":40,"tag":75,"props":630,"children":631},{"href":151},[632],{"type":40,"tag":80,"props":633,"children":635},{"className":634},[],[636],{"type":46,"value":158},{"type":46,"value":638},");\nenv-preparation including hugepages, IOMMU, pkg-config, and devlink\nmode flips (use ",{"type":40,"tag":75,"props":640,"children":642},{"href":641},"..\u002Fdoca-setup\u002FSKILL.md",[643],{"type":40,"tag":80,"props":644,"children":646},{"className":645},[],[647],{"type":46,"value":648},"doca-setup",{"type":46,"value":650},"); the body of\nthe version-match rule (use ",{"type":40,"tag":75,"props":652,"children":653},{"href":555},[654],{"type":40,"tag":80,"props":655,"children":657},{"className":656},[],[658],{"type":46,"value":562},{"type":46,"value":660},");\nor any hardware-state-changing burn itself — the change-application\ndiscipline is meta-policy owned by\n",{"type":40,"tag":75,"props":662,"children":663},{"href":183},[664],{"type":40,"tag":80,"props":665,"children":667},{"className":666},[],[668],{"type":46,"value":190},{"type":46,"value":670},", loaded\nALONGSIDE this skill.",{"type":40,"tag":201,"props":672,"children":674},{"id":673},"what-this-skill-provides",[675],{"type":46,"value":676},"What this skill provides",{"type":40,"tag":49,"props":678,"children":679},{},[680,682,687],{"type":46,"value":681},"This is a ",{"type":40,"tag":53,"props":683,"children":684},{},[685],{"type":46,"value":686},"thin loader",{"type":46,"value":688},". Substantive material lives in two\ncompanion files:",{"type":40,"tag":220,"props":690,"children":691},{},[692,783],{"type":40,"tag":224,"props":693,"children":694},{},[695,700,702,707,709,714,716,722,723,728,730,736,738,744,746,751,753,761,763,771,773,781],{"type":40,"tag":80,"props":696,"children":698},{"className":697},[],[699],{"type":46,"value":121},{"type":46,"value":701}," — the BF3 platform-bring-up contract: the\nRShim\u002FBFB transport surface (the userspace RShim daemon, the\n",{"type":40,"tag":80,"props":703,"children":705},{"className":704},[],[706],{"type":46,"value":239},{"type":46,"value":708}," tree, console-over-rshim, the BFB image as the unit\nof input), the TMFIFO management-channel surface (",{"type":40,"tag":80,"props":710,"children":712},{"className":711},[],[713],{"type":46,"value":452},{"type":46,"value":715}," \u002F\n",{"type":40,"tag":80,"props":717,"children":719},{"className":718},[],[720],{"type":46,"value":721},"tm-br",{"type":46,"value":454},{"type":40,"tag":80,"props":724,"children":726},{"className":725},[],[727],{"type":46,"value":460},{"type":46,"value":729}," convention, the\n",{"type":40,"tag":80,"props":731,"children":733},{"className":732},[],[734],{"type":46,"value":735},"ip route get",{"type":46,"value":737},"-before-",{"type":40,"tag":80,"props":739,"children":741},{"className":740},[],[742],{"type":46,"value":743},"ping",{"type":46,"value":745}," loopback gotcha), the DPU-mode\nsurface (DPU \u002F embedded-function vs separated-host \u002F NIC mode, set\nvia ",{"type":40,"tag":80,"props":747,"children":749},{"className":748},[],[750],{"type":46,"value":395},{"type":46,"value":752}," at BFB-install time — a MUTATING burn routed to\n",{"type":40,"tag":75,"props":754,"children":755},{"href":183},[756],{"type":40,"tag":80,"props":757,"children":759},{"className":758},[],[760],{"type":46,"value":190},{"type":46,"value":762},"), the\nhost-side-vs-Arm-side DOCA install distinction, the\nBF3-version overlay on the four-way match owned by\n",{"type":40,"tag":75,"props":764,"children":765},{"href":555},[766],{"type":40,"tag":80,"props":767,"children":769},{"className":768},[],[770],{"type":46,"value":562},{"type":46,"value":772},", the cross-cutting error\ntaxonomy, the observability surface, and the safety policy\n(overlay on\n",{"type":40,"tag":75,"props":774,"children":775},{"href":183},[776],{"type":40,"tag":80,"props":777,"children":779},{"className":778},[],[780],{"type":46,"value":190},{"type":46,"value":782},").",{"type":40,"tag":224,"props":784,"children":785},{},[786,791,793,799,800,806,808,814,815,821,823,829,831,837,839,845,847,853],{"type":40,"tag":80,"props":787,"children":789},{"className":788},[],[790],{"type":46,"value":90},{"type":46,"value":792}," — step-by-step workflows for the in-scope BF3\nlifecycle verbs: ",{"type":40,"tag":80,"props":794,"children":796},{"className":795},[],[797],{"type":46,"value":798},"configure",{"type":46,"value":576},{"type":40,"tag":80,"props":801,"children":803},{"className":802},[],[804],{"type":46,"value":805},"build",{"type":46,"value":807}," (routing stub), ",{"type":40,"tag":80,"props":809,"children":811},{"className":810},[],[812],{"type":46,"value":813},"modify",{"type":46,"value":583},{"type":40,"tag":80,"props":816,"children":818},{"className":817},[],[819],{"type":46,"value":820},"run",{"type":46,"value":822}," (the BFB-install + RShim\u002FTMFIFO bring-up sequence), ",{"type":40,"tag":80,"props":824,"children":826},{"className":825},[],[827],{"type":46,"value":828},"test",{"type":46,"value":830},"\n(the post-BFB readiness smoke), ",{"type":40,"tag":80,"props":832,"children":834},{"className":833},[],[835],{"type":46,"value":836},"debug",{"type":46,"value":838}," (the six-state\n",{"type":40,"tag":80,"props":840,"children":842},{"className":841},[],[843],{"type":46,"value":844},"bluefield-state-classifier",{"type":46,"value":846},"), and the ",{"type":40,"tag":80,"props":848,"children":850},{"className":849},[],[851],{"type":46,"value":852},"Deferred task verbs",{"type":46,"value":854},"\nblock routing app-launch \u002F container \u002F install \u002F library-API \u002F\nhardware-state-change \u002F BF4 questions out to their owning skills.",{"type":40,"tag":49,"props":856,"children":857},{},[858],{"type":46,"value":859},"The skill assumes a target where:",{"type":40,"tag":220,"props":861,"children":862},{},[863,875,890],{"type":40,"tag":224,"props":864,"children":865},{},[866,868,873],{"type":46,"value":867},"a BlueField-3 is physically present and powered, reachable from a\nhost that has the RShim daemon and ",{"type":40,"tag":80,"props":869,"children":871},{"className":870},[],[872],{"type":46,"value":239},{"type":46,"value":874}," tree available,",{"type":40,"tag":224,"props":876,"children":877},{},[878,880,888],{"type":46,"value":879},"the operator has a BFB image downloaded from the public DOCA\nDownloads page (route via\n",{"type":40,"tag":75,"props":881,"children":882},{"href":358},[883],{"type":40,"tag":80,"props":884,"children":886},{"className":885},[],[887],{"type":46,"value":365},{"type":46,"value":889},"),\nand",{"type":40,"tag":224,"props":891,"children":892},{},[893],{"type":46,"value":894},"the operator has an out-of-band path (BMC console, serial-over-LAN,\nor physical UART) to reach the BF3 if a push breaks the Arm OS.",{"type":40,"tag":49,"props":896,"children":897},{},[898,900,904,906,914,916,920,922,930],{"type":46,"value":899},"It does ",{"type":40,"tag":53,"props":901,"children":902},{},[903],{"type":46,"value":256},{"type":46,"value":905}," cover installing DOCA on a host from scratch (that\ngoes through ",{"type":40,"tag":75,"props":907,"children":908},{"href":641},[909],{"type":40,"tag":80,"props":910,"children":912},{"className":911},[],[913],{"type":46,"value":648},{"type":46,"value":915},"), and it does\n",{"type":40,"tag":53,"props":917,"children":918},{},[919],{"type":46,"value":256},{"type":46,"value":921}," cover BlueField-4 (that goes through\n",{"type":40,"tag":75,"props":923,"children":924},{"href":77},[925],{"type":40,"tag":80,"props":926,"children":928},{"className":927},[],[929],{"type":46,"value":85},{"type":46,"value":782},{"type":40,"tag":201,"props":932,"children":934},{"id":933},"loading-order",[935],{"type":46,"value":936},"Loading order",{"type":40,"tag":938,"props":939,"children":940},"ol",{},[941,954,967],{"type":40,"tag":224,"props":942,"children":943},{},[944,946,952],{"type":46,"value":945},"Read this ",{"type":40,"tag":80,"props":947,"children":949},{"className":948},[],[950],{"type":46,"value":951},"SKILL.md",{"type":46,"value":953}," first to confirm the user's question is in\nscope (BF3 platform bring-up over the RShim\u002FBFB path; NOT BF4,\nNOT app-launch, NOT a library-API question).",{"type":40,"tag":224,"props":955,"children":956},{},[957],{"type":40,"tag":53,"props":958,"children":959},{},[960,962,966],{"type":46,"value":961},"For the bring-up contract (RShim\u002FBFB transport, TMFIFO\nchannel, DPU-mode surface, host-vs-Arm install distinction,\nBF3-version overlay, error taxonomy, observability surface, BF3\nsafety overlay), see ",{"type":40,"tag":75,"props":963,"children":964},{"href":121},[965],{"type":46,"value":121},{"type":46,"value":160},{"type":40,"tag":224,"props":968,"children":969},{},[970],{"type":40,"tag":53,"props":971,"children":972},{},[973,975,980,981,986,988,993,994,999,1001,1006,1008,1013,1014,1019,1021,1026,1028,1032],{"type":46,"value":974},"For step-by-step workflows — ",{"type":40,"tag":80,"props":976,"children":978},{"className":977},[],[979],{"type":46,"value":798},{"type":46,"value":576},{"type":40,"tag":80,"props":982,"children":984},{"className":983},[],[985],{"type":46,"value":805},{"type":46,"value":987}," (routing\nstub), ",{"type":40,"tag":80,"props":989,"children":991},{"className":990},[],[992],{"type":46,"value":813},{"type":46,"value":576},{"type":40,"tag":80,"props":995,"children":997},{"className":996},[],[998],{"type":46,"value":820},{"type":46,"value":1000}," (BFB install + RShim\u002FTMFIFO bring-up),\n",{"type":40,"tag":80,"props":1002,"children":1004},{"className":1003},[],[1005],{"type":46,"value":828},{"type":46,"value":1007}," (post-BFB readiness smoke), ",{"type":40,"tag":80,"props":1009,"children":1011},{"className":1010},[],[1012],{"type":46,"value":836},{"type":46,"value":838},{"type":40,"tag":80,"props":1015,"children":1017},{"className":1016},[],[1018],{"type":46,"value":844},{"type":46,"value":1020},"), plus the ",{"type":40,"tag":80,"props":1022,"children":1024},{"className":1023},[],[1025],{"type":46,"value":852},{"type":46,"value":1027},"\nblock — see ",{"type":40,"tag":75,"props":1029,"children":1030},{"href":90},[1031],{"type":46,"value":90},{"type":46,"value":160},{"type":40,"tag":201,"props":1034,"children":1036},{"id":1035},"example-questions-this-skill-answers-well",[1037],{"type":46,"value":1038},"Example questions this skill answers well",{"type":40,"tag":49,"props":1040,"children":1041},{},[1042,1044,1054],{"type":46,"value":1043},"See ",{"type":40,"tag":75,"props":1045,"children":1047},{"href":1046},"references\u002Fdetails.md#example-questions-this-skill-answers-well",[1048],{"type":40,"tag":80,"props":1049,"children":1051},{"className":1050},[],[1052],{"type":46,"value":1053},"references\u002Fdetails.md",{"type":46,"value":160},{"type":40,"tag":201,"props":1056,"children":1058},{"id":1057},"what-this-skill-deliberately-does-not-ship",[1059],{"type":46,"value":1060},"What this skill deliberately does not ship",{"type":40,"tag":49,"props":1062,"children":1063},{},[1064,1065,1074],{"type":46,"value":1043},{"type":40,"tag":75,"props":1066,"children":1068},{"href":1067},"references\u002Fdetails.md#what-this-skill-deliberately-does-not-ship",[1069],{"type":40,"tag":80,"props":1070,"children":1072},{"className":1071},[],[1073],{"type":46,"value":1053},{"type":46,"value":160},{"type":40,"tag":201,"props":1076,"children":1078},{"id":1077},"related-skills",[1079],{"type":46,"value":1080},"Related skills",{"type":40,"tag":49,"props":1082,"children":1083},{},[1084,1085,1094],{"type":46,"value":1043},{"type":40,"tag":75,"props":1086,"children":1088},{"href":1087},"references\u002Fdetails.md#related-skills",[1089],{"type":40,"tag":80,"props":1090,"children":1092},{"className":1091},[],[1093],{"type":46,"value":1053},{"type":46,"value":160},{"items":1096,"total":1196},[1097,1114,1124,1138,1150,1167,1182],{"slug":1098,"name":1098,"fn":1099,"description":1100,"org":1101,"tags":1102,"stars":20,"repoUrl":21,"updatedAt":1113},"accelerated-computing-cudf","accelerate data processing with cuDF","Official NVIDIA-authored guidance for NVIDIA cuDF GPU DataFrames, pandas acceleration, dask-cuDF, ETL, joins, groupby, CSV\u002FParquet I\u002FO, nullable semantics, and multi-GPU DataFrame workloads.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1103,1106,1109,1110],{"name":1104,"slug":1105,"type":15},"Data Analysis","data-analysis",{"name":1107,"slug":1108,"type":15},"Data Engineering","data-engineering",{"name":9,"slug":8,"type":15},{"name":1111,"slug":1112,"type":15},"Performance","performance","2026-07-14T05:28:43.176466",{"slug":1115,"name":1115,"fn":1116,"description":1117,"org":1118,"tags":1119,"stars":20,"repoUrl":21,"updatedAt":1123},"aiq-deploy","deploy and manage NVIDIA AI-Q infrastructure","Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1120,1121,1122],{"name":13,"slug":14,"type":15},{"name":18,"slug":19,"type":15},{"name":9,"slug":8,"type":15},"2026-07-14T05:29:06.667109",{"slug":1125,"name":1125,"fn":1126,"description":1127,"org":1128,"tags":1129,"stars":20,"repoUrl":21,"updatedAt":1137},"aiq-research","conduct deep research with AI-Q","Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1130,1133,1134],{"name":1131,"slug":1132,"type":15},"Agents","agents",{"name":9,"slug":8,"type":15},{"name":1135,"slug":1136,"type":15},"Research","research","2026-07-14T05:28:06.816956",{"slug":1139,"name":1139,"fn":1140,"description":1141,"org":1142,"tags":1143,"stars":20,"repoUrl":21,"updatedAt":1149},"amc-run-sample-calibration","run AMC sample dataset calibration","Run end-to-end calibration on the shipped sample dataset (sdg_08_2_sample_data_010926.zip) against a running AMC microservice. Use when user says 'test sample dataset', 'run sample calibration', 'verify AMC install', or 'launch and test'.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1144,1145,1146],{"name":1104,"slug":1105,"type":15},{"name":9,"slug":8,"type":15},{"name":1147,"slug":1148,"type":15},"Testing","testing","2026-07-17T05:29:03.913266",{"slug":1151,"name":1151,"fn":1152,"description":1153,"org":1154,"tags":1155,"stars":20,"repoUrl":21,"updatedAt":1166},"amc-run-video-calibration","calibrate video datasets with AutoMagicCalib","Calibrate a new dataset from pre-recorded video files via the AutoMagicCalib REST API. Use when user has local MP4s and says 'calibrate my videos', 'run AMC on these videos', or similar. For RTSP\u002Flive streams, use amc-run-rtsp-calibration instead.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1156,1159,1162,1163],{"name":1157,"slug":1158,"type":15},"Automation","automation",{"name":1160,"slug":1161,"type":15},"Imaging","imaging",{"name":9,"slug":8,"type":15},{"name":1164,"slug":1165,"type":15},"Video","video","2026-07-17T05:28:53.905004",{"slug":1168,"name":1168,"fn":1169,"description":1170,"org":1171,"tags":1172,"stars":20,"repoUrl":21,"updatedAt":1181},"amc-setup-calibration-stack","deploy AutoMagicCalib microservice with Docker","Launch AutoMagicCalib microservice and web UI from NGC release images via Docker Compose. Use when user says 'deploy auto calibration', 'launch auto calibration', 'launch AMC', 'start MS+UI', or 'set up auto-magic-calib'. Requires NGC API key.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1173,1174,1177,1178],{"name":13,"slug":14,"type":15},{"name":1175,"slug":1176,"type":15},"Docker","docker",{"name":9,"slug":8,"type":15},{"name":1179,"slug":1180,"type":15},"Operations","operations","2026-07-17T05:28:56.913999",{"slug":1183,"name":1183,"fn":1184,"description":1185,"org":1186,"tags":1187,"stars":20,"repoUrl":21,"updatedAt":1195},"cudaq-guide","develop quantum applications with CUDA-Q","CUDA-Q onboarding guide for installation, test programs, GPU simulation, QPU hardware, and quantum applications.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1188,1189,1192],{"name":9,"slug":8,"type":15},{"name":1190,"slug":1191,"type":15},"Quantum Computing","quantum-computing",{"name":1193,"slug":1194,"type":15},"Simulation","simulation","2026-07-14T05:26:58.898253",305,{"items":1198,"total":1349},[1199,1217,1233,1244,1256,1270,1283,1297,1308,1317,1331,1340],{"slug":1200,"name":1200,"fn":1201,"description":1202,"org":1203,"tags":1204,"stars":1214,"repoUrl":1215,"updatedAt":1216},"nemoclaw-user-guide","retrieve NemoClaw documentation and configuration","Guides human users' AI agents to the NemoClaw docs MCP server and canonical Fern documentation in Markdown form. Use when users ask how to install, configure, operate, troubleshoot, secure, or learn NemoClaw with an AI coding assistant. Trigger keywords - nemoclaw docs, use nemoclaw with ai agent, nemoclaw mcp docs, nemoclaw install help, nemoclaw quickstart, nemoclaw markdown docs, llms.txt, agent skills.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1205,1208,1211],{"name":1206,"slug":1207,"type":15},"Documentation","documentation",{"name":1209,"slug":1210,"type":15},"MCP","mcp",{"name":1212,"slug":1213,"type":15},"Search","search",21777,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNemoClaw","2026-07-20T06:00:01.461044",{"slug":1218,"name":1218,"fn":1219,"description":1220,"org":1221,"tags":1222,"stars":1230,"repoUrl":1231,"updatedAt":1232},"mcore-build-and-dependency","manage Megatron-LM development environments","Container-based dev environment setup and dependency management for Megatron-LM. Covers acquiring and launching the CI container, uv package management, and updating uv.lock.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1223,1226,1227],{"name":1224,"slug":1225,"type":15},"Containers","containers",{"name":13,"slug":14,"type":15},{"name":1228,"slug":1229,"type":15},"Python","python",17049,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FMegatron-LM","2026-07-27T06:06:11.249662",{"slug":1234,"name":1234,"fn":1235,"description":1236,"org":1237,"tags":1238,"stars":1230,"repoUrl":1231,"updatedAt":1243},"mcore-bump-base-image","update NVIDIA PyTorch base images","Bump the NVIDIA PyTorch base image (`nvcr.io\u002Fnvidia\u002Fpytorch:YY.MM-py3`) used by Megatron-LM CI. Covers the two pin sites (GitHub CI in `docker\u002F.ngc_version.dev` and GitLab CI in `.gitlab\u002Fstages\u002F01.build.yml`), the post-bump CI loop (re-run functional tests, refresh golden values, mark broken tests), and the gotchas that bit PRs",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1239,1242],{"name":1240,"slug":1241,"type":15},"CI\u002FCD","ci-cd",{"name":13,"slug":14,"type":15},"2026-07-14T05:25:59.97109",{"slug":1245,"name":1245,"fn":1246,"description":1247,"org":1248,"tags":1249,"stars":1230,"repoUrl":1231,"updatedAt":1255},"mcore-cicd","manage CI\u002FCD pipelines for Megatron-LM","CI\u002FCD reference for Megatron-LM. Covers CI pipeline structure, PR scope labels, triggering internal GitLab CI (which force-pushes the current branch to a pull-request\u002FBRANCH ref — always dry-run and verify the destination first; never run against shared or protected branches), and CI failure investigation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1250,1251,1252],{"name":1240,"slug":1241,"type":15},{"name":13,"slug":14,"type":15},{"name":1253,"slug":1254,"type":15},"GitHub","github","2026-07-27T06:06:12.278222",{"slug":1257,"name":1257,"fn":1258,"description":1259,"org":1260,"tags":1261,"stars":1230,"repoUrl":1231,"updatedAt":1269},"mcore-create-issue","investigate CI failures and create issues","Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1262,1265,1266],{"name":1263,"slug":1264,"type":15},"Debugging","debugging",{"name":1253,"slug":1254,"type":15},{"name":1267,"slug":1268,"type":15},"Triage","triage","2026-07-14T05:25:57.442089",{"slug":1271,"name":1271,"fn":1272,"description":1273,"org":1274,"tags":1275,"stars":1230,"repoUrl":1231,"updatedAt":1282},"mcore-linting-and-formatting","lint and format Megatron-LM code","Linting and formatting for Megatron-LM. Covers running autoformat.sh, tools (ruff, black, isort, pylint, mypy), and code style rules.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1276,1279],{"name":1277,"slug":1278,"type":15},"Best Practices","best-practices",{"name":1280,"slug":1281,"type":15},"Code Analysis","code-analysis","2026-07-14T05:25:56.18433",{"slug":1284,"name":1284,"fn":1285,"description":1286,"org":1287,"tags":1288,"stars":1230,"repoUrl":1231,"updatedAt":1296},"mcore-migrate-gpt-to-hybrid","migrate Megatron-LM models to HybridModel","Migration guide for moving Megatron Core GPTModel checkpoints, model providers, training commands, and layer mappings to HybridModel.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1289,1292,1295],{"name":1290,"slug":1291,"type":15},"Machine Learning","machine-learning",{"name":1293,"slug":1294,"type":15},"Migration","migration",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:11.777011",{"slug":1298,"name":1298,"fn":1299,"description":1300,"org":1301,"tags":1302,"stars":1230,"repoUrl":1231,"updatedAt":1307},"mcore-onboard-gb200-1node-tests","onboard functional tests for GB200","Onboard 1-node GitHub MR functional tests for GB200 from existing mr-scoped 2-node tests.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1303,1306],{"name":1304,"slug":1305,"type":15},"QA","qa",{"name":1147,"slug":1148,"type":15},"2026-07-14T05:25:53.673039",{"slug":1309,"name":1309,"fn":1310,"description":1311,"org":1312,"tags":1313,"stars":1230,"repoUrl":1231,"updatedAt":1316},"mcore-run-on-slurm","launch distributed training jobs on SLURM","How to launch distributed Megatron-LM training jobs on a SLURM cluster. Covers a minimal sbatch skeleton, environment-variable setup for torch.distributed.run, CUDA_DEVICE_MAX_CONNECTIONS rules across hardware and parallelism modes, container conventions, monitoring, and per-rank failure diagnosis.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1314,1315],{"name":13,"slug":14,"type":15},{"name":18,"slug":19,"type":15},"2026-07-14T05:25:49.362534",{"slug":1318,"name":1318,"fn":1319,"description":1320,"org":1321,"tags":1322,"stars":1230,"repoUrl":1231,"updatedAt":1330},"mcore-split-pr","split pull requests to reduce review load","Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1323,1326,1327],{"name":1324,"slug":1325,"type":15},"Code Review","code-review",{"name":1253,"slug":1254,"type":15},{"name":1328,"slug":1329,"type":15},"Pull Requests","pull-requests","2026-07-14T05:26:01.226578",{"slug":1332,"name":1332,"fn":1333,"description":1334,"org":1335,"tags":1336,"stars":1230,"repoUrl":1231,"updatedAt":1339},"mcore-testing","run and manage Megatron-LM tests","Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1337,1338],{"name":1304,"slug":1305,"type":15},{"name":1147,"slug":1148,"type":15},"2026-07-14T05:25:54.928983",{"slug":1341,"name":1341,"fn":1342,"description":1343,"org":1344,"tags":1345,"stars":1230,"repoUrl":1231,"updatedAt":1348},"nightly-sync","manage nightly main-to-dev sync workflows","Domain knowledge for the nightly main-to-dev sync workflow. Covers merge strategy, CI architecture, failure investigation, and known issues.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1346,1347],{"name":1157,"slug":1158,"type":15},{"name":1240,"slug":1241,"type":15},"2026-07-30T05:29:03.275638",496]