[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-nvidia-doca-comch":3,"mdc-dafuea-key":31,"related-repo-nvidia-doca-comch":1192,"related-org-nvidia-doca-comch":1298},{"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-comch","configure host-to-DPU control-plane messaging","Use this skill when the user is doing hands-on DOCA Comch work on a host + BlueField pair — bringing up host ↔ DPU PCIe control-plane messaging, picking server (DPU) vs client (host) roles, choosing slow-path send-task \u002F recv-callback vs fast-path producer \u002F consumer, querying max-msg-size or max-clients capabilities, registering connection callbacks, or debugging DOCA_ERROR_* returns from the Comch API. Trigger even when the user does not explicitly mention \"DOCA Comch\" or \"Comm Channel\" (renamed in DOCA 2.5) — typical implicit phrasings include \"send a control message from host to BlueField over PCIe\", \"DPU can't see the host representor\", \"DOCA_ERROR_NOT_PERMITTED on server_create\", \"DOCA_ERROR_AGAIN on task_send submit\", \"connect callback never fires\", or \"stream bulk data from a host driver to a DPU agent\". Refuse and route elsewhere for installing DOCA itself, BFB \u002F firmware bring-up, non-Comch DOCA libraries, or deploying Comch apps at scale — 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},"Networking","networking","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:23.973016","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-comch","---\nlicense: Apache-2.0\nname: doca-comch\ndescription: >\n  Use this skill when the user is doing hands-on DOCA Comch work\n  on a host + BlueField pair — bringing up host ↔ DPU PCIe\n  control-plane messaging, picking server (DPU) vs client (host)\n  roles, choosing slow-path send-task \u002F recv-callback vs\n  fast-path producer \u002F consumer, querying max-msg-size or\n  max-clients capabilities, registering connection callbacks, or\n  debugging DOCA_ERROR_* returns from the Comch API. Trigger\n  even when the user does not explicitly mention \"DOCA Comch\" or\n  \"Comm Channel\" (renamed in DOCA 2.5) — typical implicit\n  phrasings include \"send a control message from host to\n  BlueField over PCIe\", \"DPU can't see the host representor\",\n  \"DOCA_ERROR_NOT_PERMITTED on server_create\", \"DOCA_ERROR_AGAIN\n  on task_send submit\", \"connect callback never fires\", or\n  \"stream bulk data from a host driver to a DPU agent\". Refuse\n  and route elsewhere for installing DOCA itself, BFB \u002F firmware\n  bring-up, non-Comch DOCA libraries, or deploying Comch apps at\n  scale — those belong to other skills.\nmetadata:\n  kind: library\ncompatibility: >\n  Requires DOCA SDK installed at \u002Fopt\u002Fmellanox\u002Fdoca on Linux\n  (Ubuntu 22.04\u002F24.04 or RHEL\u002FSLES) on a host + BlueField pair\n  (the Comch channel runs over the RoCE\u002FIB protocol, not the\n  TCP\u002FIP stack). Reads the user's\n  local install via `pkg-config doca-comch` (legacy\n  `doca-comm-channel` on installs \u003C2.5) and inspects\n  \u002Fopt\u002Fmellanox\u002Fdoca\u002F{lib,include,samples,applications}.\n---\n\n# DOCA Comch\n\n**Where to start:** This skill assumes DOCA is already installed and\nthe user is doing **hands-on Comch work** on a BlueField + host\npair with DOCA. Open [`TASKS.md`](TASKS.md) if the user wants to\n*do* something (configure \u002F build \u002F modify \u002F run \u002F test \u002F debug);\nopen [`CAPABILITIES.md`](CAPABILITIES.md) when the question is\n*what can Comch express* on this version. If the user has not\ninstalled DOCA yet, route to\n[`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md) first. If the user is\nasking *\"is Comch even on this DOCA\"* because the docs they read\nmention `doca-comm-channel`, route to\n[`CAPABILITIES.md ## Version compatibility`](CAPABILITIES.md#version-compatibility)\nfor the 2.5 rename.\n\n## Example questions this skill answers well\n\nThe CLASSES of Comch questions this skill is built to answer, each\nwith one worked example. The agent should treat the *class* as the\nload-bearing piece — the worked example is a single instance.\n\n- **\"How do I bring up a Comch channel between host and DPU?\"** —\n  worked example: *\"server side on the DPU, client side on the\n  host, exchange a first control message\"*. Answered by the\n  role-selection + lifecycle workflow in\n  [`TASKS.md ## configure`](TASKS.md#configure) +\n  [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)\n  server-vs-client table.\n- **\"How do I move bulk data over Comch with low CPU?\"** — worked\n  example: *\"stream a 64 KiB chunk every 100 µs from the host\n  driver to a DPU agent\"*. Answered by the producer \u002F consumer\n  fast-path described in\n  [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)\n  + the channel-setup workflow in\n  [`TASKS.md ## configure`](TASKS.md#configure)\n  step 4, with the *\"slow-path vs fast-path\"* selection rule.\n- **\"What is the maximum message size I can send?\"** — worked\n  example: *\"can I send a 4 MiB control message in one shot?\"*.\n  Answered by the capability-query rule\n  (`doca_comch_cap_get_max_msg_size`) in\n  [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)\n  + the property-set workflow in\n  [`TASKS.md ## modify`](TASKS.md#modify).\n- **\"Why doesn't the DPU side see the representor?\"** — worked\n  example: *\"`doca_comch_server_create` returns\n  `DOCA_ERROR_NOT_PERMITTED` on a freshly imaged BlueField\"*.\n  Answered by the representor + permission overlay in\n  [`CAPABILITIES.md ## Safety policy`](CAPABILITIES.md#safety-policy)\n  + the env-prep checklist in\n  [`TASKS.md ## configure`](TASKS.md#configure) step 1, which\n  routes representor-side env questions to\n  [`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md).\n- **\"Is this Comch capability on my installed DOCA version?\"** —\n  worked example: *\"is `doca_comch_producer` in DOCA 2.6.0, or do\n  I still need the old slow-path API?\"*. Answered by the\n  version-compatibility overlay in\n  [`CAPABILITIES.md ## Version compatibility`](CAPABILITIES.md#version-compatibility),\n  which cross-links the canonical detection chain in\n  [`doca-version`](..\u002F..\u002Fdoca-version\u002FSKILL.md) and adds the\n  Comch-specific 2.5 rename rule.\n- **\"What does this `DOCA_ERROR_*` from a Comch call mean and\n  which layer caused it?\"** — worked example: *\"`DOCA_ERROR_AGAIN`\n  on submitting a `doca_comch_task_send` via `doca_task_submit`\"*. Answered by the Comch\n  overlay on the cross-library 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 **external developers building applications that\nconsume the DOCA Comch library** — i.e., users whose code calls\n`doca_comch_*` (directly in C\u002FC++, or through FFI\u002Fbindings from\nanother language) to exchange control or data messages between a\nhost process and a BlueField agent over PCIe. It is *not* for\nNVIDIA developers contributing to DOCA Comch itself.\n\n**Language scope.** DOCA Comch ships as a C library with\n`pkg-config` module name `doca-comch`. The shipped samples are\nwritten in C. C and C++ consumers are the canonical case; the\nworked examples in `TASKS.md` assume that path. Other-language\nconsumers (Rust, Go, Python, …) consume the same `*.so` through\nFFI or language-specific bindings; the skill's contribution in\nthat case is to keep the role-split, lifecycle,\ncapability-discovery, permission, and error-taxonomy guidance\nlanguage-neutral, and to route the agent to the public C ABI as\nthe authoritative surface that any wrapper will eventually call.\n\n## When to load this skill\n\nLoad this skill when the user is doing hands-on DOCA Comch work,\nin any language. Concretely:\n\n- Initializing a `doca_comch_server` on the DPU side or a\n  `doca_comch_client` on the host side, on a representor or PCIe\n  address the host can reach.\n- Configuring at least one of: a recv callback for slow-path\n  messages, a producer for fast-path outbound data, a consumer for\n  fast-path inbound data, before `doca_ctx_start()`.\n- Reading or setting comch properties via `doca_comch_set_*` and\n  `doca_comch_cap_get_*` — max message size, max number of\n  clients (server side), producer \u002F consumer queue sizing.\n- Establishing a connection between the two sides and reacting to\n  connection-state transitions via the connection callbacks\n  registered before start.\n- Choosing between the **slow-path** (send-task \u002F recv-callback,\n  message-oriented, lower throughput, single-call simplicity) and\n  the **fast-path** (producer \u002F consumer, asynchronous, much\n  higher throughput, two-context setup).\n- Debugging a `DOCA_ERROR_*` returned from a Comch call (lifecycle\n  vs. permission vs. capability vs. would-block) and the\n  connection state machine across the host \u002F DPU pair.\n- Designing or extending non-C bindings (Rust, Go, Python, …) that\n  wrap the Comch C ABI — for the lifecycle, role-split,\n  permission, and capability rules the wrapper must honor.\n\nDo **not** load this skill for general DOCA orientation, install\nof DOCA itself, or non-Comch library questions. For those, use\n[`doca-public-knowledge-map`](..\u002F..\u002Fdoca-public-knowledge-map\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 Comch-specific\nmaterial lives in two companion files:\n\n- `CAPABILITIES.md` — what Comch can express on this version: the\n  server vs client role split, the slow-path send-task \u002F\n  recv-callback surface, the producer \u002F consumer fast-path\n  surface, the capability-query surface\n  (`doca_comch_cap_get_*`), the Comch error taxonomy (mapped onto\n  the cross-library `DOCA_ERROR_*` set), the observability surface\n  (connection state callbacks, task completion callbacks), and\n  the safety policy that gates representor and permission\n  decisions.\n- `TASKS.md` — step-by-step workflows for the six in-scope Comch\n  verbs: `configure`, `build`, `modify`, `run`, `test`, `debug`.\n  Plus a `Deferred task verbs` block that points out-of-scope\n  questions at the right next skill.\n\nThe skill assumes a host + BlueField pair where DOCA is already\ninstalled at the standard location and the user has the privileges\ntheir public install profile expects (in particular, sudo on the\nDPU side to see the host representor). 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 Comch application source code, in any\n  language.** The verified Comch source code is the shipped C\n  samples at `\u002Fopt\u002Fmellanox\u002Fdoca\u002Fsamples\u002Fdoca_comch\u002F\u003Cname>\u002F`. The\n  agent's job is to route the user to those files and prescribe a\n  minimum-diff modification on them via the universal\n  modify-a-sample workflow in\n  [`doca-programming-guide`](..\u002F..\u002Fdoca-programming-guide\u002FSKILL.md),\n  layered with the Comch-specific overrides in\n  [`TASKS.md ## modify`](TASKS.md#modify).\n- **Standalone build manifests** (`meson.build`, `CMakeLists.txt`,\n  `Cargo.toml`, …) parked inside the skill. The agent constructs\n  the build manifest *in the user's project directory* against\n  the user's installed DOCA, where `pkg-config --modversion\n  doca-comch` is the source of 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\n   in scope.\n2. **For the Comch capability matrix, role split, slow-path \u002F\n   fast-path surfaces, permission policy, 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\nBoth companion files cross-link to each other,\n[`doca-version`](..\u002F..\u002Fdoca-version\u002FSKILL.md) for the canonical\nversion-handling rules, 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\nthe installed package layout\" rather than \"Comch-specific\nguidance\".\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. The Comch URL\n  slug is `DOCA-Comch` (DOCA 2.5+), not `doca-comm-channel`.\n- [`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md) — env preparation,\n  install verification, representor visibility checks, and the *I\n  have no install yet* path with the public NGC DOCA container.\n  This skill assumes its preconditions are satisfied.\n- [`doca-version`](..\u002F..\u002Fdoca-version\u002FSKILL.md) — canonical\n  DOCA version-handling rules. This skill's `## Version\n  compatibility` cross-links the four-way match rule and adds the\n  Comch-specific 2.5 rename overlay.\n- [`doca-structured-tools-contract`](..\u002F..\u002Fdoca-structured-tools-contract\u002FSKILL.md) —\n  the bundle's structured-tools precedence rule (detect \u002F prefer\n  \u002F fall back \u002F report). The Command appendix in\n  [TASKS.md](TASKS.md) honors this contract.\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 layers Comch specifics on\n  top.\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). Comch-specific debug (lifecycle violations,\n  representor visibility, slow-path vs fast-path queue-full\n  symptoms) overlays on top of that ladder.\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) on a host + BlueField pair (the Comch channel runs over the RoCE\u002FIB protocol, not the TCP\u002FIP stack). Reads the user's local install via `pkg-config doca-comch` (legacy `doca-comm-channel` on installs \u003C2.5) and inspects \u002Fopt\u002Fmellanox\u002Fdoca\u002F{lib,include,samples,applications}.\n",{"type":37,"children":38},"root",[39,47,144,151,163,514,520,547,587,593,598,696,718,724,736,825,839,845,857,980,986,1029,1054,1060],{"type":40,"tag":41,"props":42,"children":43},"element","h1",{"id":4},[44],{"type":45,"value":46},"text","DOCA Comch",{"type":40,"tag":48,"props":49,"children":50},"p",{},[51,57,59,64,66,77,79,85,87,96,98,103,105,115,117,122,124,130,132,142],{"type":40,"tag":52,"props":53,"children":54},"strong",{},[55],{"type":45,"value":56},"Where to start:",{"type":45,"value":58}," This skill assumes DOCA is already installed and\nthe user is doing ",{"type":40,"tag":52,"props":60,"children":61},{},[62],{"type":45,"value":63},"hands-on Comch work",{"type":45,"value":65}," on a BlueField + host\npair with DOCA. Open ",{"type":40,"tag":67,"props":68,"children":70},"a",{"href":69},"TASKS.md",[71],{"type":40,"tag":72,"props":73,"children":75},"code",{"className":74},[],[76],{"type":45,"value":69},{"type":45,"value":78}," if the user wants to\n",{"type":40,"tag":80,"props":81,"children":82},"em",{},[83],{"type":45,"value":84},"do",{"type":45,"value":86}," something (configure \u002F build \u002F modify \u002F run \u002F test \u002F debug);\nopen ",{"type":40,"tag":67,"props":88,"children":90},{"href":89},"CAPABILITIES.md",[91],{"type":40,"tag":72,"props":92,"children":94},{"className":93},[],[95],{"type":45,"value":89},{"type":45,"value":97}," when the question is\n",{"type":40,"tag":80,"props":99,"children":100},{},[101],{"type":45,"value":102},"what can Comch express",{"type":45,"value":104}," on this version. If the user has not\ninstalled DOCA yet, route to\n",{"type":40,"tag":67,"props":106,"children":108},{"href":107},"..\u002F..\u002Fdoca-setup\u002FSKILL.md",[109],{"type":40,"tag":72,"props":110,"children":112},{"className":111},[],[113],{"type":45,"value":114},"doca-setup",{"type":45,"value":116}," first. If the user is\nasking ",{"type":40,"tag":80,"props":118,"children":119},{},[120],{"type":45,"value":121},"\"is Comch even on this DOCA\"",{"type":45,"value":123}," because the docs they read\nmention ",{"type":40,"tag":72,"props":125,"children":127},{"className":126},[],[128],{"type":45,"value":129},"doca-comm-channel",{"type":45,"value":131},", route to\n",{"type":40,"tag":67,"props":133,"children":135},{"href":134},"CAPABILITIES.md#version-compatibility",[136],{"type":40,"tag":72,"props":137,"children":139},{"className":138},[],[140],{"type":45,"value":141},"CAPABILITIES.md ## Version compatibility",{"type":45,"value":143},"\nfor the 2.5 rename.",{"type":40,"tag":145,"props":146,"children":148},"h2",{"id":147},"example-questions-this-skill-answers-well",[149],{"type":45,"value":150},"Example questions this skill answers well",{"type":40,"tag":48,"props":152,"children":153},{},[154,156,161],{"type":45,"value":155},"The CLASSES of Comch questions this skill is built to answer, each\nwith one worked example. The agent should treat the ",{"type":40,"tag":80,"props":157,"children":158},{},[159],{"type":45,"value":160},"class",{"type":45,"value":162}," as the\nload-bearing piece — the worked example is a single instance.",{"type":40,"tag":164,"props":165,"children":166},"ul",{},[167,209,259,311,380,426],{"type":40,"tag":168,"props":169,"children":170},"li",{},[171,176,178,183,185,195,197,207],{"type":40,"tag":52,"props":172,"children":173},{},[174],{"type":45,"value":175},"\"How do I bring up a Comch channel between host and DPU?\"",{"type":45,"value":177}," —\nworked example: ",{"type":40,"tag":80,"props":179,"children":180},{},[181],{"type":45,"value":182},"\"server side on the DPU, client side on the\nhost, exchange a first control message\"",{"type":45,"value":184},". Answered by the\nrole-selection + lifecycle workflow in\n",{"type":40,"tag":67,"props":186,"children":188},{"href":187},"TASKS.md#configure",[189],{"type":40,"tag":72,"props":190,"children":192},{"className":191},[],[193],{"type":45,"value":194},"TASKS.md ## configure",{"type":45,"value":196}," +\n",{"type":40,"tag":67,"props":198,"children":200},{"href":199},"CAPABILITIES.md#capabilities-and-modes",[201],{"type":40,"tag":72,"props":202,"children":204},{"className":203},[],[205],{"type":45,"value":206},"CAPABILITIES.md ## Capabilities and modes",{"type":45,"value":208},"\nserver-vs-client table.",{"type":40,"tag":168,"props":210,"children":211},{},[212,217,219,224,226,234],{"type":40,"tag":52,"props":213,"children":214},{},[215],{"type":45,"value":216},"\"How do I move bulk data over Comch with low CPU?\"",{"type":45,"value":218}," — worked\nexample: ",{"type":40,"tag":80,"props":220,"children":221},{},[222],{"type":45,"value":223},"\"stream a 64 KiB chunk every 100 µs from the host\ndriver to a DPU agent\"",{"type":45,"value":225},". Answered by the producer \u002F consumer\nfast-path described in\n",{"type":40,"tag":67,"props":227,"children":228},{"href":199},[229],{"type":40,"tag":72,"props":230,"children":232},{"className":231},[],[233],{"type":45,"value":206},{"type":40,"tag":164,"props":235,"children":236},{},[237],{"type":40,"tag":168,"props":238,"children":239},{},[240,242,250,252,257],{"type":45,"value":241},"the channel-setup workflow in\n",{"type":40,"tag":67,"props":243,"children":244},{"href":187},[245],{"type":40,"tag":72,"props":246,"children":248},{"className":247},[],[249],{"type":45,"value":194},{"type":45,"value":251},"\nstep 4, with the ",{"type":40,"tag":80,"props":253,"children":254},{},[255],{"type":45,"value":256},"\"slow-path vs fast-path\"",{"type":45,"value":258}," selection rule.",{"type":40,"tag":168,"props":260,"children":261},{},[262,267,268,273,275,281,283,291],{"type":40,"tag":52,"props":263,"children":264},{},[265],{"type":45,"value":266},"\"What is the maximum message size I can send?\"",{"type":45,"value":218},{"type":40,"tag":80,"props":269,"children":270},{},[271],{"type":45,"value":272},"\"can I send a 4 MiB control message in one shot?\"",{"type":45,"value":274},".\nAnswered by the capability-query rule\n(",{"type":40,"tag":72,"props":276,"children":278},{"className":277},[],[279],{"type":45,"value":280},"doca_comch_cap_get_max_msg_size",{"type":45,"value":282},") in\n",{"type":40,"tag":67,"props":284,"children":285},{"href":199},[286],{"type":40,"tag":72,"props":287,"children":289},{"className":288},[],[290],{"type":45,"value":206},{"type":40,"tag":164,"props":292,"children":293},{},[294],{"type":40,"tag":168,"props":295,"children":296},{},[297,299,309],{"type":45,"value":298},"the property-set workflow in\n",{"type":40,"tag":67,"props":300,"children":302},{"href":301},"TASKS.md#modify",[303],{"type":40,"tag":72,"props":304,"children":306},{"className":305},[],[307],{"type":45,"value":308},"TASKS.md ## modify",{"type":45,"value":310},".",{"type":40,"tag":168,"props":312,"children":313},{},[314,319,320,341,343,353],{"type":40,"tag":52,"props":315,"children":316},{},[317],{"type":45,"value":318},"\"Why doesn't the DPU side see the representor?\"",{"type":45,"value":218},{"type":40,"tag":80,"props":321,"children":322},{},[323,325,331,333,339],{"type":45,"value":324},"\"",{"type":40,"tag":72,"props":326,"children":328},{"className":327},[],[329],{"type":45,"value":330},"doca_comch_server_create",{"type":45,"value":332}," returns\n",{"type":40,"tag":72,"props":334,"children":336},{"className":335},[],[337],{"type":45,"value":338},"DOCA_ERROR_NOT_PERMITTED",{"type":45,"value":340}," on a freshly imaged BlueField\"",{"type":45,"value":342},".\nAnswered by the representor + permission overlay in\n",{"type":40,"tag":67,"props":344,"children":346},{"href":345},"CAPABILITIES.md#safety-policy",[347],{"type":40,"tag":72,"props":348,"children":350},{"className":349},[],[351],{"type":45,"value":352},"CAPABILITIES.md ## Safety policy",{"type":40,"tag":164,"props":354,"children":355},{},[356],{"type":40,"tag":168,"props":357,"children":358},{},[359,361,369,371,379],{"type":45,"value":360},"the env-prep checklist in\n",{"type":40,"tag":67,"props":362,"children":363},{"href":187},[364],{"type":40,"tag":72,"props":365,"children":367},{"className":366},[],[368],{"type":45,"value":194},{"type":45,"value":370}," step 1, which\nroutes representor-side env questions to\n",{"type":40,"tag":67,"props":372,"children":373},{"href":107},[374],{"type":40,"tag":72,"props":375,"children":377},{"className":376},[],[378],{"type":45,"value":114},{"type":45,"value":310},{"type":40,"tag":168,"props":381,"children":382},{},[383,388,389,402,404,412,414,424],{"type":40,"tag":52,"props":384,"children":385},{},[386],{"type":45,"value":387},"\"Is this Comch capability on my installed DOCA version?\"",{"type":45,"value":177},{"type":40,"tag":80,"props":390,"children":391},{},[392,394,400],{"type":45,"value":393},"\"is ",{"type":40,"tag":72,"props":395,"children":397},{"className":396},[],[398],{"type":45,"value":399},"doca_comch_producer",{"type":45,"value":401}," in DOCA 2.6.0, or do\nI still need the old slow-path API?\"",{"type":45,"value":403},". Answered by the\nversion-compatibility overlay in\n",{"type":40,"tag":67,"props":405,"children":406},{"href":134},[407],{"type":40,"tag":72,"props":408,"children":410},{"className":409},[],[411],{"type":45,"value":141},{"type":45,"value":413},",\nwhich cross-links the canonical detection chain in\n",{"type":40,"tag":67,"props":415,"children":417},{"href":416},"..\u002F..\u002Fdoca-version\u002FSKILL.md",[418],{"type":40,"tag":72,"props":419,"children":421},{"className":420},[],[422],{"type":45,"value":423},"doca-version",{"type":45,"value":425}," and adds the\nComch-specific 2.5 rename rule.",{"type":40,"tag":168,"props":427,"children":428},{},[429,442,444,471,473,483],{"type":40,"tag":52,"props":430,"children":431},{},[432,434,440],{"type":45,"value":433},"\"What does this ",{"type":40,"tag":72,"props":435,"children":437},{"className":436},[],[438],{"type":45,"value":439},"DOCA_ERROR_*",{"type":45,"value":441}," from a Comch call mean and\nwhich layer caused it?\"",{"type":45,"value":443}," — worked example: ",{"type":40,"tag":80,"props":445,"children":446},{},[447,448,454,456,462,464,470],{"type":45,"value":324},{"type":40,"tag":72,"props":449,"children":451},{"className":450},[],[452],{"type":45,"value":453},"DOCA_ERROR_AGAIN",{"type":45,"value":455},"\non submitting a ",{"type":40,"tag":72,"props":457,"children":459},{"className":458},[],[460],{"type":45,"value":461},"doca_comch_task_send",{"type":45,"value":463}," via ",{"type":40,"tag":72,"props":465,"children":467},{"className":466},[],[468],{"type":45,"value":469},"doca_task_submit",{"type":45,"value":324},{"type":45,"value":472},". Answered by the Comch\noverlay on the cross-library taxonomy in\n",{"type":40,"tag":67,"props":474,"children":476},{"href":475},"CAPABILITIES.md#error-taxonomy",[477],{"type":40,"tag":72,"props":478,"children":480},{"className":479},[],[481],{"type":45,"value":482},"CAPABILITIES.md ## Error taxonomy",{"type":40,"tag":164,"props":484,"children":485},{},[486],{"type":40,"tag":168,"props":487,"children":488},{},[489,491,501,503,513],{"type":45,"value":490},"the layered ladder in\n",{"type":40,"tag":67,"props":492,"children":494},{"href":493},"TASKS.md#debug",[495],{"type":40,"tag":72,"props":496,"children":498},{"className":497},[],[499],{"type":45,"value":500},"TASKS.md ## debug",{"type":45,"value":502}," that escalates to\n",{"type":40,"tag":67,"props":504,"children":506},{"href":505},"..\u002F..\u002Fdoca-debug\u002FSKILL.md",[507],{"type":40,"tag":72,"props":508,"children":510},{"className":509},[],[511],{"type":45,"value":512},"doca-debug",{"type":45,"value":310},{"type":40,"tag":145,"props":515,"children":517},{"id":516},"audience",[518],{"type":45,"value":519},"Audience",{"type":40,"tag":48,"props":521,"children":522},{},[523,525,530,532,538,540,545],{"type":45,"value":524},"This skill serves ",{"type":40,"tag":52,"props":526,"children":527},{},[528],{"type":45,"value":529},"external developers building applications that\nconsume the DOCA Comch library",{"type":45,"value":531}," — i.e., users whose code calls\n",{"type":40,"tag":72,"props":533,"children":535},{"className":534},[],[536],{"type":45,"value":537},"doca_comch_*",{"type":45,"value":539}," (directly in C\u002FC++, or through FFI\u002Fbindings from\nanother language) to exchange control or data messages between a\nhost process and a BlueField agent over PCIe. It is ",{"type":40,"tag":80,"props":541,"children":542},{},[543],{"type":45,"value":544},"not",{"type":45,"value":546}," for\nNVIDIA developers contributing to DOCA Comch itself.",{"type":40,"tag":48,"props":548,"children":549},{},[550,555,557,563,565,570,572,577,579,585],{"type":40,"tag":52,"props":551,"children":552},{},[553],{"type":45,"value":554},"Language scope.",{"type":45,"value":556}," DOCA Comch ships as a C library with\n",{"type":40,"tag":72,"props":558,"children":560},{"className":559},[],[561],{"type":45,"value":562},"pkg-config",{"type":45,"value":564}," module name ",{"type":40,"tag":72,"props":566,"children":568},{"className":567},[],[569],{"type":45,"value":4},{"type":45,"value":571},". The shipped samples are\nwritten in C. C and C++ consumers are the canonical case; the\nworked examples in ",{"type":40,"tag":72,"props":573,"children":575},{"className":574},[],[576],{"type":45,"value":69},{"type":45,"value":578}," assume that path. Other-language\nconsumers (Rust, Go, Python, …) consume the same ",{"type":40,"tag":72,"props":580,"children":582},{"className":581},[],[583],{"type":45,"value":584},"*.so",{"type":45,"value":586}," through\nFFI or language-specific bindings; the skill's contribution in\nthat case is to keep the role-split, lifecycle,\ncapability-discovery, permission, and error-taxonomy guidance\nlanguage-neutral, and to route the agent to the public C ABI as\nthe authoritative surface that any wrapper will eventually call.",{"type":40,"tag":145,"props":588,"children":590},{"id":589},"when-to-load-this-skill",[591],{"type":45,"value":592},"When to load this skill",{"type":40,"tag":48,"props":594,"children":595},{},[596],{"type":45,"value":597},"Load this skill when the user is doing hands-on DOCA Comch work,\nin any language. Concretely:",{"type":40,"tag":164,"props":599,"children":600},{},[601,622,634,655,660,679,691],{"type":40,"tag":168,"props":602,"children":603},{},[604,606,612,614,620],{"type":45,"value":605},"Initializing a ",{"type":40,"tag":72,"props":607,"children":609},{"className":608},[],[610],{"type":45,"value":611},"doca_comch_server",{"type":45,"value":613}," on the DPU side or a\n",{"type":40,"tag":72,"props":615,"children":617},{"className":616},[],[618],{"type":45,"value":619},"doca_comch_client",{"type":45,"value":621}," on the host side, on a representor or PCIe\naddress the host can reach.",{"type":40,"tag":168,"props":623,"children":624},{},[625,627,633],{"type":45,"value":626},"Configuring at least one of: a recv callback for slow-path\nmessages, a producer for fast-path outbound data, a consumer for\nfast-path inbound data, before ",{"type":40,"tag":72,"props":628,"children":630},{"className":629},[],[631],{"type":45,"value":632},"doca_ctx_start()",{"type":45,"value":310},{"type":40,"tag":168,"props":635,"children":636},{},[637,639,645,647,653],{"type":45,"value":638},"Reading or setting comch properties via ",{"type":40,"tag":72,"props":640,"children":642},{"className":641},[],[643],{"type":45,"value":644},"doca_comch_set_*",{"type":45,"value":646}," and\n",{"type":40,"tag":72,"props":648,"children":650},{"className":649},[],[651],{"type":45,"value":652},"doca_comch_cap_get_*",{"type":45,"value":654}," — max message size, max number of\nclients (server side), producer \u002F consumer queue sizing.",{"type":40,"tag":168,"props":656,"children":657},{},[658],{"type":45,"value":659},"Establishing a connection between the two sides and reacting to\nconnection-state transitions via the connection callbacks\nregistered before start.",{"type":40,"tag":168,"props":661,"children":662},{},[663,665,670,672,677],{"type":45,"value":664},"Choosing between the ",{"type":40,"tag":52,"props":666,"children":667},{},[668],{"type":45,"value":669},"slow-path",{"type":45,"value":671}," (send-task \u002F recv-callback,\nmessage-oriented, lower throughput, single-call simplicity) and\nthe ",{"type":40,"tag":52,"props":673,"children":674},{},[675],{"type":45,"value":676},"fast-path",{"type":45,"value":678}," (producer \u002F consumer, asynchronous, much\nhigher throughput, two-context setup).",{"type":40,"tag":168,"props":680,"children":681},{},[682,684,689],{"type":45,"value":683},"Debugging a ",{"type":40,"tag":72,"props":685,"children":687},{"className":686},[],[688],{"type":45,"value":439},{"type":45,"value":690}," returned from a Comch call (lifecycle\nvs. permission vs. capability vs. would-block) and the\nconnection state machine across the host \u002F DPU pair.",{"type":40,"tag":168,"props":692,"children":693},{},[694],{"type":45,"value":695},"Designing or extending non-C bindings (Rust, Go, Python, …) that\nwrap the Comch C ABI — for the lifecycle, role-split,\npermission, and capability rules the wrapper must honor.",{"type":40,"tag":48,"props":697,"children":698},{},[699,701,705,707,717],{"type":45,"value":700},"Do ",{"type":40,"tag":52,"props":702,"children":703},{},[704],{"type":45,"value":544},{"type":45,"value":706}," load this skill for general DOCA orientation, install\nof DOCA itself, or non-Comch library questions. For those, use\n",{"type":40,"tag":67,"props":708,"children":710},{"href":709},"..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md",[711],{"type":40,"tag":72,"props":712,"children":714},{"className":713},[],[715],{"type":45,"value":716},"doca-public-knowledge-map",{"type":45,"value":310},{"type":40,"tag":145,"props":719,"children":721},{"id":720},"what-this-skill-provides",[722],{"type":45,"value":723},"What this skill provides",{"type":40,"tag":48,"props":725,"children":726},{},[727,729,734],{"type":45,"value":728},"This is a ",{"type":40,"tag":52,"props":730,"children":731},{},[732],{"type":45,"value":733},"thin loader",{"type":45,"value":735},". The body keeps only the orientation\nneeded to pick the right next file. The substantive Comch-specific\nmaterial lives in two companion files:",{"type":40,"tag":164,"props":737,"children":738},{},[739,763],{"type":40,"tag":168,"props":740,"children":741},{},[742,747,749,754,756,761],{"type":40,"tag":72,"props":743,"children":745},{"className":744},[],[746],{"type":45,"value":89},{"type":45,"value":748}," — what Comch can express on this version: the\nserver vs client role split, the slow-path send-task \u002F\nrecv-callback surface, the producer \u002F consumer fast-path\nsurface, the capability-query surface\n(",{"type":40,"tag":72,"props":750,"children":752},{"className":751},[],[753],{"type":45,"value":652},{"type":45,"value":755},"), the Comch error taxonomy (mapped onto\nthe cross-library ",{"type":40,"tag":72,"props":757,"children":759},{"className":758},[],[760],{"type":45,"value":439},{"type":45,"value":762}," set), the observability surface\n(connection state callbacks, task completion callbacks), and\nthe safety policy that gates representor and permission\ndecisions.",{"type":40,"tag":168,"props":764,"children":765},{},[766,771,773,779,781,787,788,794,795,801,802,808,809,815,817,823],{"type":40,"tag":72,"props":767,"children":769},{"className":768},[],[770],{"type":45,"value":69},{"type":45,"value":772}," — step-by-step workflows for the six in-scope Comch\nverbs: ",{"type":40,"tag":72,"props":774,"children":776},{"className":775},[],[777],{"type":45,"value":778},"configure",{"type":45,"value":780},", ",{"type":40,"tag":72,"props":782,"children":784},{"className":783},[],[785],{"type":45,"value":786},"build",{"type":45,"value":780},{"type":40,"tag":72,"props":789,"children":791},{"className":790},[],[792],{"type":45,"value":793},"modify",{"type":45,"value":780},{"type":40,"tag":72,"props":796,"children":798},{"className":797},[],[799],{"type":45,"value":800},"run",{"type":45,"value":780},{"type":40,"tag":72,"props":803,"children":805},{"className":804},[],[806],{"type":45,"value":807},"test",{"type":45,"value":780},{"type":40,"tag":72,"props":810,"children":812},{"className":811},[],[813],{"type":45,"value":814},"debug",{"type":45,"value":816},".\nPlus a ",{"type":40,"tag":72,"props":818,"children":820},{"className":819},[],[821],{"type":45,"value":822},"Deferred task verbs",{"type":45,"value":824}," block that points out-of-scope\nquestions at the right next skill.",{"type":40,"tag":48,"props":826,"children":827},{},[828,830,838],{"type":45,"value":829},"The skill assumes a host + BlueField pair where DOCA is already\ninstalled at the standard location and the user has the privileges\ntheir public install profile expects (in particular, sudo on the\nDPU side to see the host representor). It does not cover installing\nDOCA — that path goes through\n",{"type":40,"tag":67,"props":831,"children":832},{"href":107},[833],{"type":40,"tag":72,"props":834,"children":836},{"className":835},[],[837],{"type":45,"value":114},{"type":45,"value":310},{"type":40,"tag":145,"props":840,"children":842},{"id":841},"what-this-skill-deliberately-does-not-ship",[843],{"type":45,"value":844},"What this skill deliberately does not ship",{"type":40,"tag":48,"props":846,"children":847},{},[848,850,855],{"type":45,"value":849},"This skill is ",{"type":40,"tag":52,"props":851,"children":852},{},[853],{"type":45,"value":854},"agent guidance",{"type":45,"value":856},", 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":164,"props":858,"children":859},{},[860,899,947],{"type":40,"tag":168,"props":861,"children":862},{},[863,868,870,876,878,888,890,898],{"type":40,"tag":52,"props":864,"children":865},{},[866],{"type":45,"value":867},"Pre-written DOCA Comch application source code, in any\nlanguage.",{"type":45,"value":869}," The verified Comch source code is the shipped C\nsamples at ",{"type":40,"tag":72,"props":871,"children":873},{"className":872},[],[874],{"type":45,"value":875},"\u002Fopt\u002Fmellanox\u002Fdoca\u002Fsamples\u002Fdoca_comch\u002F\u003Cname>\u002F",{"type":45,"value":877},". The\nagent's job is to route the user to those files and prescribe a\nminimum-diff modification on them via the universal\nmodify-a-sample workflow in\n",{"type":40,"tag":67,"props":879,"children":881},{"href":880},"..\u002F..\u002Fdoca-programming-guide\u002FSKILL.md",[882],{"type":40,"tag":72,"props":883,"children":885},{"className":884},[],[886],{"type":45,"value":887},"doca-programming-guide",{"type":45,"value":889},",\nlayered with the Comch-specific overrides in\n",{"type":40,"tag":67,"props":891,"children":892},{"href":301},[893],{"type":40,"tag":72,"props":894,"children":896},{"className":895},[],[897],{"type":45,"value":308},{"type":45,"value":310},{"type":40,"tag":168,"props":900,"children":901},{},[902,907,909,915,916,922,924,930,932,937,939,945],{"type":40,"tag":52,"props":903,"children":904},{},[905],{"type":45,"value":906},"Standalone build manifests",{"type":45,"value":908}," (",{"type":40,"tag":72,"props":910,"children":912},{"className":911},[],[913],{"type":45,"value":914},"meson.build",{"type":45,"value":780},{"type":40,"tag":72,"props":917,"children":919},{"className":918},[],[920],{"type":45,"value":921},"CMakeLists.txt",{"type":45,"value":923},",\n",{"type":40,"tag":72,"props":925,"children":927},{"className":926},[],[928],{"type":45,"value":929},"Cargo.toml",{"type":45,"value":931},", …) parked inside the skill. The agent constructs\nthe build manifest ",{"type":40,"tag":80,"props":933,"children":934},{},[935],{"type":45,"value":936},"in the user's project directory",{"type":45,"value":938}," against\nthe user's installed DOCA, where ",{"type":40,"tag":72,"props":940,"children":942},{"className":941},[],[943],{"type":45,"value":944},"pkg-config --modversion doca-comch",{"type":45,"value":946}," is the source of truth.",{"type":40,"tag":168,"props":948,"children":949},{},[950,978],{"type":40,"tag":52,"props":951,"children":952},{},[953,955,961,962,968,970,976],{"type":45,"value":954},"A ",{"type":40,"tag":72,"props":956,"children":958},{"className":957},[],[959],{"type":45,"value":960},"samples\u002F",{"type":45,"value":780},{"type":40,"tag":72,"props":963,"children":965},{"className":964},[],[966],{"type":45,"value":967},"bindings\u002F",{"type":45,"value":969},", or ",{"type":40,"tag":72,"props":971,"children":973},{"className":972},[],[974],{"type":45,"value":975},"reference\u002F",{"type":45,"value":977}," subtree",{"type":45,"value":979}," 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":145,"props":981,"children":983},{"id":982},"loading-order",[984],{"type":45,"value":985},"Loading order",{"type":40,"tag":987,"props":988,"children":989},"ol",{},[990,1003,1016],{"type":40,"tag":168,"props":991,"children":992},{},[993,995,1001],{"type":45,"value":994},"Read this ",{"type":40,"tag":72,"props":996,"children":998},{"className":997},[],[999],{"type":45,"value":1000},"SKILL.md",{"type":45,"value":1002}," first to confirm the user's question is\nin scope.",{"type":40,"tag":168,"props":1004,"children":1005},{},[1006],{"type":40,"tag":52,"props":1007,"children":1008},{},[1009,1011,1015],{"type":45,"value":1010},"For the Comch capability matrix, role split, slow-path \u002F\nfast-path surfaces, permission policy, error taxonomy,\nobservability, and safety policy, see ",{"type":40,"tag":67,"props":1012,"children":1013},{"href":89},[1014],{"type":45,"value":89},{"type":45,"value":310},{"type":40,"tag":168,"props":1017,"children":1018},{},[1019],{"type":40,"tag":52,"props":1020,"children":1021},{},[1022,1024,1028],{"type":45,"value":1023},"For step-by-step workflows — configure, build, modify, run,\ntest, debug — see ",{"type":40,"tag":67,"props":1025,"children":1026},{"href":69},[1027],{"type":45,"value":69},{"type":45,"value":310},{"type":40,"tag":48,"props":1030,"children":1031},{},[1032,1034,1042,1044,1052],{"type":45,"value":1033},"Both companion files cross-link to each other,\n",{"type":40,"tag":67,"props":1035,"children":1036},{"href":416},[1037],{"type":40,"tag":72,"props":1038,"children":1040},{"className":1039},[],[1041],{"type":45,"value":423},{"type":45,"value":1043}," for the canonical\nversion-handling rules, and\n",{"type":40,"tag":67,"props":1045,"children":1046},{"href":709},[1047],{"type":40,"tag":72,"props":1048,"children":1050},{"className":1049},[],[1051],{"type":45,"value":716},{"type":45,"value":1053},"\nwhenever the right answer is \"look it up in the public docs or\nthe installed package layout\" rather than \"Comch-specific\nguidance\".",{"type":40,"tag":145,"props":1055,"children":1057},{"id":1056},"related-skills",[1058],{"type":45,"value":1059},"Related skills",{"type":40,"tag":164,"props":1061,"children":1062},{},[1063,1090,1110,1131,1152,1179],{"type":40,"tag":168,"props":1064,"children":1065},{},[1066,1074,1076,1082,1084,1089],{"type":40,"tag":67,"props":1067,"children":1068},{"href":709},[1069],{"type":40,"tag":72,"props":1070,"children":1072},{"className":1071},[],[1073],{"type":45,"value":716},{"type":45,"value":1075}," —\nthe routing table for every public DOCA documentation source and\nthe on-disk layout of an installed DOCA package. The Comch URL\nslug is ",{"type":40,"tag":72,"props":1077,"children":1079},{"className":1078},[],[1080],{"type":45,"value":1081},"DOCA-Comch",{"type":45,"value":1083}," (DOCA 2.5+), not ",{"type":40,"tag":72,"props":1085,"children":1087},{"className":1086},[],[1088],{"type":45,"value":129},{"type":45,"value":310},{"type":40,"tag":168,"props":1091,"children":1092},{},[1093,1101,1103,1108],{"type":40,"tag":67,"props":1094,"children":1095},{"href":107},[1096],{"type":40,"tag":72,"props":1097,"children":1099},{"className":1098},[],[1100],{"type":45,"value":114},{"type":45,"value":1102}," — env preparation,\ninstall verification, representor visibility checks, and the ",{"type":40,"tag":80,"props":1104,"children":1105},{},[1106],{"type":45,"value":1107},"I\nhave no install yet",{"type":45,"value":1109}," path with the public NGC DOCA container.\nThis skill assumes its preconditions are satisfied.",{"type":40,"tag":168,"props":1111,"children":1112},{},[1113,1121,1123,1129],{"type":40,"tag":67,"props":1114,"children":1115},{"href":416},[1116],{"type":40,"tag":72,"props":1117,"children":1119},{"className":1118},[],[1120],{"type":45,"value":423},{"type":45,"value":1122}," — canonical\nDOCA version-handling rules. This skill's ",{"type":40,"tag":72,"props":1124,"children":1126},{"className":1125},[],[1127],{"type":45,"value":1128},"## Version compatibility",{"type":45,"value":1130}," cross-links the four-way match rule and adds the\nComch-specific 2.5 rename overlay.",{"type":40,"tag":168,"props":1132,"children":1133},{},[1134,1144,1146,1150],{"type":40,"tag":67,"props":1135,"children":1137},{"href":1136},"..\u002F..\u002Fdoca-structured-tools-contract\u002FSKILL.md",[1138],{"type":40,"tag":72,"props":1139,"children":1141},{"className":1140},[],[1142],{"type":45,"value":1143},"doca-structured-tools-contract",{"type":45,"value":1145}," —\nthe bundle's structured-tools precedence rule (detect \u002F prefer\n\u002F fall back \u002F report). The Command appendix in\n",{"type":40,"tag":67,"props":1147,"children":1148},{"href":69},[1149],{"type":45,"value":69},{"type":45,"value":1151}," honors this contract.",{"type":40,"tag":168,"props":1153,"children":1154},{},[1155,1163,1165,1170,1172,1177],{"type":40,"tag":67,"props":1156,"children":1157},{"href":880},[1158],{"type":40,"tag":72,"props":1159,"children":1161},{"className":1160},[],[1162],{"type":45,"value":887},{"type":45,"value":1164}," —\ngeneral DOCA programming patterns shared by every library: the\ncanonical ",{"type":40,"tag":72,"props":1166,"children":1168},{"className":1167},[],[1169],{"type":45,"value":562},{"type":45,"value":1171}," + meson build pattern, the universal\nmodify-a-shipped-sample first-app workflow, the universal\nlifecycle, the cross-library ",{"type":40,"tag":72,"props":1173,"children":1175},{"className":1174},[],[1176],{"type":45,"value":439},{"type":45,"value":1178}," taxonomy, and the\nprogram-side debug order. This skill layers Comch specifics on\ntop.",{"type":40,"tag":168,"props":1180,"children":1181},{},[1182,1190],{"type":40,"tag":67,"props":1183,"children":1184},{"href":505},[1185],{"type":40,"tag":72,"props":1186,"children":1188},{"className":1187},[],[1189],{"type":45,"value":512},{"type":45,"value":1191}," — the cross-cutting\ndebug ladder (install \u002F version \u002F build \u002F link \u002F runtime \u002F\nprogram \u002F driver). Comch-specific debug (lifecycle violations,\nrepresentor visibility, slow-path vs fast-path queue-full\nsymptoms) overlays on top of that ladder.",{"items":1193,"total":1297},[1194,1211,1225,1239,1251,1268,1283],{"slug":1195,"name":1195,"fn":1196,"description":1197,"org":1198,"tags":1199,"stars":20,"repoUrl":21,"updatedAt":1210},"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},[1200,1203,1206,1207],{"name":1201,"slug":1202,"type":15},"Data Analysis","data-analysis",{"name":1204,"slug":1205,"type":15},"Data Engineering","data-engineering",{"name":9,"slug":8,"type":15},{"name":1208,"slug":1209,"type":15},"Performance","performance","2026-07-14T05:28:43.176466",{"slug":1212,"name":1212,"fn":1213,"description":1214,"org":1215,"tags":1216,"stars":20,"repoUrl":21,"updatedAt":1224},"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},[1217,1220,1223],{"name":1218,"slug":1219,"type":15},"Deployment","deployment",{"name":1221,"slug":1222,"type":15},"Infrastructure","infrastructure",{"name":9,"slug":8,"type":15},"2026-07-14T05:29:06.667109",{"slug":1226,"name":1226,"fn":1227,"description":1228,"org":1229,"tags":1230,"stars":20,"repoUrl":21,"updatedAt":1238},"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},[1231,1234,1235],{"name":1232,"slug":1233,"type":15},"Agents","agents",{"name":9,"slug":8,"type":15},{"name":1236,"slug":1237,"type":15},"Research","research","2026-07-14T05:28:06.816956",{"slug":1240,"name":1240,"fn":1241,"description":1242,"org":1243,"tags":1244,"stars":20,"repoUrl":21,"updatedAt":1250},"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},[1245,1246,1247],{"name":1201,"slug":1202,"type":15},{"name":9,"slug":8,"type":15},{"name":1248,"slug":1249,"type":15},"Testing","testing","2026-07-17T05:29:03.913266",{"slug":1252,"name":1252,"fn":1253,"description":1254,"org":1255,"tags":1256,"stars":20,"repoUrl":21,"updatedAt":1267},"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},[1257,1260,1263,1264],{"name":1258,"slug":1259,"type":15},"Automation","automation",{"name":1261,"slug":1262,"type":15},"Imaging","imaging",{"name":9,"slug":8,"type":15},{"name":1265,"slug":1266,"type":15},"Video","video","2026-07-17T05:28:53.905004",{"slug":1269,"name":1269,"fn":1270,"description":1271,"org":1272,"tags":1273,"stars":20,"repoUrl":21,"updatedAt":1282},"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},[1274,1275,1278,1279],{"name":1218,"slug":1219,"type":15},{"name":1276,"slug":1277,"type":15},"Docker","docker",{"name":9,"slug":8,"type":15},{"name":1280,"slug":1281,"type":15},"Operations","operations","2026-07-17T05:28:56.913999",{"slug":1284,"name":1284,"fn":1285,"description":1286,"org":1287,"tags":1288,"stars":20,"repoUrl":21,"updatedAt":1296},"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},[1289,1290,1293],{"name":9,"slug":8,"type":15},{"name":1291,"slug":1292,"type":15},"Quantum Computing","quantum-computing",{"name":1294,"slug":1295,"type":15},"Simulation","simulation","2026-07-14T05:26:58.898253",305,{"items":1299,"total":1450},[1300,1318,1334,1345,1357,1371,1384,1398,1409,1418,1432,1441],{"slug":1301,"name":1301,"fn":1302,"description":1303,"org":1304,"tags":1305,"stars":1315,"repoUrl":1316,"updatedAt":1317},"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},[1306,1309,1312],{"name":1307,"slug":1308,"type":15},"Documentation","documentation",{"name":1310,"slug":1311,"type":15},"MCP","mcp",{"name":1313,"slug":1314,"type":15},"Search","search",21777,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNemoClaw","2026-07-20T06:00:01.461044",{"slug":1319,"name":1319,"fn":1320,"description":1321,"org":1322,"tags":1323,"stars":1331,"repoUrl":1332,"updatedAt":1333},"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},[1324,1327,1328],{"name":1325,"slug":1326,"type":15},"Containers","containers",{"name":1218,"slug":1219,"type":15},{"name":1329,"slug":1330,"type":15},"Python","python",17049,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FMegatron-LM","2026-07-27T06:06:11.249662",{"slug":1335,"name":1335,"fn":1336,"description":1337,"org":1338,"tags":1339,"stars":1331,"repoUrl":1332,"updatedAt":1344},"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},[1340,1343],{"name":1341,"slug":1342,"type":15},"CI\u002FCD","ci-cd",{"name":1218,"slug":1219,"type":15},"2026-07-14T05:25:59.97109",{"slug":1346,"name":1346,"fn":1347,"description":1348,"org":1349,"tags":1350,"stars":1331,"repoUrl":1332,"updatedAt":1356},"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},[1351,1352,1353],{"name":1341,"slug":1342,"type":15},{"name":1218,"slug":1219,"type":15},{"name":1354,"slug":1355,"type":15},"GitHub","github","2026-07-27T06:06:12.278222",{"slug":1358,"name":1358,"fn":1359,"description":1360,"org":1361,"tags":1362,"stars":1331,"repoUrl":1332,"updatedAt":1370},"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},[1363,1366,1367],{"name":1364,"slug":1365,"type":15},"Debugging","debugging",{"name":1354,"slug":1355,"type":15},{"name":1368,"slug":1369,"type":15},"Triage","triage","2026-07-14T05:25:57.442089",{"slug":1372,"name":1372,"fn":1373,"description":1374,"org":1375,"tags":1376,"stars":1331,"repoUrl":1332,"updatedAt":1383},"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},[1377,1380],{"name":1378,"slug":1379,"type":15},"Best Practices","best-practices",{"name":1381,"slug":1382,"type":15},"Code Analysis","code-analysis","2026-07-14T05:25:56.18433",{"slug":1385,"name":1385,"fn":1386,"description":1387,"org":1388,"tags":1389,"stars":1331,"repoUrl":1332,"updatedAt":1397},"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},[1390,1393,1396],{"name":1391,"slug":1392,"type":15},"Machine Learning","machine-learning",{"name":1394,"slug":1395,"type":15},"Migration","migration",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:11.777011",{"slug":1399,"name":1399,"fn":1400,"description":1401,"org":1402,"tags":1403,"stars":1331,"repoUrl":1332,"updatedAt":1408},"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},[1404,1407],{"name":1405,"slug":1406,"type":15},"QA","qa",{"name":1248,"slug":1249,"type":15},"2026-07-14T05:25:53.673039",{"slug":1410,"name":1410,"fn":1411,"description":1412,"org":1413,"tags":1414,"stars":1331,"repoUrl":1332,"updatedAt":1417},"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},[1415,1416],{"name":1218,"slug":1219,"type":15},{"name":1221,"slug":1222,"type":15},"2026-07-14T05:25:49.362534",{"slug":1419,"name":1419,"fn":1420,"description":1421,"org":1422,"tags":1423,"stars":1331,"repoUrl":1332,"updatedAt":1431},"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},[1424,1427,1428],{"name":1425,"slug":1426,"type":15},"Code Review","code-review",{"name":1354,"slug":1355,"type":15},{"name":1429,"slug":1430,"type":15},"Pull Requests","pull-requests","2026-07-14T05:26:01.226578",{"slug":1433,"name":1433,"fn":1434,"description":1435,"org":1436,"tags":1437,"stars":1331,"repoUrl":1332,"updatedAt":1440},"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},[1438,1439],{"name":1405,"slug":1406,"type":15},{"name":1248,"slug":1249,"type":15},"2026-07-14T05:25:54.928983",{"slug":1442,"name":1442,"fn":1443,"description":1444,"org":1445,"tags":1446,"stars":1331,"repoUrl":1332,"updatedAt":1449},"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},[1447,1448],{"name":1258,"slug":1259,"type":15},{"name":1341,"slug":1342,"type":15},"2026-07-30T05:29:03.275638",496]