[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-nvidia-doca-common":3,"mdc-qxdi61-key":31,"related-repo-nvidia-doca-common":1853,"related-org-nvidia-doca-common":1959},{"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-common","program DOCA primitives on BlueField","Use this skill whenever the user is doing hands-on DOCA programming on a BlueField DPU or ConnectX NIC and needs the foundation primitives every per-library context rests on — walking the doca_ctx lifecycle, discovering doca_dev \u002F doca_devinfo and gating on doca_*_cap_* before trusting a feature, wiring doca_mmap \u002F doca_buf_inventory \u002F doca_buf for zero-copy I\u002FO across libraries, driving doca_pe for completions, or DOCA Log's two-tier (--sdk-log-level vs app-side) model. Trigger even when the user does not say \"DOCA Common\" — typical implicit phrasings include \"my tasks submit but nothing completes\", \"DOCA_ERROR_BAD_STATE from doca_ctx_start\", \"--sdk-log-level does nothing for my DOCA_LOG_DBG lines\", \"share a buf between doca_dma and doca_rdma\", or \"crashes far from the offending line\". Refuse and route elsewhere for per-library questions in isolation (load doca-flow \u002F doca-rdma \u002F doca-eth alongside), installing DOCA (doca-setup), or doc lookup (doca-public-knowledge-map).\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,14,17],{"name":9,"slug":8,"type":13},"tag",{"name":15,"slug":16,"type":13},"Engineering","engineering",{"name":18,"slug":19,"type":13},"API Development","api-development",2473,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fskills","2026-07-20T06:24:09.310556","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-common","---\nlicense: Apache-2.0\nname: doca-common\ndescription: >\n  Use this skill whenever the user is doing hands-on DOCA programming\n  on a BlueField DPU or ConnectX NIC and needs the foundation\n  primitives every per-library context rests on — walking the\n  doca_ctx lifecycle, discovering doca_dev \u002F doca_devinfo and gating\n  on doca_*_cap_* before trusting a feature, wiring doca_mmap \u002F\n  doca_buf_inventory \u002F doca_buf for zero-copy I\u002FO across libraries,\n  driving doca_pe for completions, or DOCA Log's two-tier\n  (--sdk-log-level vs app-side) model. Trigger even when the user\n  does not say \"DOCA Common\" — typical implicit phrasings include\n  \"my tasks submit but nothing completes\", \"DOCA_ERROR_BAD_STATE\n  from doca_ctx_start\", \"--sdk-log-level does nothing for my\n  DOCA_LOG_DBG lines\", \"share a buf between doca_dma and doca_rdma\",\n  or \"crashes far from the offending line\". Refuse and route\n  elsewhere for per-library questions in isolation (load doca-flow \u002F\n  doca-rdma \u002F doca-eth alongside), installing DOCA (doca-setup), or\n  doc lookup (doca-public-knowledge-map).\nmetadata:\n  kind: library\ncompatibility: >\n  Requires DOCA SDK installed at \u002Fopt\u002Fmellanox\u002Fdoca on Linux (Ubuntu\n  22.04\u002F24.04 or RHEL\u002FSLES) with a BlueField DPU or ConnectX NIC\n  attached. doca-common is present on every healthy DOCA install;\n  reads the user's local install via `pkg-config --modversion\n  doca-common` and inspects \u002Fopt\u002Fmellanox\u002Fdoca\u002F{lib,include,samples,applications}.\n---\n\n# DOCA Common\n\n**Where to start:** This skill is the **foundation every DOCA app\nloads first** — before doca-flow, doca-rdma, doca-eth, doca-comch, or\nany other higher-level library. Every `doca_\u003Clibrary>_*` context is\nbuilt on top of `doca_ctx`, every device handle is a `doca_dev`\ndiscovered through `doca_devinfo`, every zero-copy buffer is a\n`doca_buf` from a `doca_buf_inventory` over a `doca_mmap`, every\ntask completion drains through a `doca_pe`, and every log line emits\nthrough `doca_log`. Open [`CAPABILITIES.md`](CAPABILITIES.md) when\nthe question is *what does Common express* on this install; open\n[`TASKS.md`](TASKS.md) when the user wants to *do* something\n(configure \u002F build \u002F modify \u002F run \u002F test \u002F debug). If the user has\nnot installed DOCA yet, route to\n[`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md) first. If the user is\nalready past the foundation and asking a library-specific question\n(e.g. *\"how do I program a Flow pipe\"*), load the matching per-library\nskill alongside this one — they cross-link back here for the shared\nprimitives.\n\n## Example questions this skill answers well\n\nThe CLASSES of doca-common questions this skill is built to answer,\neach with one worked example. The agent should treat the *class* as\nthe load-bearing piece — the worked example is a single instance.\n\n- **\"What is the doca-common foundation I have to set up BEFORE I\n  open a doca-flow \u002F doca-rdma \u002F doca-eth \u002F … context?\"** — worked\n  example: *\"I'm starting a brand-new DOCA Flow program on\n  BlueField-3; what's the doca-common skeleton I need before I open\n  the Flow port?\"*. Answered by the universal foundation walk in\n  [`TASKS.md ## configure`](TASKS.md#configure) +\n  [`CAPABILITIES.md ## ctx`](CAPABILITIES.md#ctx) +\n  [`CAPABILITIES.md ## dev`](CAPABILITIES.md#dev) +\n  [`CAPABILITIES.md ## progress engine`](CAPABILITIES.md#progress-engine).\n- **\"How do I discover a device and gate on its capabilities before\n  trusting the public docs?\"** — worked example: *\"I want to use\n  `doca_eth_txq` but the docs hint at a feature only on certain\n  firmware bands\"*. Answered by the capability-discovery rule\n  (`doca_devinfo_create_list` → `doca_*_cap_*` against the active\n  `doca_devinfo` is the runtime authority) in\n  [`CAPABILITIES.md ## dev`](CAPABILITIES.md#dev) +\n  [`TASKS.md ## use`](TASKS.md#use).\n- **\"What's the doca_buf \u002F doca_mmap \u002F doca_buf_inventory wiring\n  for zero-copy I\u002FO, and what's the lifecycle order?\"** — worked\n  example: *\"I want to register a user-space buffer with my device,\n  carve it into N data-plane buffers, and reference-count them\n  across multiple DOCA libraries\"*. Answered by the zero-copy\n  buffer model in\n  [`CAPABILITIES.md ## buf`](CAPABILITIES.md#buf) +\n  the buffer-lifecycle walk in\n  [`TASKS.md ## configure`](TASKS.md#configure) +\n  [`TASKS.md ## use`](TASKS.md#use).\n- **\"How does the progress engine work and where do I have to call\n  it?\"** — worked example: *\"my doca_rdma task submits cleanly but\n  nothing completes — what loop am I missing?\"*. Answered by the PE\n  surface in\n  [`CAPABILITIES.md ## progress engine`](CAPABILITIES.md#progress-engine)\n  + the run-loop pattern in [`TASKS.md ## run`](TASKS.md#run).\n- **\"Why don't my DOCA log lines appear at the level I expect, and\n  what's the difference between `--sdk-log-level` and the app-side\n  setter?\"** — worked example: *\"I set `--sdk-log-level DEBUG`, my\n  own `DOCA_LOG_DBG` lines still don't print\"*. Answered by the\n  two-tier log model in [`CAPABILITIES.md ## log`](CAPABILITIES.md#log)\n  + the tier-flip iteration in [`TASKS.md ## log`](TASKS.md#log).\n- **\"What does this `DOCA_ERROR_*` from a `doca_buf_*` \u002F `doca_ctx_*`\n  \u002F `doca_dev_*` \u002F `doca_pe_*` \u002F `doca_log_*` call mean?\"** —\n  worked example: *\"`DOCA_ERROR_BAD_STATE` from `doca_ctx_start`\"*.\n  Answered by the Common overlay on the cross-library `DOCA_ERROR_*`\n  taxonomy in\n  [`CAPABILITIES.md ## Error taxonomy`](CAPABILITIES.md#error-taxonomy)\n  + the layered ladder in\n  [`TASKS.md ## debug`](TASKS.md#debug) that escalates to\n  [`doca-debug`](..\u002F..\u002Fdoca-debug\u002FSKILL.md).\n\n## Audience\n\nThis skill serves **every external developer building applications\nthat consume any DOCA library** — i.e., users whose code calls *any*\n`doca_*` symbol (directly in C\u002FC++, or through FFI\u002Fbindings from\nanother language). Whether the user's primary library is doca-flow,\ndoca-rdma, doca-eth, doca-comch, doca-dma, doca-rmax, doca-sha,\ndoca-aes-gcm, doca-erasure-coding, or any other, the doca-common\nsurface is *under* it and the user will hit `doca_buf`, `doca_ctx`,\n`doca_dev`, `doca_pe`, and `doca_log` as part of the first-app\njourney. It is *not* for NVIDIA developers contributing to DOCA\nCommon itself.\n\n## Language scope\n\nDOCA Common ships as a C library with `pkg-config` module name\n`doca-common`. The shipped samples that demonstrate Common primitives\nlive *inside* every per-library samples tree (any\n`\u002Fopt\u002Fmellanox\u002Fdoca\u002Fsamples\u002F\u003Clibrary>\u002F\u003Csample>\u002F*_main.c` is a worked\nexample of the universal foundation — `doca_devinfo_create_list`\n→ `doca_dev_open` → per-library `doca_ctx` create → `doca_pe_create`\n→ `doca_pe_connect_ctx` → `doca_ctx_start` → submit work → drive\n`doca_pe_progress` → drain completions → `doca_ctx_stop` → destroy).\nC and C++ consumers are the canonical case and the worked examples\nin `TASKS.md` assume that path. Other-language consumers (Rust, Go,\nPython, …) consume the same `*.so` through FFI or language-specific\nbindings; the skill's contribution in that case is to keep the\nuniversal foundation walk, the lifecycle, the capability-discovery\nrule, the PE-drives-completion rule, and the two-tier log model\nlanguage-neutral, and to route the agent to the public C ABI as the\nauthoritative surface that any wrapper will eventually call.\n\n## When to load this skill\n\nLoad this skill whenever the user is doing **any** hands-on DOCA\nwork — it is the foundation. Concretely:\n\n- Setting up the universal DOCA-side skeleton before opening any\n  per-library context (Flow, RDMA, Eth, Comch, DMA, Rmax, …).\n- Discovering devices and representors and gating capability use\n  on the active `doca_devinfo` via the `doca_*_cap_*` family.\n- Wiring `doca_mmap` + `doca_buf_inventory` + `doca_buf` for\n  zero-copy I\u002FO that crosses libraries (e.g. doca-eth feeds\n  doca-dma feeds doca-rdma — they share the same buf surface).\n- Driving the progress engine (`doca_pe_create` \u002F\n  `doca_pe_connect_ctx` \u002F `doca_pe_progress`) — the universal\n  task-completion drain every DOCA Core context relies on.\n- Wiring DOCA Log into a fresh app or modifying a shipped sample to\n  add the user's own per-component log lines via the two-tier\n  (`--sdk-log-level` vs app-side registry) model.\n- Debugging a `DOCA_ERROR_*` returned from any `doca_buf_*` \u002F\n  `doca_ctx_*` \u002F `doca_dev_*` \u002F `doca_pe_*` \u002F `doca_log_*` call —\n  the Common surface is where most lifecycle \u002F capability \u002F\n  permission errors first surface for higher-level libraries.\n- Designing or extending non-C bindings (Rust, Go, Python, …) that\n  wrap any DOCA library — for the universal foundation surface\n  (buf, ctx, dev, pe, log) the wrapper has to expose first.\n\nDo **not** load this skill for library-specific Flow, RDMA, Eth,\nComch, DMA, Rmax, … questions in isolation — load the matching\nper-library skill alongside this one. Do **not** load this skill for\ngeneral DOCA orientation, install of DOCA itself, or\n*\"where do I find docs\"*. For those, use\n[`doca-public-knowledge-map`](..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md)\nor [`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md).\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 Common material\nlives in two companion files:\n\n- `CAPABILITIES.md` — what doca-common expresses on this install:\n  the `## Capabilities and modes` overview of the universal\n  primitives every DOCA application touches; the five subsystem\n  H2s (`## log`, `## buf`, `## ctx`, `## dev`, `## progress\n  engine`) that own the per-primitive surface; the\n  `## Version compatibility` doca-common-specific overlay;\n  the `## Error taxonomy` Common-side view of the universal\n  `DOCA_ERROR_*` set; the `## Observability` surface (logs, PE\n  events, capability snapshots); and the `## Safety policy` overlay\n  on the bundle-wide hardware-safety meta-policy.\n- `TASKS.md` — step-by-step workflows for the universal verbs\n  (`configure`, `build`, `modify`, `run`, `test`, `debug`, `use`)\n  PLUS a `## log` verb-side that covers the two-tier log model in\n  workflow form. Plus a `Deferred task verbs` block that points\n  install \u002F deploy \u002F rollback questions at the right next skill.\n\nThe skill assumes a host or BlueField where DOCA is already\ninstalled at the standard location and the user has the privileges\ntheir public install profile expects. It does not cover installing\nDOCA — that path goes through\n[`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md).\n\n## What this skill deliberately does not ship\n\nThis skill is **agent guidance**, not a samples or templates\nbundle. To keep the boundary clean, it deliberately does not\ncontain — and pull requests should not add:\n\n- **Pre-written DOCA application source code, in any language.**\n  The verified Common usage shows up inside every shipped DOCA\n  sample at `\u002Fopt\u002Fmellanox\u002Fdoca\u002Fsamples\u002F\u003Clibrary>\u002F\u003Csample>\u002F*_main.c`\n  and inside every shipped reference application. The agent's job\n  is to route the user to those files and prescribe a minimum-diff\n  modification on them via the universal modify-a-sample workflow\n  in\n  [`doca-programming-guide`](..\u002F..\u002Fdoca-programming-guide\u002FSKILL.md).\n- **Standalone build manifests** (`meson.build`,\n  `CMakeLists.txt`, `Cargo.toml`, `setup.py`, `go.mod`, …) parked\n  inside the skill. The agent constructs the build manifest *in\n  the user's project directory* against the user's installed DOCA,\n  where `pkg-config --modversion doca-common` is the source of\n  truth.\n- **A `samples\u002F`, `bindings\u002F`, or `reference\u002F` subtree** of any\n  kind. A mock or incomplete artifact in this skill's tree, even\n  one labeled \"reference\", is misleading: users will read it as\n  buildable.\n\n## Loading order\n\n1. Read this `SKILL.md` first to confirm the user's question is in\n   scope.\n2. **For the universal primitives (`log` \u002F `buf` \u002F `ctx` \u002F `dev` \u002F\n   `progress engine`), the `pkg-config --modversion doca-common`\n   anchor, the Common error overlay, observability, and safety\n   policy, see [CAPABILITIES.md](CAPABILITIES.md).**\n3. **For step-by-step workflows — configure, build, modify, run,\n   test, debug, use, log — see [TASKS.md](TASKS.md).**\n\nBoth companion files cross-link to each other,\n[`doca-version`](..\u002F..\u002Fdoca-version\u002FSKILL.md) for the canonical\nversion-handling rules,\n[`doca-programming-guide`](..\u002F..\u002Fdoca-programming-guide\u002FSKILL.md)\nfor the universal modify-a-shipped-sample workflow and the\ncross-library `DOCA_ERROR_*` taxonomy,\n[`doca-debug`](..\u002F..\u002Fdoca-debug\u002FSKILL.md) for the cross-cutting\ndebug ladder, and\n[`doca-public-knowledge-map`](..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md)\nwhenever the right answer is \"look it up in the public docs or the\ninstalled package layout\" rather than \"Common-specific guidance\".\n\n## Related skills\n\n- [`doca-public-knowledge-map`](..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md) —\n  the routing table for every public DOCA documentation source and\n  the on-disk layout of an installed DOCA package. Always available\n  alongside this skill; this skill expects to be able to defer\n  documentation-finding and install-layout questions there instead\n  of duplicating them.\n- [`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md) — env preparation,\n  install verification, and the *I have no install yet* path with\n  the public NGC DOCA container (`nvcr.io\u002Fnvidia\u002Fdoca\u002Fdoca`) as the\n  universal Stage-1 fallback. This skill assumes its preconditions\n  are satisfied.\n- [`doca-version`](..\u002F..\u002Fdoca-version\u002FSKILL.md) — canonical DOCA\n  version-handling rules (four-way match, NGC semantics,\n  headers-win-over-docs). `pkg-config --modversion doca-common` is\n  the build-time anchor *every* DOCA install carries; this skill's\n  `## Version compatibility` overlays the Common-specific notes on\n  top.\n- [`doca-programming-guide`](..\u002F..\u002Fdoca-programming-guide\u002FSKILL.md) —\n  general DOCA programming patterns shared by every library: the\n  canonical `pkg-config` + meson build pattern, the universal\n  modify-a-shipped-sample first-app workflow, the universal\n  lifecycle, the cross-library `DOCA_ERROR_*` taxonomy, and the\n  program-side debug order. This skill is the *primitives* layer\n  the programming-guide patterns rest on.\n- [`doca-debug`](..\u002F..\u002Fdoca-debug\u002FSKILL.md) — the cross-cutting\n  debug ladder (install \u002F version \u002F build \u002F link \u002F runtime \u002F\n  program \u002F driver) and the verbosity-escalation surface. DOCA Log\n  is the foundation `doca-debug` builds its runtime-debug story on;\n  this skill is where the two-tier log model and the universal\n  lifecycle errors first surface, and `doca-debug` cross-links here\n  for both.\n- [`doca-structured-tools-contract`](..\u002F..\u002Fdoca-structured-tools-contract\u002FSKILL.md) —\n  the bundle's structured-tools precedence rule (detect \u002F prefer \u002F\n  fall back \u002F report). The Command appendix in\n  [TASKS.md](TASKS.md) honors this contract.\n- [`doca-hardware-safety`](..\u002F..\u002Fdoca-hardware-safety\u002FSKILL.md) —\n  the cross-cutting hardware-safety meta-policy this skill's\n  `## Safety policy` overlays.\n- Per-library skills (`doca-flow`, `doca-rdma`, `doca-eth`,\n  `doca-comch`, `doca-dma`, `doca-rmax`, `doca-sha`, `doca-aes-gcm`,\n  `doca-erasure-coding`, `doca-compress`, `doca-dpa`, `doca-gpunetio`,\n  `doca-pcc`, `doca-sta`, `doca-telemetry`, `doca-urom`,\n  `doca-verbs`, `doca-argp`, `doca-devemu`,\n  `doca-dpdk-bridge`, …) — every per-library skill cross-links\n  back to this skill for the foundation primitives. Loading this\n  skill alongside any of them is the recommended default.\n",{"data":32,"body":36},{"license":23,"name":4,"description":6,"metadata":33,"compatibility":35},{"kind":34},"library","Requires DOCA SDK installed at \u002Fopt\u002Fmellanox\u002Fdoca on Linux (Ubuntu 22.04\u002F24.04 or RHEL\u002FSLES) with a BlueField DPU or ConnectX NIC attached. doca-common is present on every healthy DOCA install; reads the user's local install via `pkg-config --modversion doca-common` and inspects \u002Fopt\u002Fmellanox\u002Fdoca\u002F{lib,include,samples,applications}.\n",{"type":37,"children":38},"root",[39,47,196,203,215,634,640,713,719,828,834,845,982,1027,1033,1045,1216,1230,1236,1248,1373,1379,1465,1519,1525],{"type":40,"tag":41,"props":42,"children":43},"element","h1",{"id":4},[44],{"type":45,"value":46},"text","DOCA Common",{"type":40,"tag":48,"props":49,"children":50},"p",{},[51,57,59,64,66,73,75,81,83,89,91,97,99,105,107,113,115,121,123,129,131,137,139,149,151,157,159,168,170,175,177,187,189,194],{"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 ",{"type":40,"tag":52,"props":60,"children":61},{},[62],{"type":45,"value":63},"foundation every DOCA app\nloads first",{"type":45,"value":65}," — before doca-flow, doca-rdma, doca-eth, doca-comch, or\nany other higher-level library. Every ",{"type":40,"tag":67,"props":68,"children":70},"code",{"className":69},[],[71],{"type":45,"value":72},"doca_\u003Clibrary>_*",{"type":45,"value":74}," context is\nbuilt on top of ",{"type":40,"tag":67,"props":76,"children":78},{"className":77},[],[79],{"type":45,"value":80},"doca_ctx",{"type":45,"value":82},", every device handle is a ",{"type":40,"tag":67,"props":84,"children":86},{"className":85},[],[87],{"type":45,"value":88},"doca_dev",{"type":45,"value":90},"\ndiscovered through ",{"type":40,"tag":67,"props":92,"children":94},{"className":93},[],[95],{"type":45,"value":96},"doca_devinfo",{"type":45,"value":98},", every zero-copy buffer is a\n",{"type":40,"tag":67,"props":100,"children":102},{"className":101},[],[103],{"type":45,"value":104},"doca_buf",{"type":45,"value":106}," from a ",{"type":40,"tag":67,"props":108,"children":110},{"className":109},[],[111],{"type":45,"value":112},"doca_buf_inventory",{"type":45,"value":114}," over a ",{"type":40,"tag":67,"props":116,"children":118},{"className":117},[],[119],{"type":45,"value":120},"doca_mmap",{"type":45,"value":122},", every\ntask completion drains through a ",{"type":40,"tag":67,"props":124,"children":126},{"className":125},[],[127],{"type":45,"value":128},"doca_pe",{"type":45,"value":130},", and every log line emits\nthrough ",{"type":40,"tag":67,"props":132,"children":134},{"className":133},[],[135],{"type":45,"value":136},"doca_log",{"type":45,"value":138},". Open ",{"type":40,"tag":140,"props":141,"children":143},"a",{"href":142},"CAPABILITIES.md",[144],{"type":40,"tag":67,"props":145,"children":147},{"className":146},[],[148],{"type":45,"value":142},{"type":45,"value":150}," when\nthe question is ",{"type":40,"tag":152,"props":153,"children":154},"em",{},[155],{"type":45,"value":156},"what does Common express",{"type":45,"value":158}," on this install; open\n",{"type":40,"tag":140,"props":160,"children":162},{"href":161},"TASKS.md",[163],{"type":40,"tag":67,"props":164,"children":166},{"className":165},[],[167],{"type":45,"value":161},{"type":45,"value":169}," when the user wants to ",{"type":40,"tag":152,"props":171,"children":172},{},[173],{"type":45,"value":174},"do",{"type":45,"value":176}," something\n(configure \u002F build \u002F modify \u002F run \u002F test \u002F debug). If the user has\nnot installed DOCA yet, route to\n",{"type":40,"tag":140,"props":178,"children":180},{"href":179},"..\u002F..\u002Fdoca-setup\u002FSKILL.md",[181],{"type":40,"tag":67,"props":182,"children":184},{"className":183},[],[185],{"type":45,"value":186},"doca-setup",{"type":45,"value":188}," first. If the user is\nalready past the foundation and asking a library-specific question\n(e.g. ",{"type":40,"tag":152,"props":190,"children":191},{},[192],{"type":45,"value":193},"\"how do I program a Flow pipe\"",{"type":45,"value":195},"), load the matching per-library\nskill alongside this one — they cross-link back here for the shared\nprimitives.",{"type":40,"tag":197,"props":198,"children":200},"h2",{"id":199},"example-questions-this-skill-answers-well",[201],{"type":45,"value":202},"Example questions this skill answers well",{"type":40,"tag":48,"props":204,"children":205},{},[206,208,213],{"type":45,"value":207},"The CLASSES of doca-common questions this skill is built to answer,\neach with one worked example. The agent should treat the ",{"type":40,"tag":152,"props":209,"children":210},{},[211],{"type":45,"value":212},"class",{"type":45,"value":214}," as\nthe load-bearing piece — the worked example is a single instance.",{"type":40,"tag":216,"props":217,"children":218},"ul",{},[219,283,351,397,440,509],{"type":40,"tag":220,"props":221,"children":222},"li",{},[223,228,230,235,237,247,249,259,260,270,271,281],{"type":40,"tag":52,"props":224,"children":225},{},[226],{"type":45,"value":227},"\"What is the doca-common foundation I have to set up BEFORE I\nopen a doca-flow \u002F doca-rdma \u002F doca-eth \u002F … context?\"",{"type":45,"value":229}," — worked\nexample: ",{"type":40,"tag":152,"props":231,"children":232},{},[233],{"type":45,"value":234},"\"I'm starting a brand-new DOCA Flow program on\nBlueField-3; what's the doca-common skeleton I need before I open\nthe Flow port?\"",{"type":45,"value":236},". Answered by the universal foundation walk in\n",{"type":40,"tag":140,"props":238,"children":240},{"href":239},"TASKS.md#configure",[241],{"type":40,"tag":67,"props":242,"children":244},{"className":243},[],[245],{"type":45,"value":246},"TASKS.md ## configure",{"type":45,"value":248}," +\n",{"type":40,"tag":140,"props":250,"children":252},{"href":251},"CAPABILITIES.md#ctx",[253],{"type":40,"tag":67,"props":254,"children":256},{"className":255},[],[257],{"type":45,"value":258},"CAPABILITIES.md ## ctx",{"type":45,"value":248},{"type":40,"tag":140,"props":261,"children":263},{"href":262},"CAPABILITIES.md#dev",[264],{"type":40,"tag":67,"props":265,"children":267},{"className":266},[],[268],{"type":45,"value":269},"CAPABILITIES.md ## dev",{"type":45,"value":248},{"type":40,"tag":140,"props":272,"children":274},{"href":273},"CAPABILITIES.md#progress-engine",[275],{"type":40,"tag":67,"props":276,"children":278},{"className":277},[],[279],{"type":45,"value":280},"CAPABILITIES.md ## progress engine",{"type":45,"value":282},".",{"type":40,"tag":220,"props":284,"children":285},{},[286,291,293,306,308,314,316,322,324,329,331,339,340,350],{"type":40,"tag":52,"props":287,"children":288},{},[289],{"type":45,"value":290},"\"How do I discover a device and gate on its capabilities before\ntrusting the public docs?\"",{"type":45,"value":292}," — worked example: ",{"type":40,"tag":152,"props":294,"children":295},{},[296,298,304],{"type":45,"value":297},"\"I want to use\n",{"type":40,"tag":67,"props":299,"children":301},{"className":300},[],[302],{"type":45,"value":303},"doca_eth_txq",{"type":45,"value":305}," but the docs hint at a feature only on certain\nfirmware bands\"",{"type":45,"value":307},". Answered by the capability-discovery rule\n(",{"type":40,"tag":67,"props":309,"children":311},{"className":310},[],[312],{"type":45,"value":313},"doca_devinfo_create_list",{"type":45,"value":315}," → ",{"type":40,"tag":67,"props":317,"children":319},{"className":318},[],[320],{"type":45,"value":321},"doca_*_cap_*",{"type":45,"value":323}," against the active\n",{"type":40,"tag":67,"props":325,"children":327},{"className":326},[],[328],{"type":45,"value":96},{"type":45,"value":330}," is the runtime authority) in\n",{"type":40,"tag":140,"props":332,"children":333},{"href":262},[334],{"type":40,"tag":67,"props":335,"children":337},{"className":336},[],[338],{"type":45,"value":269},{"type":45,"value":248},{"type":40,"tag":140,"props":341,"children":343},{"href":342},"TASKS.md#use",[344],{"type":40,"tag":67,"props":345,"children":347},{"className":346},[],[348],{"type":45,"value":349},"TASKS.md ## use",{"type":45,"value":282},{"type":40,"tag":220,"props":352,"children":353},{},[354,359,360,365,367,377,379,387,388,396],{"type":40,"tag":52,"props":355,"children":356},{},[357],{"type":45,"value":358},"\"What's the doca_buf \u002F doca_mmap \u002F doca_buf_inventory wiring\nfor zero-copy I\u002FO, and what's the lifecycle order?\"",{"type":45,"value":229},{"type":40,"tag":152,"props":361,"children":362},{},[363],{"type":45,"value":364},"\"I want to register a user-space buffer with my device,\ncarve it into N data-plane buffers, and reference-count them\nacross multiple DOCA libraries\"",{"type":45,"value":366},". Answered by the zero-copy\nbuffer model in\n",{"type":40,"tag":140,"props":368,"children":370},{"href":369},"CAPABILITIES.md#buf",[371],{"type":40,"tag":67,"props":372,"children":374},{"className":373},[],[375],{"type":45,"value":376},"CAPABILITIES.md ## buf",{"type":45,"value":378}," +\nthe buffer-lifecycle walk in\n",{"type":40,"tag":140,"props":380,"children":381},{"href":239},[382],{"type":40,"tag":67,"props":383,"children":385},{"className":384},[],[386],{"type":45,"value":246},{"type":45,"value":248},{"type":40,"tag":140,"props":389,"children":390},{"href":342},[391],{"type":40,"tag":67,"props":392,"children":394},{"className":393},[],[395],{"type":45,"value":349},{"type":45,"value":282},{"type":40,"tag":220,"props":398,"children":399},{},[400,405,406,411,413,421],{"type":40,"tag":52,"props":401,"children":402},{},[403],{"type":45,"value":404},"\"How does the progress engine work and where do I have to call\nit?\"",{"type":45,"value":292},{"type":40,"tag":152,"props":407,"children":408},{},[409],{"type":45,"value":410},"\"my doca_rdma task submits cleanly but\nnothing completes — what loop am I missing?\"",{"type":45,"value":412},". Answered by the PE\nsurface in\n",{"type":40,"tag":140,"props":414,"children":415},{"href":273},[416],{"type":40,"tag":67,"props":417,"children":419},{"className":418},[],[420],{"type":45,"value":280},{"type":40,"tag":216,"props":422,"children":423},{},[424],{"type":40,"tag":220,"props":425,"children":426},{},[427,429,439],{"type":45,"value":428},"the run-loop pattern in ",{"type":40,"tag":140,"props":430,"children":432},{"href":431},"TASKS.md#run",[433],{"type":40,"tag":67,"props":434,"children":436},{"className":435},[],[437],{"type":45,"value":438},"TASKS.md ## run",{"type":45,"value":282},{"type":40,"tag":220,"props":441,"children":442},{},[443,456,457,478,480,490],{"type":40,"tag":52,"props":444,"children":445},{},[446,448,454],{"type":45,"value":447},"\"Why don't my DOCA log lines appear at the level I expect, and\nwhat's the difference between ",{"type":40,"tag":67,"props":449,"children":451},{"className":450},[],[452],{"type":45,"value":453},"--sdk-log-level",{"type":45,"value":455}," and the app-side\nsetter?\"",{"type":45,"value":292},{"type":40,"tag":152,"props":458,"children":459},{},[460,462,468,470,476],{"type":45,"value":461},"\"I set ",{"type":40,"tag":67,"props":463,"children":465},{"className":464},[],[466],{"type":45,"value":467},"--sdk-log-level DEBUG",{"type":45,"value":469},", my\nown ",{"type":40,"tag":67,"props":471,"children":473},{"className":472},[],[474],{"type":45,"value":475},"DOCA_LOG_DBG",{"type":45,"value":477}," lines still don't print\"",{"type":45,"value":479},". Answered by the\ntwo-tier log model in ",{"type":40,"tag":140,"props":481,"children":483},{"href":482},"CAPABILITIES.md#log",[484],{"type":40,"tag":67,"props":485,"children":487},{"className":486},[],[488],{"type":45,"value":489},"CAPABILITIES.md ## log",{"type":40,"tag":216,"props":491,"children":492},{},[493],{"type":40,"tag":220,"props":494,"children":495},{},[496,498,508],{"type":45,"value":497},"the tier-flip iteration in ",{"type":40,"tag":140,"props":499,"children":501},{"href":500},"TASKS.md#log",[502],{"type":40,"tag":67,"props":503,"children":505},{"className":504},[],[506],{"type":45,"value":507},"TASKS.md ## log",{"type":45,"value":282},{"type":40,"tag":220,"props":510,"children":511},{},[512,562,564,584,586,591,593,603],{"type":40,"tag":52,"props":513,"children":514},{},[515,517,523,524,530,532,538,540,546,547,553,554,560],{"type":45,"value":516},"\"What does this ",{"type":40,"tag":67,"props":518,"children":520},{"className":519},[],[521],{"type":45,"value":522},"DOCA_ERROR_*",{"type":45,"value":106},{"type":40,"tag":67,"props":525,"children":527},{"className":526},[],[528],{"type":45,"value":529},"doca_buf_*",{"type":45,"value":531}," \u002F ",{"type":40,"tag":67,"props":533,"children":535},{"className":534},[],[536],{"type":45,"value":537},"doca_ctx_*",{"type":45,"value":539},"\n\u002F ",{"type":40,"tag":67,"props":541,"children":543},{"className":542},[],[544],{"type":45,"value":545},"doca_dev_*",{"type":45,"value":531},{"type":40,"tag":67,"props":548,"children":550},{"className":549},[],[551],{"type":45,"value":552},"doca_pe_*",{"type":45,"value":531},{"type":40,"tag":67,"props":555,"children":557},{"className":556},[],[558],{"type":45,"value":559},"doca_log_*",{"type":45,"value":561}," call mean?\"",{"type":45,"value":563}," —\nworked example: ",{"type":40,"tag":152,"props":565,"children":566},{},[567,569,575,577,583],{"type":45,"value":568},"\"",{"type":40,"tag":67,"props":570,"children":572},{"className":571},[],[573],{"type":45,"value":574},"DOCA_ERROR_BAD_STATE",{"type":45,"value":576}," from ",{"type":40,"tag":67,"props":578,"children":580},{"className":579},[],[581],{"type":45,"value":582},"doca_ctx_start",{"type":45,"value":568},{"type":45,"value":585},".\nAnswered by the Common overlay on the cross-library ",{"type":40,"tag":67,"props":587,"children":589},{"className":588},[],[590],{"type":45,"value":522},{"type":45,"value":592},"\ntaxonomy in\n",{"type":40,"tag":140,"props":594,"children":596},{"href":595},"CAPABILITIES.md#error-taxonomy",[597],{"type":40,"tag":67,"props":598,"children":600},{"className":599},[],[601],{"type":45,"value":602},"CAPABILITIES.md ## Error taxonomy",{"type":40,"tag":216,"props":604,"children":605},{},[606],{"type":40,"tag":220,"props":607,"children":608},{},[609,611,621,623,633],{"type":45,"value":610},"the layered ladder in\n",{"type":40,"tag":140,"props":612,"children":614},{"href":613},"TASKS.md#debug",[615],{"type":40,"tag":67,"props":616,"children":618},{"className":617},[],[619],{"type":45,"value":620},"TASKS.md ## debug",{"type":45,"value":622}," that escalates to\n",{"type":40,"tag":140,"props":624,"children":626},{"href":625},"..\u002F..\u002Fdoca-debug\u002FSKILL.md",[627],{"type":40,"tag":67,"props":628,"children":630},{"className":629},[],[631],{"type":45,"value":632},"doca-debug",{"type":45,"value":282},{"type":40,"tag":197,"props":635,"children":637},{"id":636},"audience",[638],{"type":45,"value":639},"Audience",{"type":40,"tag":48,"props":641,"children":642},{},[643,645,650,652,657,663,665,670,672,677,679,684,686,691,692,697,699,704,706,711],{"type":45,"value":644},"This skill serves ",{"type":40,"tag":52,"props":646,"children":647},{},[648],{"type":45,"value":649},"every external developer building applications\nthat consume any DOCA library",{"type":45,"value":651}," — i.e., users whose code calls ",{"type":40,"tag":152,"props":653,"children":654},{},[655],{"type":45,"value":656},"any",{"type":40,"tag":67,"props":658,"children":660},{"className":659},[],[661],{"type":45,"value":662},"doca_*",{"type":45,"value":664}," symbol (directly in C\u002FC++, or through FFI\u002Fbindings from\nanother language). Whether the user's primary library is doca-flow,\ndoca-rdma, doca-eth, doca-comch, doca-dma, doca-rmax, doca-sha,\ndoca-aes-gcm, doca-erasure-coding, or any other, the doca-common\nsurface is ",{"type":40,"tag":152,"props":666,"children":667},{},[668],{"type":45,"value":669},"under",{"type":45,"value":671}," it and the user will hit ",{"type":40,"tag":67,"props":673,"children":675},{"className":674},[],[676],{"type":45,"value":104},{"type":45,"value":678},", ",{"type":40,"tag":67,"props":680,"children":682},{"className":681},[],[683],{"type":45,"value":80},{"type":45,"value":685},",\n",{"type":40,"tag":67,"props":687,"children":689},{"className":688},[],[690],{"type":45,"value":88},{"type":45,"value":678},{"type":40,"tag":67,"props":693,"children":695},{"className":694},[],[696],{"type":45,"value":128},{"type":45,"value":698},", and ",{"type":40,"tag":67,"props":700,"children":702},{"className":701},[],[703],{"type":45,"value":136},{"type":45,"value":705}," as part of the first-app\njourney. It is ",{"type":40,"tag":152,"props":707,"children":708},{},[709],{"type":45,"value":710},"not",{"type":45,"value":712}," for NVIDIA developers contributing to DOCA\nCommon itself.",{"type":40,"tag":197,"props":714,"children":716},{"id":715},"language-scope",[717],{"type":45,"value":718},"Language scope",{"type":40,"tag":48,"props":720,"children":721},{},[722,724,730,732,737,739,744,746,752,754,759,761,767,769,774,776,782,783,789,790,795,797,803,805,811,813,818,820,826],{"type":45,"value":723},"DOCA Common ships as a C library with ",{"type":40,"tag":67,"props":725,"children":727},{"className":726},[],[728],{"type":45,"value":729},"pkg-config",{"type":45,"value":731}," module name\n",{"type":40,"tag":67,"props":733,"children":735},{"className":734},[],[736],{"type":45,"value":4},{"type":45,"value":738},". The shipped samples that demonstrate Common primitives\nlive ",{"type":40,"tag":152,"props":740,"children":741},{},[742],{"type":45,"value":743},"inside",{"type":45,"value":745}," every per-library samples tree (any\n",{"type":40,"tag":67,"props":747,"children":749},{"className":748},[],[750],{"type":45,"value":751},"\u002Fopt\u002Fmellanox\u002Fdoca\u002Fsamples\u002F\u003Clibrary>\u002F\u003Csample>\u002F*_main.c",{"type":45,"value":753}," is a worked\nexample of the universal foundation — ",{"type":40,"tag":67,"props":755,"children":757},{"className":756},[],[758],{"type":45,"value":313},{"type":45,"value":760},"\n→ ",{"type":40,"tag":67,"props":762,"children":764},{"className":763},[],[765],{"type":45,"value":766},"doca_dev_open",{"type":45,"value":768}," → per-library ",{"type":40,"tag":67,"props":770,"children":772},{"className":771},[],[773],{"type":45,"value":80},{"type":45,"value":775}," create → ",{"type":40,"tag":67,"props":777,"children":779},{"className":778},[],[780],{"type":45,"value":781},"doca_pe_create",{"type":45,"value":760},{"type":40,"tag":67,"props":784,"children":786},{"className":785},[],[787],{"type":45,"value":788},"doca_pe_connect_ctx",{"type":45,"value":315},{"type":40,"tag":67,"props":791,"children":793},{"className":792},[],[794],{"type":45,"value":582},{"type":45,"value":796}," → submit work → drive\n",{"type":40,"tag":67,"props":798,"children":800},{"className":799},[],[801],{"type":45,"value":802},"doca_pe_progress",{"type":45,"value":804}," → drain completions → ",{"type":40,"tag":67,"props":806,"children":808},{"className":807},[],[809],{"type":45,"value":810},"doca_ctx_stop",{"type":45,"value":812}," → destroy).\nC and C++ consumers are the canonical case and the worked examples\nin ",{"type":40,"tag":67,"props":814,"children":816},{"className":815},[],[817],{"type":45,"value":161},{"type":45,"value":819}," assume that path. Other-language consumers (Rust, Go,\nPython, …) consume the same ",{"type":40,"tag":67,"props":821,"children":823},{"className":822},[],[824],{"type":45,"value":825},"*.so",{"type":45,"value":827}," through FFI or language-specific\nbindings; the skill's contribution in that case is to keep the\nuniversal foundation walk, the lifecycle, the capability-discovery\nrule, the PE-drives-completion rule, and the two-tier log model\nlanguage-neutral, and to route the agent to the public C ABI as the\nauthoritative surface that any wrapper will eventually call.",{"type":40,"tag":197,"props":829,"children":831},{"id":830},"when-to-load-this-skill",[832],{"type":45,"value":833},"When to load this skill",{"type":40,"tag":48,"props":835,"children":836},{},[837,839,843],{"type":45,"value":838},"Load this skill whenever the user is doing ",{"type":40,"tag":52,"props":840,"children":841},{},[842],{"type":45,"value":656},{"type":45,"value":844}," hands-on DOCA\nwork — it is the foundation. Concretely:",{"type":40,"tag":216,"props":846,"children":847},{},[848,853,872,897,922,934,977],{"type":40,"tag":220,"props":849,"children":850},{},[851],{"type":45,"value":852},"Setting up the universal DOCA-side skeleton before opening any\nper-library context (Flow, RDMA, Eth, Comch, DMA, Rmax, …).",{"type":40,"tag":220,"props":854,"children":855},{},[856,858,863,865,870],{"type":45,"value":857},"Discovering devices and representors and gating capability use\non the active ",{"type":40,"tag":67,"props":859,"children":861},{"className":860},[],[862],{"type":45,"value":96},{"type":45,"value":864}," via the ",{"type":40,"tag":67,"props":866,"children":868},{"className":867},[],[869],{"type":45,"value":321},{"type":45,"value":871}," family.",{"type":40,"tag":220,"props":873,"children":874},{},[875,877,882,884,889,890,895],{"type":45,"value":876},"Wiring ",{"type":40,"tag":67,"props":878,"children":880},{"className":879},[],[881],{"type":45,"value":120},{"type":45,"value":883}," + ",{"type":40,"tag":67,"props":885,"children":887},{"className":886},[],[888],{"type":45,"value":112},{"type":45,"value":883},{"type":40,"tag":67,"props":891,"children":893},{"className":892},[],[894],{"type":45,"value":104},{"type":45,"value":896}," for\nzero-copy I\u002FO that crosses libraries (e.g. doca-eth feeds\ndoca-dma feeds doca-rdma — they share the same buf surface).",{"type":40,"tag":220,"props":898,"children":899},{},[900,902,907,909,914,915,920],{"type":45,"value":901},"Driving the progress engine (",{"type":40,"tag":67,"props":903,"children":905},{"className":904},[],[906],{"type":45,"value":781},{"type":45,"value":908}," \u002F\n",{"type":40,"tag":67,"props":910,"children":912},{"className":911},[],[913],{"type":45,"value":788},{"type":45,"value":531},{"type":40,"tag":67,"props":916,"children":918},{"className":917},[],[919],{"type":45,"value":802},{"type":45,"value":921},") — the universal\ntask-completion drain every DOCA Core context relies on.",{"type":40,"tag":220,"props":923,"children":924},{},[925,927,932],{"type":45,"value":926},"Wiring DOCA Log into a fresh app or modifying a shipped sample to\nadd the user's own per-component log lines via the two-tier\n(",{"type":40,"tag":67,"props":928,"children":930},{"className":929},[],[931],{"type":45,"value":453},{"type":45,"value":933}," vs app-side registry) model.",{"type":40,"tag":220,"props":935,"children":936},{},[937,939,944,946,951,952,957,958,963,964,969,970,975],{"type":45,"value":938},"Debugging a ",{"type":40,"tag":67,"props":940,"children":942},{"className":941},[],[943],{"type":45,"value":522},{"type":45,"value":945}," returned from any ",{"type":40,"tag":67,"props":947,"children":949},{"className":948},[],[950],{"type":45,"value":529},{"type":45,"value":908},{"type":40,"tag":67,"props":953,"children":955},{"className":954},[],[956],{"type":45,"value":537},{"type":45,"value":531},{"type":40,"tag":67,"props":959,"children":961},{"className":960},[],[962],{"type":45,"value":545},{"type":45,"value":531},{"type":40,"tag":67,"props":965,"children":967},{"className":966},[],[968],{"type":45,"value":552},{"type":45,"value":531},{"type":40,"tag":67,"props":971,"children":973},{"className":972},[],[974],{"type":45,"value":559},{"type":45,"value":976}," call —\nthe Common surface is where most lifecycle \u002F capability \u002F\npermission errors first surface for higher-level libraries.",{"type":40,"tag":220,"props":978,"children":979},{},[980],{"type":45,"value":981},"Designing or extending non-C bindings (Rust, Go, Python, …) that\nwrap any DOCA library — for the universal foundation surface\n(buf, ctx, dev, pe, log) the wrapper has to expose first.",{"type":40,"tag":48,"props":983,"children":984},{},[985,987,991,993,997,999,1004,1006,1016,1018,1026],{"type":45,"value":986},"Do ",{"type":40,"tag":52,"props":988,"children":989},{},[990],{"type":45,"value":710},{"type":45,"value":992}," load this skill for library-specific Flow, RDMA, Eth,\nComch, DMA, Rmax, … questions in isolation — load the matching\nper-library skill alongside this one. Do ",{"type":40,"tag":52,"props":994,"children":995},{},[996],{"type":45,"value":710},{"type":45,"value":998}," load this skill for\ngeneral DOCA orientation, install of DOCA itself, or\n",{"type":40,"tag":152,"props":1000,"children":1001},{},[1002],{"type":45,"value":1003},"\"where do I find docs\"",{"type":45,"value":1005},". For those, use\n",{"type":40,"tag":140,"props":1007,"children":1009},{"href":1008},"..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md",[1010],{"type":40,"tag":67,"props":1011,"children":1013},{"className":1012},[],[1014],{"type":45,"value":1015},"doca-public-knowledge-map",{"type":45,"value":1017},"\nor ",{"type":40,"tag":140,"props":1019,"children":1020},{"href":179},[1021],{"type":40,"tag":67,"props":1022,"children":1024},{"className":1023},[],[1025],{"type":45,"value":186},{"type":45,"value":282},{"type":40,"tag":197,"props":1028,"children":1030},{"id":1029},"what-this-skill-provides",[1031],{"type":45,"value":1032},"What this skill provides",{"type":40,"tag":48,"props":1034,"children":1035},{},[1036,1038,1043],{"type":45,"value":1037},"This is a ",{"type":40,"tag":52,"props":1039,"children":1040},{},[1041],{"type":45,"value":1042},"thin loader",{"type":45,"value":1044},". The body keeps only the orientation\nneeded to pick the right next file. The substantive Common material\nlives in two companion files:",{"type":40,"tag":216,"props":1046,"children":1047},{},[1048,1141],{"type":40,"tag":220,"props":1049,"children":1050},{},[1051,1056,1058,1064,1066,1072,1073,1079,1080,1086,1087,1093,1094,1100,1102,1108,1110,1116,1118,1123,1125,1131,1133,1139],{"type":40,"tag":67,"props":1052,"children":1054},{"className":1053},[],[1055],{"type":45,"value":142},{"type":45,"value":1057}," — what doca-common expresses on this install:\nthe ",{"type":40,"tag":67,"props":1059,"children":1061},{"className":1060},[],[1062],{"type":45,"value":1063},"## Capabilities and modes",{"type":45,"value":1065}," overview of the universal\nprimitives every DOCA application touches; the five subsystem\nH2s (",{"type":40,"tag":67,"props":1067,"children":1069},{"className":1068},[],[1070],{"type":45,"value":1071},"## log",{"type":45,"value":678},{"type":40,"tag":67,"props":1074,"children":1076},{"className":1075},[],[1077],{"type":45,"value":1078},"## buf",{"type":45,"value":678},{"type":40,"tag":67,"props":1081,"children":1083},{"className":1082},[],[1084],{"type":45,"value":1085},"## ctx",{"type":45,"value":678},{"type":40,"tag":67,"props":1088,"children":1090},{"className":1089},[],[1091],{"type":45,"value":1092},"## dev",{"type":45,"value":678},{"type":40,"tag":67,"props":1095,"children":1097},{"className":1096},[],[1098],{"type":45,"value":1099},"## progress engine",{"type":45,"value":1101},") that own the per-primitive surface; the\n",{"type":40,"tag":67,"props":1103,"children":1105},{"className":1104},[],[1106],{"type":45,"value":1107},"## Version compatibility",{"type":45,"value":1109}," doca-common-specific overlay;\nthe ",{"type":40,"tag":67,"props":1111,"children":1113},{"className":1112},[],[1114],{"type":45,"value":1115},"## Error taxonomy",{"type":45,"value":1117}," Common-side view of the universal\n",{"type":40,"tag":67,"props":1119,"children":1121},{"className":1120},[],[1122],{"type":45,"value":522},{"type":45,"value":1124}," set; the ",{"type":40,"tag":67,"props":1126,"children":1128},{"className":1127},[],[1129],{"type":45,"value":1130},"## Observability",{"type":45,"value":1132}," surface (logs, PE\nevents, capability snapshots); and the ",{"type":40,"tag":67,"props":1134,"children":1136},{"className":1135},[],[1137],{"type":45,"value":1138},"## Safety policy",{"type":45,"value":1140}," overlay\non the bundle-wide hardware-safety meta-policy.",{"type":40,"tag":220,"props":1142,"children":1143},{},[1144,1149,1151,1157,1158,1164,1165,1171,1172,1178,1179,1185,1186,1192,1193,1199,1201,1206,1208,1214],{"type":40,"tag":67,"props":1145,"children":1147},{"className":1146},[],[1148],{"type":45,"value":161},{"type":45,"value":1150}," — step-by-step workflows for the universal verbs\n(",{"type":40,"tag":67,"props":1152,"children":1154},{"className":1153},[],[1155],{"type":45,"value":1156},"configure",{"type":45,"value":678},{"type":40,"tag":67,"props":1159,"children":1161},{"className":1160},[],[1162],{"type":45,"value":1163},"build",{"type":45,"value":678},{"type":40,"tag":67,"props":1166,"children":1168},{"className":1167},[],[1169],{"type":45,"value":1170},"modify",{"type":45,"value":678},{"type":40,"tag":67,"props":1173,"children":1175},{"className":1174},[],[1176],{"type":45,"value":1177},"run",{"type":45,"value":678},{"type":40,"tag":67,"props":1180,"children":1182},{"className":1181},[],[1183],{"type":45,"value":1184},"test",{"type":45,"value":678},{"type":40,"tag":67,"props":1187,"children":1189},{"className":1188},[],[1190],{"type":45,"value":1191},"debug",{"type":45,"value":678},{"type":40,"tag":67,"props":1194,"children":1196},{"className":1195},[],[1197],{"type":45,"value":1198},"use",{"type":45,"value":1200},")\nPLUS a ",{"type":40,"tag":67,"props":1202,"children":1204},{"className":1203},[],[1205],{"type":45,"value":1071},{"type":45,"value":1207}," verb-side that covers the two-tier log model in\nworkflow form. Plus a ",{"type":40,"tag":67,"props":1209,"children":1211},{"className":1210},[],[1212],{"type":45,"value":1213},"Deferred task verbs",{"type":45,"value":1215}," block that points\ninstall \u002F deploy \u002F rollback questions at the right next skill.",{"type":40,"tag":48,"props":1217,"children":1218},{},[1219,1221,1229],{"type":45,"value":1220},"The skill assumes a host or BlueField where DOCA is already\ninstalled at the standard location and the user has the privileges\ntheir public install profile expects. It does not cover installing\nDOCA — that path goes through\n",{"type":40,"tag":140,"props":1222,"children":1223},{"href":179},[1224],{"type":40,"tag":67,"props":1225,"children":1227},{"className":1226},[],[1228],{"type":45,"value":186},{"type":45,"value":282},{"type":40,"tag":197,"props":1231,"children":1233},{"id":1232},"what-this-skill-deliberately-does-not-ship",[1234],{"type":45,"value":1235},"What this skill deliberately does not ship",{"type":40,"tag":48,"props":1237,"children":1238},{},[1239,1241,1246],{"type":45,"value":1240},"This skill is ",{"type":40,"tag":52,"props":1242,"children":1243},{},[1244],{"type":45,"value":1245},"agent guidance",{"type":45,"value":1247},", not a samples or templates\nbundle. To keep the boundary clean, it deliberately does not\ncontain — and pull requests should not add:",{"type":40,"tag":216,"props":1249,"children":1250},{},[1251,1279,1340],{"type":40,"tag":220,"props":1252,"children":1253},{},[1254,1259,1261,1266,1268,1278],{"type":40,"tag":52,"props":1255,"children":1256},{},[1257],{"type":45,"value":1258},"Pre-written DOCA application source code, in any language.",{"type":45,"value":1260},"\nThe verified Common usage shows up inside every shipped DOCA\nsample at ",{"type":40,"tag":67,"props":1262,"children":1264},{"className":1263},[],[1265],{"type":45,"value":751},{"type":45,"value":1267},"\nand inside every shipped reference application. The agent's job\nis to route the user to those files and prescribe a minimum-diff\nmodification on them via the universal modify-a-sample workflow\nin\n",{"type":40,"tag":140,"props":1269,"children":1271},{"href":1270},"..\u002F..\u002Fdoca-programming-guide\u002FSKILL.md",[1272],{"type":40,"tag":67,"props":1273,"children":1275},{"className":1274},[],[1276],{"type":45,"value":1277},"doca-programming-guide",{"type":45,"value":282},{"type":40,"tag":220,"props":1280,"children":1281},{},[1282,1287,1289,1295,1296,1302,1303,1309,1310,1316,1317,1323,1325,1330,1332,1338],{"type":40,"tag":52,"props":1283,"children":1284},{},[1285],{"type":45,"value":1286},"Standalone build manifests",{"type":45,"value":1288}," (",{"type":40,"tag":67,"props":1290,"children":1292},{"className":1291},[],[1293],{"type":45,"value":1294},"meson.build",{"type":45,"value":685},{"type":40,"tag":67,"props":1297,"children":1299},{"className":1298},[],[1300],{"type":45,"value":1301},"CMakeLists.txt",{"type":45,"value":678},{"type":40,"tag":67,"props":1304,"children":1306},{"className":1305},[],[1307],{"type":45,"value":1308},"Cargo.toml",{"type":45,"value":678},{"type":40,"tag":67,"props":1311,"children":1313},{"className":1312},[],[1314],{"type":45,"value":1315},"setup.py",{"type":45,"value":678},{"type":40,"tag":67,"props":1318,"children":1320},{"className":1319},[],[1321],{"type":45,"value":1322},"go.mod",{"type":45,"value":1324},", …) parked\ninside the skill. The agent constructs the build manifest ",{"type":40,"tag":152,"props":1326,"children":1327},{},[1328],{"type":45,"value":1329},"in\nthe user's project directory",{"type":45,"value":1331}," against the user's installed DOCA,\nwhere ",{"type":40,"tag":67,"props":1333,"children":1335},{"className":1334},[],[1336],{"type":45,"value":1337},"pkg-config --modversion doca-common",{"type":45,"value":1339}," is the source of\ntruth.",{"type":40,"tag":220,"props":1341,"children":1342},{},[1343,1371],{"type":40,"tag":52,"props":1344,"children":1345},{},[1346,1348,1354,1355,1361,1363,1369],{"type":45,"value":1347},"A ",{"type":40,"tag":67,"props":1349,"children":1351},{"className":1350},[],[1352],{"type":45,"value":1353},"samples\u002F",{"type":45,"value":678},{"type":40,"tag":67,"props":1356,"children":1358},{"className":1357},[],[1359],{"type":45,"value":1360},"bindings\u002F",{"type":45,"value":1362},", or ",{"type":40,"tag":67,"props":1364,"children":1366},{"className":1365},[],[1367],{"type":45,"value":1368},"reference\u002F",{"type":45,"value":1370}," subtree",{"type":45,"value":1372}," of any\nkind. A mock or incomplete artifact in this skill's tree, even\none labeled \"reference\", is misleading: users will read it as\nbuildable.",{"type":40,"tag":197,"props":1374,"children":1376},{"id":1375},"loading-order",[1377],{"type":45,"value":1378},"Loading order",{"type":40,"tag":1380,"props":1381,"children":1382},"ol",{},[1383,1396,1452],{"type":40,"tag":220,"props":1384,"children":1385},{},[1386,1388,1394],{"type":45,"value":1387},"Read this ",{"type":40,"tag":67,"props":1389,"children":1391},{"className":1390},[],[1392],{"type":45,"value":1393},"SKILL.md",{"type":45,"value":1395}," first to confirm the user's question is in\nscope.",{"type":40,"tag":220,"props":1397,"children":1398},{},[1399],{"type":40,"tag":52,"props":1400,"children":1401},{},[1402,1404,1410,1411,1417,1418,1424,1425,1431,1432,1438,1440,1445,1447,1451],{"type":45,"value":1403},"For the universal primitives (",{"type":40,"tag":67,"props":1405,"children":1407},{"className":1406},[],[1408],{"type":45,"value":1409},"log",{"type":45,"value":531},{"type":40,"tag":67,"props":1412,"children":1414},{"className":1413},[],[1415],{"type":45,"value":1416},"buf",{"type":45,"value":531},{"type":40,"tag":67,"props":1419,"children":1421},{"className":1420},[],[1422],{"type":45,"value":1423},"ctx",{"type":45,"value":531},{"type":40,"tag":67,"props":1426,"children":1428},{"className":1427},[],[1429],{"type":45,"value":1430},"dev",{"type":45,"value":908},{"type":40,"tag":67,"props":1433,"children":1435},{"className":1434},[],[1436],{"type":45,"value":1437},"progress engine",{"type":45,"value":1439},"), the ",{"type":40,"tag":67,"props":1441,"children":1443},{"className":1442},[],[1444],{"type":45,"value":1337},{"type":45,"value":1446},"\nanchor, the Common error overlay, observability, and safety\npolicy, see ",{"type":40,"tag":140,"props":1448,"children":1449},{"href":142},[1450],{"type":45,"value":142},{"type":45,"value":282},{"type":40,"tag":220,"props":1453,"children":1454},{},[1455],{"type":40,"tag":52,"props":1456,"children":1457},{},[1458,1460,1464],{"type":45,"value":1459},"For step-by-step workflows — configure, build, modify, run,\ntest, debug, use, log — see ",{"type":40,"tag":140,"props":1461,"children":1462},{"href":161},[1463],{"type":45,"value":161},{"type":45,"value":282},{"type":40,"tag":48,"props":1466,"children":1467},{},[1468,1470,1480,1482,1490,1492,1497,1499,1507,1509,1517],{"type":45,"value":1469},"Both companion files cross-link to each other,\n",{"type":40,"tag":140,"props":1471,"children":1473},{"href":1472},"..\u002F..\u002Fdoca-version\u002FSKILL.md",[1474],{"type":40,"tag":67,"props":1475,"children":1477},{"className":1476},[],[1478],{"type":45,"value":1479},"doca-version",{"type":45,"value":1481}," for the canonical\nversion-handling rules,\n",{"type":40,"tag":140,"props":1483,"children":1484},{"href":1270},[1485],{"type":40,"tag":67,"props":1486,"children":1488},{"className":1487},[],[1489],{"type":45,"value":1277},{"type":45,"value":1491},"\nfor the universal modify-a-shipped-sample workflow and the\ncross-library ",{"type":40,"tag":67,"props":1493,"children":1495},{"className":1494},[],[1496],{"type":45,"value":522},{"type":45,"value":1498}," taxonomy,\n",{"type":40,"tag":140,"props":1500,"children":1501},{"href":625},[1502],{"type":40,"tag":67,"props":1503,"children":1505},{"className":1504},[],[1506],{"type":45,"value":632},{"type":45,"value":1508}," for the cross-cutting\ndebug ladder, and\n",{"type":40,"tag":140,"props":1510,"children":1511},{"href":1008},[1512],{"type":40,"tag":67,"props":1513,"children":1515},{"className":1514},[],[1516],{"type":45,"value":1015},{"type":45,"value":1518},"\nwhenever the right answer is \"look it up in the public docs or the\ninstalled package layout\" rather than \"Common-specific guidance\".",{"type":40,"tag":197,"props":1520,"children":1522},{"id":1521},"related-skills",[1523],{"type":45,"value":1524},"Related skills",{"type":40,"tag":216,"props":1526,"children":1527},{},[1528,1541,1569,1603,1637,1664,1685,1707],{"type":40,"tag":220,"props":1529,"children":1530},{},[1531,1539],{"type":40,"tag":140,"props":1532,"children":1533},{"href":1008},[1534],{"type":40,"tag":67,"props":1535,"children":1537},{"className":1536},[],[1538],{"type":45,"value":1015},{"type":45,"value":1540}," —\nthe routing table for every public DOCA documentation source and\nthe on-disk layout of an installed DOCA package. Always available\nalongside this skill; this skill expects to be able to defer\ndocumentation-finding and install-layout questions there instead\nof duplicating them.",{"type":40,"tag":220,"props":1542,"children":1543},{},[1544,1552,1554,1559,1561,1567],{"type":40,"tag":140,"props":1545,"children":1546},{"href":179},[1547],{"type":40,"tag":67,"props":1548,"children":1550},{"className":1549},[],[1551],{"type":45,"value":186},{"type":45,"value":1553}," — env preparation,\ninstall verification, and the ",{"type":40,"tag":152,"props":1555,"children":1556},{},[1557],{"type":45,"value":1558},"I have no install yet",{"type":45,"value":1560}," path with\nthe public NGC DOCA container (",{"type":40,"tag":67,"props":1562,"children":1564},{"className":1563},[],[1565],{"type":45,"value":1566},"nvcr.io\u002Fnvidia\u002Fdoca\u002Fdoca",{"type":45,"value":1568},") as the\nuniversal Stage-1 fallback. This skill assumes its preconditions\nare satisfied.",{"type":40,"tag":220,"props":1570,"children":1571},{},[1572,1580,1582,1587,1589,1594,1596,1601],{"type":40,"tag":140,"props":1573,"children":1574},{"href":1472},[1575],{"type":40,"tag":67,"props":1576,"children":1578},{"className":1577},[],[1579],{"type":45,"value":1479},{"type":45,"value":1581}," — canonical DOCA\nversion-handling rules (four-way match, NGC semantics,\nheaders-win-over-docs). ",{"type":40,"tag":67,"props":1583,"children":1585},{"className":1584},[],[1586],{"type":45,"value":1337},{"type":45,"value":1588}," is\nthe build-time anchor ",{"type":40,"tag":152,"props":1590,"children":1591},{},[1592],{"type":45,"value":1593},"every",{"type":45,"value":1595}," DOCA install carries; this skill's\n",{"type":40,"tag":67,"props":1597,"children":1599},{"className":1598},[],[1600],{"type":45,"value":1107},{"type":45,"value":1602}," overlays the Common-specific notes on\ntop.",{"type":40,"tag":220,"props":1604,"children":1605},{},[1606,1614,1616,1621,1623,1628,1630,1635],{"type":40,"tag":140,"props":1607,"children":1608},{"href":1270},[1609],{"type":40,"tag":67,"props":1610,"children":1612},{"className":1611},[],[1613],{"type":45,"value":1277},{"type":45,"value":1615}," —\ngeneral DOCA programming patterns shared by every library: the\ncanonical ",{"type":40,"tag":67,"props":1617,"children":1619},{"className":1618},[],[1620],{"type":45,"value":729},{"type":45,"value":1622}," + meson build pattern, the universal\nmodify-a-shipped-sample first-app workflow, the universal\nlifecycle, the cross-library ",{"type":40,"tag":67,"props":1624,"children":1626},{"className":1625},[],[1627],{"type":45,"value":522},{"type":45,"value":1629}," taxonomy, and the\nprogram-side debug order. This skill is the ",{"type":40,"tag":152,"props":1631,"children":1632},{},[1633],{"type":45,"value":1634},"primitives",{"type":45,"value":1636}," layer\nthe programming-guide patterns rest on.",{"type":40,"tag":220,"props":1638,"children":1639},{},[1640,1648,1650,1655,1657,1662],{"type":40,"tag":140,"props":1641,"children":1642},{"href":625},[1643],{"type":40,"tag":67,"props":1644,"children":1646},{"className":1645},[],[1647],{"type":45,"value":632},{"type":45,"value":1649}," — the cross-cutting\ndebug ladder (install \u002F version \u002F build \u002F link \u002F runtime \u002F\nprogram \u002F driver) and the verbosity-escalation surface. DOCA Log\nis the foundation ",{"type":40,"tag":67,"props":1651,"children":1653},{"className":1652},[],[1654],{"type":45,"value":632},{"type":45,"value":1656}," builds its runtime-debug story on;\nthis skill is where the two-tier log model and the universal\nlifecycle errors first surface, and ",{"type":40,"tag":67,"props":1658,"children":1660},{"className":1659},[],[1661],{"type":45,"value":632},{"type":45,"value":1663}," cross-links here\nfor both.",{"type":40,"tag":220,"props":1665,"children":1666},{},[1667,1677,1679,1683],{"type":40,"tag":140,"props":1668,"children":1670},{"href":1669},"..\u002F..\u002Fdoca-structured-tools-contract\u002FSKILL.md",[1671],{"type":40,"tag":67,"props":1672,"children":1674},{"className":1673},[],[1675],{"type":45,"value":1676},"doca-structured-tools-contract",{"type":45,"value":1678}," —\nthe bundle's structured-tools precedence rule (detect \u002F prefer \u002F\nfall back \u002F report). The Command appendix in\n",{"type":40,"tag":140,"props":1680,"children":1681},{"href":161},[1682],{"type":45,"value":161},{"type":45,"value":1684}," honors this contract.",{"type":40,"tag":220,"props":1686,"children":1687},{},[1688,1698,1700,1705],{"type":40,"tag":140,"props":1689,"children":1691},{"href":1690},"..\u002F..\u002Fdoca-hardware-safety\u002FSKILL.md",[1692],{"type":40,"tag":67,"props":1693,"children":1695},{"className":1694},[],[1696],{"type":45,"value":1697},"doca-hardware-safety",{"type":45,"value":1699}," —\nthe cross-cutting hardware-safety meta-policy this skill's\n",{"type":40,"tag":67,"props":1701,"children":1703},{"className":1702},[],[1704],{"type":45,"value":1138},{"type":45,"value":1706}," overlays.",{"type":40,"tag":220,"props":1708,"children":1709},{},[1710,1712,1718,1719,1725,1726,1732,1733,1739,1740,1746,1747,1753,1754,1760,1761,1767,1768,1774,1775,1781,1782,1788,1789,1795,1796,1802,1803,1809,1810,1816,1817,1823,1824,1830,1831,1837,1838,1844,1845,1851],{"type":45,"value":1711},"Per-library skills (",{"type":40,"tag":67,"props":1713,"children":1715},{"className":1714},[],[1716],{"type":45,"value":1717},"doca-flow",{"type":45,"value":678},{"type":40,"tag":67,"props":1720,"children":1722},{"className":1721},[],[1723],{"type":45,"value":1724},"doca-rdma",{"type":45,"value":678},{"type":40,"tag":67,"props":1727,"children":1729},{"className":1728},[],[1730],{"type":45,"value":1731},"doca-eth",{"type":45,"value":685},{"type":40,"tag":67,"props":1734,"children":1736},{"className":1735},[],[1737],{"type":45,"value":1738},"doca-comch",{"type":45,"value":678},{"type":40,"tag":67,"props":1741,"children":1743},{"className":1742},[],[1744],{"type":45,"value":1745},"doca-dma",{"type":45,"value":678},{"type":40,"tag":67,"props":1748,"children":1750},{"className":1749},[],[1751],{"type":45,"value":1752},"doca-rmax",{"type":45,"value":678},{"type":40,"tag":67,"props":1755,"children":1757},{"className":1756},[],[1758],{"type":45,"value":1759},"doca-sha",{"type":45,"value":678},{"type":40,"tag":67,"props":1762,"children":1764},{"className":1763},[],[1765],{"type":45,"value":1766},"doca-aes-gcm",{"type":45,"value":685},{"type":40,"tag":67,"props":1769,"children":1771},{"className":1770},[],[1772],{"type":45,"value":1773},"doca-erasure-coding",{"type":45,"value":678},{"type":40,"tag":67,"props":1776,"children":1778},{"className":1777},[],[1779],{"type":45,"value":1780},"doca-compress",{"type":45,"value":678},{"type":40,"tag":67,"props":1783,"children":1785},{"className":1784},[],[1786],{"type":45,"value":1787},"doca-dpa",{"type":45,"value":678},{"type":40,"tag":67,"props":1790,"children":1792},{"className":1791},[],[1793],{"type":45,"value":1794},"doca-gpunetio",{"type":45,"value":685},{"type":40,"tag":67,"props":1797,"children":1799},{"className":1798},[],[1800],{"type":45,"value":1801},"doca-pcc",{"type":45,"value":678},{"type":40,"tag":67,"props":1804,"children":1806},{"className":1805},[],[1807],{"type":45,"value":1808},"doca-sta",{"type":45,"value":678},{"type":40,"tag":67,"props":1811,"children":1813},{"className":1812},[],[1814],{"type":45,"value":1815},"doca-telemetry",{"type":45,"value":678},{"type":40,"tag":67,"props":1818,"children":1820},{"className":1819},[],[1821],{"type":45,"value":1822},"doca-urom",{"type":45,"value":685},{"type":40,"tag":67,"props":1825,"children":1827},{"className":1826},[],[1828],{"type":45,"value":1829},"doca-verbs",{"type":45,"value":678},{"type":40,"tag":67,"props":1832,"children":1834},{"className":1833},[],[1835],{"type":45,"value":1836},"doca-argp",{"type":45,"value":678},{"type":40,"tag":67,"props":1839,"children":1841},{"className":1840},[],[1842],{"type":45,"value":1843},"doca-devemu",{"type":45,"value":685},{"type":40,"tag":67,"props":1846,"children":1848},{"className":1847},[],[1849],{"type":45,"value":1850},"doca-dpdk-bridge",{"type":45,"value":1852},", …) — every per-library skill cross-links\nback to this skill for the foundation primitives. Loading this\nskill alongside any of them is the recommended default.",{"items":1854,"total":1958},[1855,1872,1886,1900,1912,1929,1944],{"slug":1856,"name":1856,"fn":1857,"description":1858,"org":1859,"tags":1860,"stars":20,"repoUrl":21,"updatedAt":1871},"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},[1861,1864,1867,1868],{"name":1862,"slug":1863,"type":13},"Data Analysis","data-analysis",{"name":1865,"slug":1866,"type":13},"Data Engineering","data-engineering",{"name":9,"slug":8,"type":13},{"name":1869,"slug":1870,"type":13},"Performance","performance","2026-07-14T05:28:43.176466",{"slug":1873,"name":1873,"fn":1874,"description":1875,"org":1876,"tags":1877,"stars":20,"repoUrl":21,"updatedAt":1885},"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},[1878,1881,1884],{"name":1879,"slug":1880,"type":13},"Deployment","deployment",{"name":1882,"slug":1883,"type":13},"Infrastructure","infrastructure",{"name":9,"slug":8,"type":13},"2026-07-14T05:29:06.667109",{"slug":1887,"name":1887,"fn":1888,"description":1889,"org":1890,"tags":1891,"stars":20,"repoUrl":21,"updatedAt":1899},"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},[1892,1895,1896],{"name":1893,"slug":1894,"type":13},"Agents","agents",{"name":9,"slug":8,"type":13},{"name":1897,"slug":1898,"type":13},"Research","research","2026-07-14T05:28:06.816956",{"slug":1901,"name":1901,"fn":1902,"description":1903,"org":1904,"tags":1905,"stars":20,"repoUrl":21,"updatedAt":1911},"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},[1906,1907,1908],{"name":1862,"slug":1863,"type":13},{"name":9,"slug":8,"type":13},{"name":1909,"slug":1910,"type":13},"Testing","testing","2026-07-17T05:29:03.913266",{"slug":1913,"name":1913,"fn":1914,"description":1915,"org":1916,"tags":1917,"stars":20,"repoUrl":21,"updatedAt":1928},"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},[1918,1921,1924,1925],{"name":1919,"slug":1920,"type":13},"Automation","automation",{"name":1922,"slug":1923,"type":13},"Imaging","imaging",{"name":9,"slug":8,"type":13},{"name":1926,"slug":1927,"type":13},"Video","video","2026-07-17T05:28:53.905004",{"slug":1930,"name":1930,"fn":1931,"description":1932,"org":1933,"tags":1934,"stars":20,"repoUrl":21,"updatedAt":1943},"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},[1935,1936,1939,1940],{"name":1879,"slug":1880,"type":13},{"name":1937,"slug":1938,"type":13},"Docker","docker",{"name":9,"slug":8,"type":13},{"name":1941,"slug":1942,"type":13},"Operations","operations","2026-07-17T05:28:56.913999",{"slug":1945,"name":1945,"fn":1946,"description":1947,"org":1948,"tags":1949,"stars":20,"repoUrl":21,"updatedAt":1957},"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},[1950,1951,1954],{"name":9,"slug":8,"type":13},{"name":1952,"slug":1953,"type":13},"Quantum Computing","quantum-computing",{"name":1955,"slug":1956,"type":13},"Simulation","simulation","2026-07-14T05:26:58.898253",305,{"items":1960,"total":2111},[1961,1979,1995,2006,2018,2032,2045,2059,2070,2079,2093,2102],{"slug":1962,"name":1962,"fn":1963,"description":1964,"org":1965,"tags":1966,"stars":1976,"repoUrl":1977,"updatedAt":1978},"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},[1967,1970,1973],{"name":1968,"slug":1969,"type":13},"Documentation","documentation",{"name":1971,"slug":1972,"type":13},"MCP","mcp",{"name":1974,"slug":1975,"type":13},"Search","search",21777,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNemoClaw","2026-07-20T06:00:01.461044",{"slug":1980,"name":1980,"fn":1981,"description":1982,"org":1983,"tags":1984,"stars":1992,"repoUrl":1993,"updatedAt":1994},"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},[1985,1988,1989],{"name":1986,"slug":1987,"type":13},"Containers","containers",{"name":1879,"slug":1880,"type":13},{"name":1990,"slug":1991,"type":13},"Python","python",17049,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FMegatron-LM","2026-07-27T06:06:11.249662",{"slug":1996,"name":1996,"fn":1997,"description":1998,"org":1999,"tags":2000,"stars":1992,"repoUrl":1993,"updatedAt":2005},"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},[2001,2004],{"name":2002,"slug":2003,"type":13},"CI\u002FCD","ci-cd",{"name":1879,"slug":1880,"type":13},"2026-07-14T05:25:59.97109",{"slug":2007,"name":2007,"fn":2008,"description":2009,"org":2010,"tags":2011,"stars":1992,"repoUrl":1993,"updatedAt":2017},"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},[2012,2013,2014],{"name":2002,"slug":2003,"type":13},{"name":1879,"slug":1880,"type":13},{"name":2015,"slug":2016,"type":13},"GitHub","github","2026-07-27T06:06:12.278222",{"slug":2019,"name":2019,"fn":2020,"description":2021,"org":2022,"tags":2023,"stars":1992,"repoUrl":1993,"updatedAt":2031},"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},[2024,2027,2028],{"name":2025,"slug":2026,"type":13},"Debugging","debugging",{"name":2015,"slug":2016,"type":13},{"name":2029,"slug":2030,"type":13},"Triage","triage","2026-07-14T05:25:57.442089",{"slug":2033,"name":2033,"fn":2034,"description":2035,"org":2036,"tags":2037,"stars":1992,"repoUrl":1993,"updatedAt":2044},"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},[2038,2041],{"name":2039,"slug":2040,"type":13},"Best Practices","best-practices",{"name":2042,"slug":2043,"type":13},"Code Analysis","code-analysis","2026-07-14T05:25:56.18433",{"slug":2046,"name":2046,"fn":2047,"description":2048,"org":2049,"tags":2050,"stars":1992,"repoUrl":1993,"updatedAt":2058},"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},[2051,2054,2057],{"name":2052,"slug":2053,"type":13},"Machine Learning","machine-learning",{"name":2055,"slug":2056,"type":13},"Migration","migration",{"name":9,"slug":8,"type":13},"2026-07-17T06:07:11.777011",{"slug":2060,"name":2060,"fn":2061,"description":2062,"org":2063,"tags":2064,"stars":1992,"repoUrl":1993,"updatedAt":2069},"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},[2065,2068],{"name":2066,"slug":2067,"type":13},"QA","qa",{"name":1909,"slug":1910,"type":13},"2026-07-14T05:25:53.673039",{"slug":2071,"name":2071,"fn":2072,"description":2073,"org":2074,"tags":2075,"stars":1992,"repoUrl":1993,"updatedAt":2078},"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},[2076,2077],{"name":1879,"slug":1880,"type":13},{"name":1882,"slug":1883,"type":13},"2026-07-14T05:25:49.362534",{"slug":2080,"name":2080,"fn":2081,"description":2082,"org":2083,"tags":2084,"stars":1992,"repoUrl":1993,"updatedAt":2092},"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},[2085,2088,2089],{"name":2086,"slug":2087,"type":13},"Code Review","code-review",{"name":2015,"slug":2016,"type":13},{"name":2090,"slug":2091,"type":13},"Pull Requests","pull-requests","2026-07-14T05:26:01.226578",{"slug":2094,"name":2094,"fn":2095,"description":2096,"org":2097,"tags":2098,"stars":1992,"repoUrl":1993,"updatedAt":2101},"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},[2099,2100],{"name":2066,"slug":2067,"type":13},{"name":1909,"slug":1910,"type":13},"2026-07-14T05:25:54.928983",{"slug":2103,"name":2103,"fn":2104,"description":2105,"org":2106,"tags":2107,"stars":1992,"repoUrl":1993,"updatedAt":2110},"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},[2108,2109],{"name":1919,"slug":1920,"type":13},{"name":2002,"slug":2003,"type":13},"2026-07-30T05:29:03.275638",496]