[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-nvidia-doca-version":3,"mdc--n8k8d-key":31,"related-repo-nvidia-doca-version":1251,"related-org-nvidia-doca-version":1357},{"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-version","manage and validate DOCA software versions","Use this skill when the user is doing DOCA version handling — detecting the installed release, validating the four-way match across pkg-config doca-common, applications\u002FVERSION, doca_caps --version, and bfver\u002Fmlnx-release on BlueField, reasoning about NGC container tags, looking up whether a capability is on the installed release, or diagnosing build-vs-runtime drift. Trigger even when the user does not explicitly say \"DOCA version\" or \"four-way match\" — typical implicit phrasings include \"program built but does nothing on the wire\", \"undefined reference to a symbol the docs claim exists\", \"DOCA_ERROR_NOT_SUPPORTED at runtime\", \"counter didn't increment\", \"what does `latest` mean for this tag\", or \"is my LTS still supported\". Refuse and route elsewhere for installing or choosing DOCA packages (doca-setup), per-library API\u002Fcapability questions (matching library skill), the cross-library DOCA_ERROR_* taxonomy (doca-programming-guide), or the general debug ladder (doca-debug) — those belong to other skills.\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},"Configuration","configuration","tag",{"name":9,"slug":8,"type":15},{"name":18,"slug":19,"type":15},"Engineering","engineering",2473,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fskills","2026-07-20T06:24:20.42663","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-version","---\nlicense: Apache-2.0\nname: doca-version\ndescription: >\n  Use this skill when the user is doing DOCA version handling —\n  detecting the installed release, validating the four-way match\n  across pkg-config doca-common, applications\u002FVERSION, doca_caps\n  --version, and bfver\u002Fmlnx-release on BlueField, reasoning about\n  NGC container tags, looking up whether a capability is on the\n  installed release, or diagnosing build-vs-runtime drift. Trigger\n  even when the user does not explicitly say \"DOCA version\" or\n  \"four-way match\" — typical implicit phrasings include \"program\n  built but does nothing on the wire\", \"undefined reference to a\n  symbol the docs claim exists\", \"DOCA_ERROR_NOT_SUPPORTED at\n  runtime\", \"counter didn't increment\", \"what does `latest` mean\n  for this tag\", or \"is my LTS still supported\". Refuse and route\n  elsewhere for installing or choosing DOCA packages (doca-setup),\n  per-library API\u002Fcapability questions (matching library skill),\n  the cross-library DOCA_ERROR_* taxonomy (doca-programming-guide),\n  or the general debug ladder (doca-debug) — those belong to other\n  skills.\nmetadata:\n  kind: library\ncompatibility: >\n  No DOCA install required to read this skill (it is an overlay\n  loaded against any DOCA artifact skill); the validation steps\n  within DO require a live DOCA install at \u002Fopt\u002Fmellanox\u002Fdoca.\n---\n\n# DOCA version\n\n**Where to start:** This skill is the bundle's single source of\ntruth for DOCA *version handling*. Open\n[`TASKS.md`](TASKS.md) if the user wants to *do* something with the\nversion (detect \u002F validate \u002F diagnose mismatch); open\n[`CAPABILITIES.md`](CAPABILITIES.md) when the question is *what does\nversion handling cover* (the four-way match, the detection chain,\nNGC semantics, the per-library overlay pattern). Every other skill\nin the bundle that touches version routes here — they MUST NOT\nredefine the rules.\n\n## Example questions this skill answers well\n\nThe CLASSES of version-handling questions this skill is built to\nanswer, each with one worked example. The agent should treat the\n*class* as the load-bearing piece — the worked example is a single\ninstance.\n\n- **\"What DOCA version do I actually have installed?\"** — worked\n  example: *\"the docs say 3.3 but I'm not sure what's on this\n  host\"*. Answered by the canonical detection chain in\n  [`TASKS.md ## configure`](TASKS.md#configure) +\n  [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)\n  source-of-truth table.\n- **\"My program built but does nothing on the wire — is my install\n  consistent?\"** — worked example: *\"`pkg-config --modversion`\n  says 3.3.0; `doca_caps --version` says 3.2.0\"*. Answered by the\n  four-way match rule in\n  [`CAPABILITIES.md ## Version compatibility`](CAPABILITIES.md#version-compatibility)\n  + the partial-install diagnosis in\n  [`TASKS.md ## debug`](TASKS.md#debug).\n- **\"Is this DOCA capability \u002F API \u002F sample on the version I\n  have?\"** — worked example: *\"is the symmetric-RSS hash mode in\n  Flow 2.6.0\"*. Answered by the version-matrix lookup procedure in\n  [`TASKS.md ## test`](TASKS.md#test) (which uses the\n  `version-matrix.json` schema defined in\n  [`doca-structured-tools-contract`](..\u002Fdoca-structured-tools-contract\u002FSKILL.md#schemas)\n  with fallback to per-library docs via\n  [`doca-public-knowledge-map`](..\u002Fdoca-public-knowledge-map\u002FSKILL.md)).\n- **\"Can I run my host package version X against BFB version Y?\"** —\n  worked example: *\"host is 3.3.0 LTS, BlueField BFB is 3.1.0\"*.\n  Answered by the routing to the\n  [DOCA Compatibility Policy](https:\u002F\u002Fdocs.nvidia.com\u002Fdoca\u002Fsdk\u002Fdoca-compatibility-policy\u002Findex.html)\n  documented in\n  [`CAPABILITIES.md ## Version compatibility`](CAPABILITIES.md#version-compatibility).\n- **\"I'm inside the NGC DOCA container — what does the version\n  match look like?\"** — worked example: *\"do I still need to check\n  pkg-config \u002F applications\u002FVERSION \u002F doca_caps separately?\"*.\n  Answered by the NGC container rule in\n  [`CAPABILITIES.md ## Version compatibility`](CAPABILITIES.md#version-compatibility)\n  + the container path in\n  [`TASKS.md ## configure`](TASKS.md#configure).\n- **\"How do I write a per-library version-compatibility section\n  for a new skill?\"** — worked example: *\"adding `doca-comch` to\n  the bundle, what does its `## Version compatibility` look\n  like?\"*. Answered by the per-library overlay pattern in\n  [`CAPABILITIES.md ## Safety policy`](CAPABILITIES.md#safety-policy)\n  + the worked-example template in\n  [`TASKS.md ## modify`](TASKS.md#modify).\n- **\"My `apt list` shows DOCA `3.3.0109`, but `\u002Fetc\u002Fapt\u002Fsources.list.d\u002Fdoca.list`\n  is pinned at `latest` \u002F a different release — is the next\n  `apt install doca-*` going to silently upgrade me?\"** — worked\n  example: *\"I rolled back BFB to 3.1.0105 but my sources still\n  point at the latest channel.\"* Answered by the apt-source\n  consistency precheck in\n  [`TASKS.md ## apt-source consistency`](TASKS.md#apt-source-consistency),\n  which enumerates the three legitimate shapes of a configured\n  DOCA apt source (network URL, local file-repo, RHEL\u002FOEL\n  equivalent) and the *do-not-install-until-the-source-matches*\n  rule that protects pinned installs from accidental drift.\n\n## When to load this skill\n\nLoad this skill whenever version handling is the load-bearing\nconcern. The decision must be made **before** the agent composes\nits first sentence — the activation checklist below is the same\none referenced from\n[`AGENTS.md ## Cross-cutting overlay activation triggers`](..\u002F..\u002FAGENTS.md#cross-cutting-overlay-activation-triggers),\nmirrored here so the activation rule is at hand whenever this skill\nis consulted.\n\n## Agent activation checklist — load this skill at the START of the answer when any cell below is true\n\n| Trigger class | Concrete prompt-side signals (any one fires the overlay) |\n| --- | --- |\n| Direct version question | *\"what DOCA version do I have\"*, *\"is X consistent\"*, *\"is feature Y supported on version Z\"*, *\"can I mix host package version A with BFB version B\"*, *\"is my LTS still supported\"*, *\"what does the version string mean\"* |\n| Container tag question | any prompt that mentions a specific NGC container tag, or asks about `latest`, or asks how to pin a tag in a Dockerfile \u002F pod spec \u002F Compose file. The agent MUST also cite the *\"never invent a tag string from memory, never quote `latest` without confirming it\"* rule from [`CAPABILITIES.md ## Safety policy`](CAPABILITIES.md#safety-policy). |\n| Build vs runtime drift | any debug session where the symptom is *\"the program built fine but DOCA_ERROR_NOT_SUPPORTED at runtime\"*, *\"undefined reference to a symbol the docs say exists\"*, *\"my code does nothing on the wire\"*, *\"counter didn't increment\"* — these are the canonical partial-install symptoms |\n| Upgrade \u002F downgrade plan | the user is planning to upgrade or downgrade DOCA on a host already running other DOCA workloads, or to refresh the BFB on a BlueField pair already attached to a host |\n| Per-artifact cross-link | a per-artifact skill's `## Version compatibility` section cross-links here for the rule body, OR the agent is about to author a new per-artifact skill and needs the overlay template |\n\nWhen any cell above fires, the agent MUST:\n\n1. Cite the **four-source detection chain** from [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes) explicitly in the answer — `pkg-config --modversion doca-common` → `cat \u002Fopt\u002Fmellanox\u002Fdoca\u002Fapplications\u002FVERSION` → `doca_caps --version` → `bfver` plus `cat \u002Fetc\u002Fmlnx-release` (BlueField hosts). Do not paraphrase or summarize the chain; cite the commands by name. Do NOT substitute `mlxprivhost` or `bfb-info` for the BFB leg — those are common hallucinations and the bundle explicitly bans them in [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes).\n2. State the **four-way match rule** from [`CAPABILITIES.md ## Version compatibility`](CAPABILITIES.md#version-compatibility) verbatim if the prompt could possibly involve a mismatch (every deploy-shape question and every debug-shape question can; orientation-shape questions usually cannot).\n3. Refuse to invent a version string. If the agent doesn't have the actual `pkg-config --modversion` output from the user's host, the answer must say so and route to the detection chain — not assert a version from training-data recall.\n\n## Universal version-coherence trigger\n\nWhenever ANOTHER overlay (e.g. [`doca-setup`](..\u002Fdoca-setup\u002FSKILL.md), [`doca-hardware-safety`](..\u002Fdoca-hardware-safety\u002FSKILL.md), [`doca-container-deployment`](..\u002Fdoca-container-deployment\u002FSKILL.md), [`doca-bare-metal-deployment`](..\u002Fdoca-bare-metal-deployment\u002FSKILL.md)) calls a `## test` \u002F `## configure` \u002F `## modify` step that requires *\"the install is healthy\"* or *\"versions are consistent\"*, that step MUST resolve to a citation of this skill's four-source detection chain and four-way match rule. The agent does NOT redefine the rule per-overlay — every step that needs a version verification must route here. This is the *only* place in the bundle that owns the rule body.\n\nDo **not** load this skill for general DOCA orientation, for\ninstall procedures (use [`doca-setup`](..\u002Fdoca-setup\u002FSKILL.md)),\nor for library-specific API questions (use the matching library\nskill).\n\n## What this skill provides\n\nThis is a **thin loader**. The body keeps only the orientation\nneeded to pick the right next file. The substantive\nversion-handling material lives in two companion files:\n\n- `CAPABILITIES.md` — the version-handling surface: the canonical\n  source-of-truth table for version detection, the four-way match\n  rule, NGC container semantics, the per-library overlay pattern,\n  the routing to the DOCA Compatibility Policy, the error\n  taxonomy for version-related failures (pkg-config missing,\n  partial install, BFB\u002Fhost mismatch, NGC mixing), the\n  observability surface (which command to read for which version\n  source), and the safety policy (\"never invent a version, never\n  quote `latest`\").\n- `TASKS.md` — step-by-step workflows for the six in-scope\n  version verbs: `configure` (detect on this host), `build`\n  (build-time match), `modify` (update a version pin in a build\n  manifest), `run` (runtime check), `test` (four-way validation +\n  version-matrix lookup), `debug` (diagnose mismatch \u002F partial\n  install). Plus a `Deferred task verbs` block.\n\n## Loading order\n\n1. Read this `SKILL.md` first to confirm the user's question is in\n   scope.\n2. **For the version-detection sources, four-way match rule, NGC\n   semantics, per-library overlay pattern, error taxonomy,\n   observability, and safety policy, see [CAPABILITIES.md](CAPABILITIES.md).**\n3. **For step-by-step workflows — configure, build, modify, run,\n   test, debug — see [TASKS.md](TASKS.md).**\n\n## Related skills\n\n- [`doca-structured-tools-contract`](..\u002Fdoca-structured-tools-contract\u002FSKILL.md) —\n  the JSON schemas for the helper tools the agent should prefer\n  when present. This skill's `## test` workflow uses the\n  `version-matrix.json` schema defined there; do not redefine the\n  schema here.\n- [`doca-public-knowledge-map`](..\u002Fdoca-public-knowledge-map\u002FSKILL.md) —\n  the routing table to public DOCA docs, including the\n  Compatibility Policy. This skill cites the Compatibility Policy\n  URL once via that map; it does not duplicate the routing.\n- [`doca-setup`](..\u002Fdoca-setup\u002FSKILL.md) — env-side install \u002F\n  verify \u002F NGC container path. This skill assumes its\n  preconditions are satisfied (i.e., something is installed\n  somewhere; the version question is *what was installed and is\n  it consistent*).\n- [`doca-programming-guide`](..\u002Fdoca-programming-guide\u002FSKILL.md) —\n  program-side guidance (quote the version observed, header-wins,\n  capability-discovery rules). The program-side `## Version\n  compatibility` section there is now a 3-5 line redirect to this\n  skill plus the program-side overlay (quote vs assume; never use\n  agent-memory version).\n- [`doca-debug`](..\u002Fdoca-debug\u002FSKILL.md) — the cross-cutting\n  debug ladder. Layer 2 (*version mismatch*) of that ladder is\n  owned by this skill's `## debug` workflow.\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 an overlay loaded against any DOCA artifact skill); the validation steps within DO require a live DOCA install at \u002Fopt\u002Fmellanox\u002Fdoca.\n",{"type":37,"children":38},"root",[39,47,105,112,124,506,512,536,542,731,736,857,863,956,978,984,996,1082,1088,1130,1136],{"type":40,"tag":41,"props":42,"children":43},"element","h1",{"id":4},[44],{"type":45,"value":46},"text","DOCA version",{"type":40,"tag":48,"props":49,"children":50},"p",{},[51,57,59,65,67,78,80,85,87,96,98,103],{"type":40,"tag":52,"props":53,"children":54},"strong",{},[55],{"type":45,"value":56},"Where to start:",{"type":45,"value":58}," This skill is the bundle's single source of\ntruth for DOCA ",{"type":40,"tag":60,"props":61,"children":62},"em",{},[63],{"type":45,"value":64},"version handling",{"type":45,"value":66},". Open\n",{"type":40,"tag":68,"props":69,"children":71},"a",{"href":70},"TASKS.md",[72],{"type":40,"tag":73,"props":74,"children":76},"code",{"className":75},[],[77],{"type":45,"value":70},{"type":45,"value":79}," if the user wants to ",{"type":40,"tag":60,"props":81,"children":82},{},[83],{"type":45,"value":84},"do",{"type":45,"value":86}," something with the\nversion (detect \u002F validate \u002F diagnose mismatch); open\n",{"type":40,"tag":68,"props":88,"children":90},{"href":89},"CAPABILITIES.md",[91],{"type":40,"tag":73,"props":92,"children":94},{"className":93},[],[95],{"type":45,"value":89},{"type":45,"value":97}," when the question is ",{"type":40,"tag":60,"props":99,"children":100},{},[101],{"type":45,"value":102},"what does\nversion handling cover",{"type":45,"value":104}," (the four-way match, the detection chain,\nNGC semantics, the per-library overlay pattern). Every other skill\nin the bundle that touches version routes here — they MUST NOT\nredefine the rules.",{"type":40,"tag":106,"props":107,"children":109},"h2",{"id":108},"example-questions-this-skill-answers-well",[110],{"type":45,"value":111},"Example questions this skill answers well",{"type":40,"tag":48,"props":113,"children":114},{},[115,117,122],{"type":45,"value":116},"The CLASSES of version-handling questions this skill is built to\nanswer, each with one worked example. The agent should treat the\n",{"type":40,"tag":60,"props":118,"children":119},{},[120],{"type":45,"value":121},"class",{"type":45,"value":123}," as the load-bearing piece — the worked example is a single\ninstance.",{"type":40,"tag":125,"props":126,"children":127},"ul",{},[128,170,233,293,329,370,431],{"type":40,"tag":129,"props":130,"children":131},"li",{},[132,137,139,144,146,156,158,168],{"type":40,"tag":52,"props":133,"children":134},{},[135],{"type":45,"value":136},"\"What DOCA version do I actually have installed?\"",{"type":45,"value":138}," — worked\nexample: ",{"type":40,"tag":60,"props":140,"children":141},{},[142],{"type":45,"value":143},"\"the docs say 3.3 but I'm not sure what's on this\nhost\"",{"type":45,"value":145},". Answered by the canonical detection chain in\n",{"type":40,"tag":68,"props":147,"children":149},{"href":148},"TASKS.md#configure",[150],{"type":40,"tag":73,"props":151,"children":153},{"className":152},[],[154],{"type":45,"value":155},"TASKS.md ## configure",{"type":45,"value":157}," +\n",{"type":40,"tag":68,"props":159,"children":161},{"href":160},"CAPABILITIES.md#capabilities-and-modes",[162],{"type":40,"tag":73,"props":163,"children":165},{"className":164},[],[166],{"type":45,"value":167},"CAPABILITIES.md ## Capabilities and modes",{"type":45,"value":169},"\nsource-of-truth table.",{"type":40,"tag":129,"props":171,"children":172},{},[173,178,180,201,203,213],{"type":40,"tag":52,"props":174,"children":175},{},[176],{"type":45,"value":177},"\"My program built but does nothing on the wire — is my install\nconsistent?\"",{"type":45,"value":179}," — worked example: ",{"type":40,"tag":60,"props":181,"children":182},{},[183,185,191,193,199],{"type":45,"value":184},"\"",{"type":40,"tag":73,"props":186,"children":188},{"className":187},[],[189],{"type":45,"value":190},"pkg-config --modversion",{"type":45,"value":192},"\nsays 3.3.0; ",{"type":40,"tag":73,"props":194,"children":196},{"className":195},[],[197],{"type":45,"value":198},"doca_caps --version",{"type":45,"value":200}," says 3.2.0\"",{"type":45,"value":202},". Answered by the\nfour-way match rule in\n",{"type":40,"tag":68,"props":204,"children":206},{"href":205},"CAPABILITIES.md#version-compatibility",[207],{"type":40,"tag":73,"props":208,"children":210},{"className":209},[],[211],{"type":45,"value":212},"CAPABILITIES.md ## Version compatibility",{"type":40,"tag":125,"props":214,"children":215},{},[216],{"type":40,"tag":129,"props":217,"children":218},{},[219,221,231],{"type":45,"value":220},"the partial-install diagnosis in\n",{"type":40,"tag":68,"props":222,"children":224},{"href":223},"TASKS.md#debug",[225],{"type":40,"tag":73,"props":226,"children":228},{"className":227},[],[229],{"type":45,"value":230},"TASKS.md ## debug",{"type":45,"value":232},".",{"type":40,"tag":129,"props":234,"children":235},{},[236,241,242,247,249,259,261,267,269,279,281,291],{"type":40,"tag":52,"props":237,"children":238},{},[239],{"type":45,"value":240},"\"Is this DOCA capability \u002F API \u002F sample on the version I\nhave?\"",{"type":45,"value":179},{"type":40,"tag":60,"props":243,"children":244},{},[245],{"type":45,"value":246},"\"is the symmetric-RSS hash mode in\nFlow 2.6.0\"",{"type":45,"value":248},". Answered by the version-matrix lookup procedure in\n",{"type":40,"tag":68,"props":250,"children":252},{"href":251},"TASKS.md#test",[253],{"type":40,"tag":73,"props":254,"children":256},{"className":255},[],[257],{"type":45,"value":258},"TASKS.md ## test",{"type":45,"value":260}," (which uses the\n",{"type":40,"tag":73,"props":262,"children":264},{"className":263},[],[265],{"type":45,"value":266},"version-matrix.json",{"type":45,"value":268}," schema defined in\n",{"type":40,"tag":68,"props":270,"children":272},{"href":271},"..\u002Fdoca-structured-tools-contract\u002FSKILL.md#schemas",[273],{"type":40,"tag":73,"props":274,"children":276},{"className":275},[],[277],{"type":45,"value":278},"doca-structured-tools-contract",{"type":45,"value":280},"\nwith fallback to per-library docs via\n",{"type":40,"tag":68,"props":282,"children":284},{"href":283},"..\u002Fdoca-public-knowledge-map\u002FSKILL.md",[285],{"type":40,"tag":73,"props":286,"children":288},{"className":287},[],[289],{"type":45,"value":290},"doca-public-knowledge-map",{"type":45,"value":292},").",{"type":40,"tag":129,"props":294,"children":295},{},[296,301,303,308,310,318,320,328],{"type":40,"tag":52,"props":297,"children":298},{},[299],{"type":45,"value":300},"\"Can I run my host package version X against BFB version Y?\"",{"type":45,"value":302}," —\nworked example: ",{"type":40,"tag":60,"props":304,"children":305},{},[306],{"type":45,"value":307},"\"host is 3.3.0 LTS, BlueField BFB is 3.1.0\"",{"type":45,"value":309},".\nAnswered by the routing to the\n",{"type":40,"tag":68,"props":311,"children":315},{"href":312,"rel":313},"https:\u002F\u002Fdocs.nvidia.com\u002Fdoca\u002Fsdk\u002Fdoca-compatibility-policy\u002Findex.html",[314],"nofollow",[316],{"type":45,"value":317},"DOCA Compatibility Policy",{"type":45,"value":319},"\ndocumented in\n",{"type":40,"tag":68,"props":321,"children":322},{"href":205},[323],{"type":40,"tag":73,"props":324,"children":326},{"className":325},[],[327],{"type":45,"value":212},{"type":45,"value":232},{"type":40,"tag":129,"props":330,"children":331},{},[332,337,338,343,345,353],{"type":40,"tag":52,"props":333,"children":334},{},[335],{"type":45,"value":336},"\"I'm inside the NGC DOCA container — what does the version\nmatch look like?\"",{"type":45,"value":179},{"type":40,"tag":60,"props":339,"children":340},{},[341],{"type":45,"value":342},"\"do I still need to check\npkg-config \u002F applications\u002FVERSION \u002F doca_caps separately?\"",{"type":45,"value":344},".\nAnswered by the NGC container rule in\n",{"type":40,"tag":68,"props":346,"children":347},{"href":205},[348],{"type":40,"tag":73,"props":349,"children":351},{"className":350},[],[352],{"type":45,"value":212},{"type":40,"tag":125,"props":354,"children":355},{},[356],{"type":40,"tag":129,"props":357,"children":358},{},[359,361,369],{"type":45,"value":360},"the container path in\n",{"type":40,"tag":68,"props":362,"children":363},{"href":148},[364],{"type":40,"tag":73,"props":365,"children":367},{"className":366},[],[368],{"type":45,"value":155},{"type":45,"value":232},{"type":40,"tag":129,"props":371,"children":372},{},[373,378,379,400,402,412],{"type":40,"tag":52,"props":374,"children":375},{},[376],{"type":45,"value":377},"\"How do I write a per-library version-compatibility section\nfor a new skill?\"",{"type":45,"value":179},{"type":40,"tag":60,"props":380,"children":381},{},[382,384,390,392,398],{"type":45,"value":383},"\"adding ",{"type":40,"tag":73,"props":385,"children":387},{"className":386},[],[388],{"type":45,"value":389},"doca-comch",{"type":45,"value":391}," to\nthe bundle, what does its ",{"type":40,"tag":73,"props":393,"children":395},{"className":394},[],[396],{"type":45,"value":397},"## Version compatibility",{"type":45,"value":399}," look\nlike?\"",{"type":45,"value":401},". Answered by the per-library overlay pattern in\n",{"type":40,"tag":68,"props":403,"children":405},{"href":404},"CAPABILITIES.md#safety-policy",[406],{"type":40,"tag":73,"props":407,"children":409},{"className":408},[],[410],{"type":45,"value":411},"CAPABILITIES.md ## Safety policy",{"type":40,"tag":125,"props":413,"children":414},{},[415],{"type":40,"tag":129,"props":416,"children":417},{},[418,420,430],{"type":45,"value":419},"the worked-example template in\n",{"type":40,"tag":68,"props":421,"children":423},{"href":422},"TASKS.md#modify",[424],{"type":40,"tag":73,"props":425,"children":427},{"className":426},[],[428],{"type":45,"value":429},"TASKS.md ## modify",{"type":45,"value":232},{"type":40,"tag":129,"props":432,"children":433},{},[434,479,480,485,487,497,499,504],{"type":40,"tag":52,"props":435,"children":436},{},[437,439,445,447,453,455,461,463,469,471,477],{"type":45,"value":438},"\"My ",{"type":40,"tag":73,"props":440,"children":442},{"className":441},[],[443],{"type":45,"value":444},"apt list",{"type":45,"value":446}," shows DOCA ",{"type":40,"tag":73,"props":448,"children":450},{"className":449},[],[451],{"type":45,"value":452},"3.3.0109",{"type":45,"value":454},", but ",{"type":40,"tag":73,"props":456,"children":458},{"className":457},[],[459],{"type":45,"value":460},"\u002Fetc\u002Fapt\u002Fsources.list.d\u002Fdoca.list",{"type":45,"value":462},"\nis pinned at ",{"type":40,"tag":73,"props":464,"children":466},{"className":465},[],[467],{"type":45,"value":468},"latest",{"type":45,"value":470}," \u002F a different release — is the next\n",{"type":40,"tag":73,"props":472,"children":474},{"className":473},[],[475],{"type":45,"value":476},"apt install doca-*",{"type":45,"value":478}," going to silently upgrade me?\"",{"type":45,"value":138},{"type":40,"tag":60,"props":481,"children":482},{},[483],{"type":45,"value":484},"\"I rolled back BFB to 3.1.0105 but my sources still\npoint at the latest channel.\"",{"type":45,"value":486}," Answered by the apt-source\nconsistency precheck in\n",{"type":40,"tag":68,"props":488,"children":490},{"href":489},"TASKS.md#apt-source-consistency",[491],{"type":40,"tag":73,"props":492,"children":494},{"className":493},[],[495],{"type":45,"value":496},"TASKS.md ## apt-source consistency",{"type":45,"value":498},",\nwhich enumerates the three legitimate shapes of a configured\nDOCA apt source (network URL, local file-repo, RHEL\u002FOEL\nequivalent) and the ",{"type":40,"tag":60,"props":500,"children":501},{},[502],{"type":45,"value":503},"do-not-install-until-the-source-matches",{"type":45,"value":505},"\nrule that protects pinned installs from accidental drift.",{"type":40,"tag":106,"props":507,"children":509},{"id":508},"when-to-load-this-skill",[510],{"type":45,"value":511},"When to load this skill",{"type":40,"tag":48,"props":513,"children":514},{},[515,517,522,524,534],{"type":45,"value":516},"Load this skill whenever version handling is the load-bearing\nconcern. The decision must be made ",{"type":40,"tag":52,"props":518,"children":519},{},[520],{"type":45,"value":521},"before",{"type":45,"value":523}," the agent composes\nits first sentence — the activation checklist below is the same\none referenced from\n",{"type":40,"tag":68,"props":525,"children":527},{"href":526},"..\u002F..\u002FAGENTS.md#cross-cutting-overlay-activation-triggers",[528],{"type":40,"tag":73,"props":529,"children":531},{"className":530},[],[532],{"type":45,"value":533},"AGENTS.md ## Cross-cutting overlay activation triggers",{"type":45,"value":535},",\nmirrored here so the activation rule is at hand whenever this skill\nis consulted.",{"type":40,"tag":106,"props":537,"children":539},{"id":538},"agent-activation-checklist-load-this-skill-at-the-start-of-the-answer-when-any-cell-below-is-true",[540],{"type":45,"value":541},"Agent activation checklist — load this skill at the START of the answer when any cell below is true",{"type":40,"tag":543,"props":544,"children":545},"table",{},[546,565],{"type":40,"tag":547,"props":548,"children":549},"thead",{},[550],{"type":40,"tag":551,"props":552,"children":553},"tr",{},[554,560],{"type":40,"tag":555,"props":556,"children":557},"th",{},[558],{"type":45,"value":559},"Trigger class",{"type":40,"tag":555,"props":561,"children":562},{},[563],{"type":45,"value":564},"Concrete prompt-side signals (any one fires the overlay)",{"type":40,"tag":566,"props":567,"children":568},"tbody",{},[569,617,660,698,711],{"type":40,"tag":551,"props":570,"children":571},{},[572,578],{"type":40,"tag":573,"props":574,"children":575},"td",{},[576],{"type":45,"value":577},"Direct version question",{"type":40,"tag":573,"props":579,"children":580},{},[581,586,588,593,594,599,600,605,606,611,612],{"type":40,"tag":60,"props":582,"children":583},{},[584],{"type":45,"value":585},"\"what DOCA version do I have\"",{"type":45,"value":587},", ",{"type":40,"tag":60,"props":589,"children":590},{},[591],{"type":45,"value":592},"\"is X consistent\"",{"type":45,"value":587},{"type":40,"tag":60,"props":595,"children":596},{},[597],{"type":45,"value":598},"\"is feature Y supported on version Z\"",{"type":45,"value":587},{"type":40,"tag":60,"props":601,"children":602},{},[603],{"type":45,"value":604},"\"can I mix host package version A with BFB version B\"",{"type":45,"value":587},{"type":40,"tag":60,"props":607,"children":608},{},[609],{"type":45,"value":610},"\"is my LTS still supported\"",{"type":45,"value":587},{"type":40,"tag":60,"props":613,"children":614},{},[615],{"type":45,"value":616},"\"what does the version string mean\"",{"type":40,"tag":551,"props":618,"children":619},{},[620,625],{"type":40,"tag":573,"props":621,"children":622},{},[623],{"type":45,"value":624},"Container tag question",{"type":40,"tag":573,"props":626,"children":627},{},[628,630,635,637,649,651,659],{"type":45,"value":629},"any prompt that mentions a specific NGC container tag, or asks about ",{"type":40,"tag":73,"props":631,"children":633},{"className":632},[],[634],{"type":45,"value":468},{"type":45,"value":636},", or asks how to pin a tag in a Dockerfile \u002F pod spec \u002F Compose file. The agent MUST also cite the ",{"type":40,"tag":60,"props":638,"children":639},{},[640,642,647],{"type":45,"value":641},"\"never invent a tag string from memory, never quote ",{"type":40,"tag":73,"props":643,"children":645},{"className":644},[],[646],{"type":45,"value":468},{"type":45,"value":648}," without confirming it\"",{"type":45,"value":650}," rule from ",{"type":40,"tag":68,"props":652,"children":653},{"href":404},[654],{"type":40,"tag":73,"props":655,"children":657},{"className":656},[],[658],{"type":45,"value":411},{"type":45,"value":232},{"type":40,"tag":551,"props":661,"children":662},{},[663,668],{"type":40,"tag":573,"props":664,"children":665},{},[666],{"type":45,"value":667},"Build vs runtime drift",{"type":40,"tag":573,"props":669,"children":670},{},[671,673,678,679,684,685,690,691,696],{"type":45,"value":672},"any debug session where the symptom is ",{"type":40,"tag":60,"props":674,"children":675},{},[676],{"type":45,"value":677},"\"the program built fine but DOCA_ERROR_NOT_SUPPORTED at runtime\"",{"type":45,"value":587},{"type":40,"tag":60,"props":680,"children":681},{},[682],{"type":45,"value":683},"\"undefined reference to a symbol the docs say exists\"",{"type":45,"value":587},{"type":40,"tag":60,"props":686,"children":687},{},[688],{"type":45,"value":689},"\"my code does nothing on the wire\"",{"type":45,"value":587},{"type":40,"tag":60,"props":692,"children":693},{},[694],{"type":45,"value":695},"\"counter didn't increment\"",{"type":45,"value":697}," — these are the canonical partial-install symptoms",{"type":40,"tag":551,"props":699,"children":700},{},[701,706],{"type":40,"tag":573,"props":702,"children":703},{},[704],{"type":45,"value":705},"Upgrade \u002F downgrade plan",{"type":40,"tag":573,"props":707,"children":708},{},[709],{"type":45,"value":710},"the user is planning to upgrade or downgrade DOCA on a host already running other DOCA workloads, or to refresh the BFB on a BlueField pair already attached to a host",{"type":40,"tag":551,"props":712,"children":713},{},[714,719],{"type":40,"tag":573,"props":715,"children":716},{},[717],{"type":45,"value":718},"Per-artifact cross-link",{"type":40,"tag":573,"props":720,"children":721},{},[722,724,729],{"type":45,"value":723},"a per-artifact skill's ",{"type":40,"tag":73,"props":725,"children":727},{"className":726},[],[728],{"type":45,"value":397},{"type":45,"value":730}," section cross-links here for the rule body, OR the agent is about to author a new per-artifact skill and needs the overlay template",{"type":40,"tag":48,"props":732,"children":733},{},[734],{"type":45,"value":735},"When any cell above fires, the agent MUST:",{"type":40,"tag":737,"props":738,"children":739},"ol",{},[740,824,845],{"type":40,"tag":129,"props":741,"children":742},{},[743,745,750,752,760,762,768,770,776,777,782,783,789,791,797,799,805,807,813,815,823],{"type":45,"value":744},"Cite the ",{"type":40,"tag":52,"props":746,"children":747},{},[748],{"type":45,"value":749},"four-source detection chain",{"type":45,"value":751}," from ",{"type":40,"tag":68,"props":753,"children":754},{"href":160},[755],{"type":40,"tag":73,"props":756,"children":758},{"className":757},[],[759],{"type":45,"value":167},{"type":45,"value":761}," explicitly in the answer — ",{"type":40,"tag":73,"props":763,"children":765},{"className":764},[],[766],{"type":45,"value":767},"pkg-config --modversion doca-common",{"type":45,"value":769}," → ",{"type":40,"tag":73,"props":771,"children":773},{"className":772},[],[774],{"type":45,"value":775},"cat \u002Fopt\u002Fmellanox\u002Fdoca\u002Fapplications\u002FVERSION",{"type":45,"value":769},{"type":40,"tag":73,"props":778,"children":780},{"className":779},[],[781],{"type":45,"value":198},{"type":45,"value":769},{"type":40,"tag":73,"props":784,"children":786},{"className":785},[],[787],{"type":45,"value":788},"bfver",{"type":45,"value":790}," plus ",{"type":40,"tag":73,"props":792,"children":794},{"className":793},[],[795],{"type":45,"value":796},"cat \u002Fetc\u002Fmlnx-release",{"type":45,"value":798}," (BlueField hosts). Do not paraphrase or summarize the chain; cite the commands by name. Do NOT substitute ",{"type":40,"tag":73,"props":800,"children":802},{"className":801},[],[803],{"type":45,"value":804},"mlxprivhost",{"type":45,"value":806}," or ",{"type":40,"tag":73,"props":808,"children":810},{"className":809},[],[811],{"type":45,"value":812},"bfb-info",{"type":45,"value":814}," for the BFB leg — those are common hallucinations and the bundle explicitly bans them in ",{"type":40,"tag":68,"props":816,"children":817},{"href":160},[818],{"type":40,"tag":73,"props":819,"children":821},{"className":820},[],[822],{"type":45,"value":167},{"type":45,"value":232},{"type":40,"tag":129,"props":825,"children":826},{},[827,829,834,835,843],{"type":45,"value":828},"State the ",{"type":40,"tag":52,"props":830,"children":831},{},[832],{"type":45,"value":833},"four-way match rule",{"type":45,"value":751},{"type":40,"tag":68,"props":836,"children":837},{"href":205},[838],{"type":40,"tag":73,"props":839,"children":841},{"className":840},[],[842],{"type":45,"value":212},{"type":45,"value":844}," verbatim if the prompt could possibly involve a mismatch (every deploy-shape question and every debug-shape question can; orientation-shape questions usually cannot).",{"type":40,"tag":129,"props":846,"children":847},{},[848,850,855],{"type":45,"value":849},"Refuse to invent a version string. If the agent doesn't have the actual ",{"type":40,"tag":73,"props":851,"children":853},{"className":852},[],[854],{"type":45,"value":190},{"type":45,"value":856}," output from the user's host, the answer must say so and route to the detection chain — not assert a version from training-data recall.",{"type":40,"tag":106,"props":858,"children":860},{"id":859},"universal-version-coherence-trigger",[861],{"type":45,"value":862},"Universal version-coherence trigger",{"type":40,"tag":48,"props":864,"children":865},{},[866,868,878,879,889,890,900,901,911,913,919,921,927,928,934,936,941,942,947,949,954],{"type":45,"value":867},"Whenever ANOTHER overlay (e.g. ",{"type":40,"tag":68,"props":869,"children":871},{"href":870},"..\u002Fdoca-setup\u002FSKILL.md",[872],{"type":40,"tag":73,"props":873,"children":875},{"className":874},[],[876],{"type":45,"value":877},"doca-setup",{"type":45,"value":587},{"type":40,"tag":68,"props":880,"children":882},{"href":881},"..\u002Fdoca-hardware-safety\u002FSKILL.md",[883],{"type":40,"tag":73,"props":884,"children":886},{"className":885},[],[887],{"type":45,"value":888},"doca-hardware-safety",{"type":45,"value":587},{"type":40,"tag":68,"props":891,"children":893},{"href":892},"..\u002Fdoca-container-deployment\u002FSKILL.md",[894],{"type":40,"tag":73,"props":895,"children":897},{"className":896},[],[898],{"type":45,"value":899},"doca-container-deployment",{"type":45,"value":587},{"type":40,"tag":68,"props":902,"children":904},{"href":903},"..\u002Fdoca-bare-metal-deployment\u002FSKILL.md",[905],{"type":40,"tag":73,"props":906,"children":908},{"className":907},[],[909],{"type":45,"value":910},"doca-bare-metal-deployment",{"type":45,"value":912},") calls a ",{"type":40,"tag":73,"props":914,"children":916},{"className":915},[],[917],{"type":45,"value":918},"## test",{"type":45,"value":920}," \u002F ",{"type":40,"tag":73,"props":922,"children":924},{"className":923},[],[925],{"type":45,"value":926},"## configure",{"type":45,"value":920},{"type":40,"tag":73,"props":929,"children":931},{"className":930},[],[932],{"type":45,"value":933},"## modify",{"type":45,"value":935}," step that requires ",{"type":40,"tag":60,"props":937,"children":938},{},[939],{"type":45,"value":940},"\"the install is healthy\"",{"type":45,"value":806},{"type":40,"tag":60,"props":943,"children":944},{},[945],{"type":45,"value":946},"\"versions are consistent\"",{"type":45,"value":948},", that step MUST resolve to a citation of this skill's four-source detection chain and four-way match rule. The agent does NOT redefine the rule per-overlay — every step that needs a version verification must route here. This is the ",{"type":40,"tag":60,"props":950,"children":951},{},[952],{"type":45,"value":953},"only",{"type":45,"value":955}," place in the bundle that owns the rule body.",{"type":40,"tag":48,"props":957,"children":958},{},[959,961,966,968,976],{"type":45,"value":960},"Do ",{"type":40,"tag":52,"props":962,"children":963},{},[964],{"type":45,"value":965},"not",{"type":45,"value":967}," load this skill for general DOCA orientation, for\ninstall procedures (use ",{"type":40,"tag":68,"props":969,"children":970},{"href":870},[971],{"type":40,"tag":73,"props":972,"children":974},{"className":973},[],[975],{"type":45,"value":877},{"type":45,"value":977},"),\nor for library-specific API questions (use the matching library\nskill).",{"type":40,"tag":106,"props":979,"children":981},{"id":980},"what-this-skill-provides",[982],{"type":45,"value":983},"What this skill provides",{"type":40,"tag":48,"props":985,"children":986},{},[987,989,994],{"type":45,"value":988},"This is a ",{"type":40,"tag":52,"props":990,"children":991},{},[992],{"type":45,"value":993},"thin loader",{"type":45,"value":995},". The body keeps only the orientation\nneeded to pick the right next file. The substantive\nversion-handling material lives in two companion files:",{"type":40,"tag":125,"props":997,"children":998},{},[999,1016],{"type":40,"tag":129,"props":1000,"children":1001},{},[1002,1007,1009,1014],{"type":40,"tag":73,"props":1003,"children":1005},{"className":1004},[],[1006],{"type":45,"value":89},{"type":45,"value":1008}," — the version-handling surface: the canonical\nsource-of-truth table for version detection, the four-way match\nrule, NGC container semantics, the per-library overlay pattern,\nthe routing to the DOCA Compatibility Policy, the error\ntaxonomy for version-related failures (pkg-config missing,\npartial install, BFB\u002Fhost mismatch, NGC mixing), the\nobservability surface (which command to read for which version\nsource), and the safety policy (\"never invent a version, never\nquote ",{"type":40,"tag":73,"props":1010,"children":1012},{"className":1011},[],[1013],{"type":45,"value":468},{"type":45,"value":1015},"\").",{"type":40,"tag":129,"props":1017,"children":1018},{},[1019,1024,1026,1032,1034,1040,1042,1048,1050,1056,1058,1064,1066,1072,1074,1080],{"type":40,"tag":73,"props":1020,"children":1022},{"className":1021},[],[1023],{"type":45,"value":70},{"type":45,"value":1025}," — step-by-step workflows for the six in-scope\nversion verbs: ",{"type":40,"tag":73,"props":1027,"children":1029},{"className":1028},[],[1030],{"type":45,"value":1031},"configure",{"type":45,"value":1033}," (detect on this host), ",{"type":40,"tag":73,"props":1035,"children":1037},{"className":1036},[],[1038],{"type":45,"value":1039},"build",{"type":45,"value":1041},"\n(build-time match), ",{"type":40,"tag":73,"props":1043,"children":1045},{"className":1044},[],[1046],{"type":45,"value":1047},"modify",{"type":45,"value":1049}," (update a version pin in a build\nmanifest), ",{"type":40,"tag":73,"props":1051,"children":1053},{"className":1052},[],[1054],{"type":45,"value":1055},"run",{"type":45,"value":1057}," (runtime check), ",{"type":40,"tag":73,"props":1059,"children":1061},{"className":1060},[],[1062],{"type":45,"value":1063},"test",{"type":45,"value":1065}," (four-way validation +\nversion-matrix lookup), ",{"type":40,"tag":73,"props":1067,"children":1069},{"className":1068},[],[1070],{"type":45,"value":1071},"debug",{"type":45,"value":1073}," (diagnose mismatch \u002F partial\ninstall). Plus a ",{"type":40,"tag":73,"props":1075,"children":1077},{"className":1076},[],[1078],{"type":45,"value":1079},"Deferred task verbs",{"type":45,"value":1081}," block.",{"type":40,"tag":106,"props":1083,"children":1085},{"id":1084},"loading-order",[1086],{"type":45,"value":1087},"Loading order",{"type":40,"tag":737,"props":1089,"children":1090},{},[1091,1104,1117],{"type":40,"tag":129,"props":1092,"children":1093},{},[1094,1096,1102],{"type":45,"value":1095},"Read this ",{"type":40,"tag":73,"props":1097,"children":1099},{"className":1098},[],[1100],{"type":45,"value":1101},"SKILL.md",{"type":45,"value":1103}," first to confirm the user's question is in\nscope.",{"type":40,"tag":129,"props":1105,"children":1106},{},[1107],{"type":40,"tag":52,"props":1108,"children":1109},{},[1110,1112,1116],{"type":45,"value":1111},"For the version-detection sources, four-way match rule, NGC\nsemantics, per-library overlay pattern, error taxonomy,\nobservability, and safety policy, see ",{"type":40,"tag":68,"props":1113,"children":1114},{"href":89},[1115],{"type":45,"value":89},{"type":45,"value":232},{"type":40,"tag":129,"props":1118,"children":1119},{},[1120],{"type":40,"tag":52,"props":1121,"children":1122},{},[1123,1125,1129],{"type":45,"value":1124},"For step-by-step workflows — configure, build, modify, run,\ntest, debug — see ",{"type":40,"tag":68,"props":1126,"children":1127},{"href":70},[1128],{"type":45,"value":70},{"type":45,"value":232},{"type":40,"tag":106,"props":1131,"children":1133},{"id":1132},"related-skills",[1134],{"type":45,"value":1135},"Related skills",{"type":40,"tag":125,"props":1137,"children":1138},{},[1139,1167,1180,1199,1221],{"type":40,"tag":129,"props":1140,"children":1141},{},[1142,1151,1153,1158,1160,1165],{"type":40,"tag":68,"props":1143,"children":1145},{"href":1144},"..\u002Fdoca-structured-tools-contract\u002FSKILL.md",[1146],{"type":40,"tag":73,"props":1147,"children":1149},{"className":1148},[],[1150],{"type":45,"value":278},{"type":45,"value":1152}," —\nthe JSON schemas for the helper tools the agent should prefer\nwhen present. This skill's ",{"type":40,"tag":73,"props":1154,"children":1156},{"className":1155},[],[1157],{"type":45,"value":918},{"type":45,"value":1159}," workflow uses the\n",{"type":40,"tag":73,"props":1161,"children":1163},{"className":1162},[],[1164],{"type":45,"value":266},{"type":45,"value":1166}," schema defined there; do not redefine the\nschema here.",{"type":40,"tag":129,"props":1168,"children":1169},{},[1170,1178],{"type":40,"tag":68,"props":1171,"children":1172},{"href":283},[1173],{"type":40,"tag":73,"props":1174,"children":1176},{"className":1175},[],[1177],{"type":45,"value":290},{"type":45,"value":1179}," —\nthe routing table to public DOCA docs, including the\nCompatibility Policy. This skill cites the Compatibility Policy\nURL once via that map; it does not duplicate the routing.",{"type":40,"tag":129,"props":1181,"children":1182},{},[1183,1191,1193,1198],{"type":40,"tag":68,"props":1184,"children":1185},{"href":870},[1186],{"type":40,"tag":73,"props":1187,"children":1189},{"className":1188},[],[1190],{"type":45,"value":877},{"type":45,"value":1192}," — env-side install \u002F\nverify \u002F NGC container path. This skill assumes its\npreconditions are satisfied (i.e., something is installed\nsomewhere; the version question is ",{"type":40,"tag":60,"props":1194,"children":1195},{},[1196],{"type":45,"value":1197},"what was installed and is\nit consistent",{"type":45,"value":292},{"type":40,"tag":129,"props":1200,"children":1201},{},[1202,1212,1214,1219],{"type":40,"tag":68,"props":1203,"children":1205},{"href":1204},"..\u002Fdoca-programming-guide\u002FSKILL.md",[1206],{"type":40,"tag":73,"props":1207,"children":1209},{"className":1208},[],[1210],{"type":45,"value":1211},"doca-programming-guide",{"type":45,"value":1213}," —\nprogram-side guidance (quote the version observed, header-wins,\ncapability-discovery rules). The program-side ",{"type":40,"tag":73,"props":1215,"children":1217},{"className":1216},[],[1218],{"type":45,"value":397},{"type":45,"value":1220}," section there is now a 3-5 line redirect to this\nskill plus the program-side overlay (quote vs assume; never use\nagent-memory version).",{"type":40,"tag":129,"props":1222,"children":1223},{},[1224,1234,1236,1241,1243,1249],{"type":40,"tag":68,"props":1225,"children":1227},{"href":1226},"..\u002Fdoca-debug\u002FSKILL.md",[1228],{"type":40,"tag":73,"props":1229,"children":1231},{"className":1230},[],[1232],{"type":45,"value":1233},"doca-debug",{"type":45,"value":1235}," — the cross-cutting\ndebug ladder. Layer 2 (",{"type":40,"tag":60,"props":1237,"children":1238},{},[1239],{"type":45,"value":1240},"version mismatch",{"type":45,"value":1242},") of that ladder is\nowned by this skill's ",{"type":40,"tag":73,"props":1244,"children":1246},{"className":1245},[],[1247],{"type":45,"value":1248},"## debug",{"type":45,"value":1250}," workflow.",{"items":1252,"total":1356},[1253,1270,1284,1298,1310,1327,1342],{"slug":1254,"name":1254,"fn":1255,"description":1256,"org":1257,"tags":1258,"stars":20,"repoUrl":21,"updatedAt":1269},"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},[1259,1262,1265,1266],{"name":1260,"slug":1261,"type":15},"Data Analysis","data-analysis",{"name":1263,"slug":1264,"type":15},"Data Engineering","data-engineering",{"name":9,"slug":8,"type":15},{"name":1267,"slug":1268,"type":15},"Performance","performance","2026-07-14T05:28:43.176466",{"slug":1271,"name":1271,"fn":1272,"description":1273,"org":1274,"tags":1275,"stars":20,"repoUrl":21,"updatedAt":1283},"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},[1276,1279,1282],{"name":1277,"slug":1278,"type":15},"Deployment","deployment",{"name":1280,"slug":1281,"type":15},"Infrastructure","infrastructure",{"name":9,"slug":8,"type":15},"2026-07-14T05:29:06.667109",{"slug":1285,"name":1285,"fn":1286,"description":1287,"org":1288,"tags":1289,"stars":20,"repoUrl":21,"updatedAt":1297},"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},[1290,1293,1294],{"name":1291,"slug":1292,"type":15},"Agents","agents",{"name":9,"slug":8,"type":15},{"name":1295,"slug":1296,"type":15},"Research","research","2026-07-14T05:28:06.816956",{"slug":1299,"name":1299,"fn":1300,"description":1301,"org":1302,"tags":1303,"stars":20,"repoUrl":21,"updatedAt":1309},"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},[1304,1305,1306],{"name":1260,"slug":1261,"type":15},{"name":9,"slug":8,"type":15},{"name":1307,"slug":1308,"type":15},"Testing","testing","2026-07-17T05:29:03.913266",{"slug":1311,"name":1311,"fn":1312,"description":1313,"org":1314,"tags":1315,"stars":20,"repoUrl":21,"updatedAt":1326},"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},[1316,1319,1322,1323],{"name":1317,"slug":1318,"type":15},"Automation","automation",{"name":1320,"slug":1321,"type":15},"Imaging","imaging",{"name":9,"slug":8,"type":15},{"name":1324,"slug":1325,"type":15},"Video","video","2026-07-17T05:28:53.905004",{"slug":1328,"name":1328,"fn":1329,"description":1330,"org":1331,"tags":1332,"stars":20,"repoUrl":21,"updatedAt":1341},"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},[1333,1334,1337,1338],{"name":1277,"slug":1278,"type":15},{"name":1335,"slug":1336,"type":15},"Docker","docker",{"name":9,"slug":8,"type":15},{"name":1339,"slug":1340,"type":15},"Operations","operations","2026-07-17T05:28:56.913999",{"slug":1343,"name":1343,"fn":1344,"description":1345,"org":1346,"tags":1347,"stars":20,"repoUrl":21,"updatedAt":1355},"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},[1348,1349,1352],{"name":9,"slug":8,"type":15},{"name":1350,"slug":1351,"type":15},"Quantum Computing","quantum-computing",{"name":1353,"slug":1354,"type":15},"Simulation","simulation","2026-07-14T05:26:58.898253",305,{"items":1358,"total":1509},[1359,1377,1393,1404,1416,1430,1443,1457,1468,1477,1491,1500],{"slug":1360,"name":1360,"fn":1361,"description":1362,"org":1363,"tags":1364,"stars":1374,"repoUrl":1375,"updatedAt":1376},"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},[1365,1368,1371],{"name":1366,"slug":1367,"type":15},"Documentation","documentation",{"name":1369,"slug":1370,"type":15},"MCP","mcp",{"name":1372,"slug":1373,"type":15},"Search","search",21777,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNemoClaw","2026-07-20T06:00:01.461044",{"slug":1378,"name":1378,"fn":1379,"description":1380,"org":1381,"tags":1382,"stars":1390,"repoUrl":1391,"updatedAt":1392},"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},[1383,1386,1387],{"name":1384,"slug":1385,"type":15},"Containers","containers",{"name":1277,"slug":1278,"type":15},{"name":1388,"slug":1389,"type":15},"Python","python",17049,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FMegatron-LM","2026-07-27T06:06:11.249662",{"slug":1394,"name":1394,"fn":1395,"description":1396,"org":1397,"tags":1398,"stars":1390,"repoUrl":1391,"updatedAt":1403},"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},[1399,1402],{"name":1400,"slug":1401,"type":15},"CI\u002FCD","ci-cd",{"name":1277,"slug":1278,"type":15},"2026-07-14T05:25:59.97109",{"slug":1405,"name":1405,"fn":1406,"description":1407,"org":1408,"tags":1409,"stars":1390,"repoUrl":1391,"updatedAt":1415},"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},[1410,1411,1412],{"name":1400,"slug":1401,"type":15},{"name":1277,"slug":1278,"type":15},{"name":1413,"slug":1414,"type":15},"GitHub","github","2026-07-27T06:06:12.278222",{"slug":1417,"name":1417,"fn":1418,"description":1419,"org":1420,"tags":1421,"stars":1390,"repoUrl":1391,"updatedAt":1429},"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},[1422,1425,1426],{"name":1423,"slug":1424,"type":15},"Debugging","debugging",{"name":1413,"slug":1414,"type":15},{"name":1427,"slug":1428,"type":15},"Triage","triage","2026-07-14T05:25:57.442089",{"slug":1431,"name":1431,"fn":1432,"description":1433,"org":1434,"tags":1435,"stars":1390,"repoUrl":1391,"updatedAt":1442},"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},[1436,1439],{"name":1437,"slug":1438,"type":15},"Best Practices","best-practices",{"name":1440,"slug":1441,"type":15},"Code Analysis","code-analysis","2026-07-14T05:25:56.18433",{"slug":1444,"name":1444,"fn":1445,"description":1446,"org":1447,"tags":1448,"stars":1390,"repoUrl":1391,"updatedAt":1456},"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},[1449,1452,1455],{"name":1450,"slug":1451,"type":15},"Machine Learning","machine-learning",{"name":1453,"slug":1454,"type":15},"Migration","migration",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:11.777011",{"slug":1458,"name":1458,"fn":1459,"description":1460,"org":1461,"tags":1462,"stars":1390,"repoUrl":1391,"updatedAt":1467},"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},[1463,1466],{"name":1464,"slug":1465,"type":15},"QA","qa",{"name":1307,"slug":1308,"type":15},"2026-07-14T05:25:53.673039",{"slug":1469,"name":1469,"fn":1470,"description":1471,"org":1472,"tags":1473,"stars":1390,"repoUrl":1391,"updatedAt":1476},"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},[1474,1475],{"name":1277,"slug":1278,"type":15},{"name":1280,"slug":1281,"type":15},"2026-07-14T05:25:49.362534",{"slug":1478,"name":1478,"fn":1479,"description":1480,"org":1481,"tags":1482,"stars":1390,"repoUrl":1391,"updatedAt":1490},"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},[1483,1486,1487],{"name":1484,"slug":1485,"type":15},"Code Review","code-review",{"name":1413,"slug":1414,"type":15},{"name":1488,"slug":1489,"type":15},"Pull Requests","pull-requests","2026-07-14T05:26:01.226578",{"slug":1492,"name":1492,"fn":1493,"description":1494,"org":1495,"tags":1496,"stars":1390,"repoUrl":1391,"updatedAt":1499},"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},[1497,1498],{"name":1464,"slug":1465,"type":15},{"name":1307,"slug":1308,"type":15},"2026-07-14T05:25:54.928983",{"slug":1501,"name":1501,"fn":1502,"description":1503,"org":1504,"tags":1505,"stars":1390,"repoUrl":1391,"updatedAt":1508},"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},[1506,1507],{"name":1317,"slug":1318,"type":15},{"name":1400,"slug":1401,"type":15},"2026-07-30T05:29:03.275638",496]