[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-nvidia-doca-comm-channel-admin":3,"mdc--xpxist-key":31,"related-org-nvidia-doca-comm-channel-admin":1256,"related-repo-nvidia-doca-comm-channel-admin":1417},{"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-comm-channel-admin","administer DOCA communication channel connections","Use this skill to enumerate host↔DPU DOCA comch (formerly Comm Channel) servers and connections via the shipped doca_comm_channel_admin binary — listing comch-capable devices and decoding the per-device server \u002F connection table (server name, PID, in-use \u002F max, PCIe address). The shipped binary is a SINGLE-SHOT SCAN-AND-PRINT tool with no registered arguments — NO list \u002F inspect \u002F drain \u002F restart subcommands; one inventory pass over every comch-capable doca_dev on this side. Channel reset \u002F drain \u002F restart go to doca-comch (program side), doca-setup \u002F doca-hardware-safety (driver reload), or BFB \u002F RShim — NOT to this binary. Trigger on phrasings like \"list comch servers\", \"which channels are active on this BlueField\", or \"verify admin tool sees same channel as program.\" Refuse and route elsewhere for the comch programming API, library install, protocol design, channel reset, or general orientation.\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},"Operations","operations","tag",{"name":9,"slug":8,"type":15},{"name":18,"slug":19,"type":15},"Engineering","engineering",2473,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fskills","2026-07-30T05:28:49.403675","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-comm-channel-admin","---\nlicense: Apache-2.0\nname: doca-comm-channel-admin\ndescription: >\n  Use this skill to enumerate host↔DPU DOCA comch (formerly\n  Comm Channel) servers and connections via the shipped\n  doca_comm_channel_admin binary — listing comch-capable\n  devices and decoding the per-device server \u002F connection\n  table (server name, PID, in-use \u002F max, PCIe address). The\n  shipped binary is a SINGLE-SHOT SCAN-AND-PRINT tool with no\n  registered arguments — NO list \u002F inspect \u002F drain \u002F restart\n  subcommands; one inventory pass over every comch-capable\n  doca_dev on this side. Channel reset \u002F drain \u002F restart go to\n  doca-comch (program side), doca-setup \u002F doca-hardware-safety\n  (driver reload), or BFB \u002F RShim — NOT to this binary.\n  Trigger on phrasings like \"list comch servers\", \"which\n  channels are active on this BlueField\", or \"verify admin\n  tool sees same channel as program.\" Refuse and route\n  elsewhere for the comch programming API, library install,\n  protocol design, channel reset, or general orientation.\nmetadata:\n  kind: tool\ncompatibility: >\n  Requires DOCA SDK installed at \u002Fopt\u002Fmellanox\u002Fdoca on Linux\n  (Ubuntu 22.04\u002F24.04 or RHEL\u002FSLES) with the Comm Channel tooling\n  subpackage so the CLI is present under\n  \u002Fopt\u002Fmellanox\u002Fdoca\u002Ftools\u002F. Runs from either the x86\u002FArm host or\n  the BlueField Arm side; a live host↔DPU comch channel created\n  via the doca-comch library is needed for non-empty tables.\n---\n\n# DOCA Comm Channel Admin Tool\n\n> **Actual binary contract.** `doca_comm_channel_admin` is one\n> zero-application-argument, read-only scan-and-print operation.\n> It scans every comch-capable `doca_dev` on the current side via\n> `resourcedump` (MFT) and prints SERVERS and CONNECTIONS tables.\n> It has no list, inspect, device-scope, drain, restart, or other\n> application operation. This skill does not retain conceptual\n> workflows under invented command names.\n\n**Where to start:** This is a tool skill for invoking the DOCA Comm\nChannel Admin Tool — the **read-only inventory** CLI counterpart\nto the [`doca-comch`](..\u002F..\u002Flibs\u002Fdoca-comch\u002FSKILL.md) library. The\nshipped `doca_comm_channel_admin` binary takes **no arguments\nbeyond ARGP defaults** (`--help`, `--version`, `--log-level`,\n`--sdk-log-level`, `--json`) and performs **one inventory pass**\nper invocation: it walks every `doca_dev` on this side, filters\nto comch-capable devices, shells out to `resourcedump` (MFT) on\neach, and prints two ASCII tables (SERVERS and CONNECTIONS).\nThere is no `list` subcommand, no `inspect` subcommand, no\n`drain` flag, and no `restart` flag — those are not part of the\ntool's surface. Open [`TASKS.md`](TASKS.md) and start at\n[`## run`](TASKS.md#run) for the single-shot invocation, or\n[`## debug`](TASKS.md#debug) when the user reports the tool sees\na different channel set than the program. Open\n[`CAPABILITIES.md`](CAPABILITIES.md) when the question is *what\nthe printed tables actually mean* and *what is not in this\ntool's scope*. If the user has not installed DOCA yet, route to\n[`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md) first; if the user\nneeds MFT (`resourcedump` on `PATH` with the privilege documented\nfor the installed release), `doca-setup` + `doca-public-knowledge-map`\ncover that. If the user is holding pre-2.5 docs that mention\n\"Comm Channel\", route to\n[`doca-comch CAPABILITIES.md ## Version compatibility`](..\u002F..\u002Flibs\u002Fdoca-comch\u002FCAPABILITIES.md#version-compatibility)\nfor the rename rule. If the user wants to *change* channel\nstate, route to the program-side\nreconnect lifecycle in [`doca-comch`](..\u002F..\u002Flibs\u002Fdoca-comch\u002FSKILL.md)\nor to BlueField mode \u002F driver reload in\n[`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md) +\n[`doca-hardware-safety`](..\u002F..\u002Fdoca-hardware-safety\u002FSKILL.md) — **not**\nto this tool.\n\n## Example questions this skill answers well\n\nThe CLASSES of admin-tool questions this skill is built to answer,\neach with one worked example. The class is the load-bearing piece;\nthe worked example is one instance.\n\n- **\"Which comch servers and connections are currently visible?\"** —\n  worked example: *\"print every server and connection row visible\n  on this side\"*. Answered by the scan-and-print surface in\n  [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)\n  + the single invocation in\n  [`TASKS.md ## run`](TASKS.md#run).\n- **\"What does the tool report for this server or connection?\"** —\n  locate the matching row in the SERVERS or CONNECTIONS table;\n  there is no second per-channel query. Answered by\n  [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)\n  + [`TASKS.md ## run`](TASKS.md#run).\n- **\"How do I know the admin tool's view matches what my Comch\n  program sees?\"** — worked example: *\"the program reports\n  CONNECTED but the admin tool lists zero channels\"*. Answered by\n  the cross-checking pattern in\n  [`TASKS.md ## test`](TASKS.md#test) and the representor-binding\n  layer in\n  [`CAPABILITIES.md ## Error taxonomy`](CAPABILITIES.md#error-taxonomy).\n- **\"Is this admin tool on my installed DOCA version, and does it\n  match the comch library version?\"** — worked example: *\"is the\n  tool available on DOCA 2.4\"*. Answered by the overlay in\n  [`CAPABILITIES.md ## Version compatibility`](CAPABILITIES.md#version-compatibility),\n  which redirects to the canonical\n  [`doca-version`](..\u002F..\u002Fdoca-version\u002FSKILL.md) rules and adds the\n  Comm Channel Admin Tool specifics.\n- **\"The tool prints nothing — is the install broken or is there\n  genuinely no channel?\"** — worked example: *\"`list` returned an\n  empty result on a host with a known-good Comch client\"*.\n  Answered by the empty-output interpretation rules in\n  [`TASKS.md ## debug`](TASKS.md#debug) +\n  [`CAPABILITIES.md ## Error taxonomy`](CAPABILITIES.md#error-taxonomy).\n\n## Audience\n\nThis skill serves **external operators and AI agents who need to\ninventory a host-DPU comch channel from the outside**\n— after the [`doca-comch`](..\u002F..\u002Flibs\u002Fdoca-comch\u002FSKILL.md) library\nhas been used to create the channel from a program. Concretely:\n\n- A platform operator who runs a Comch-using service on BlueField\n  and needs to confirm the channel is healthy before declaring the\n  service ready.\n- A developer of a Comch consumer who sees `DOCA_ERROR_AGAIN` or a\n  silent stall on the program side and wants to read the channel's\n  state from outside the program rather than guessing.\n- An AI agent capturing the external server\u002Fconnection rows before\n  recommending a program-side code or lifecycle change.\n\nIt is **not** for users debugging the admin tool itself, **not** a\nsubstitute for the live public DOCA Comm Channel Admin Tool guide,\nand **not** the right place for users learning the comch API —\nthat audience belongs in\n[`doca-comch`](..\u002F..\u002Flibs\u002Fdoca-comch\u002FSKILL.md).\n\nThe tool is shipped as a CLI binary under\n`\u002Fopt\u002Fmellanox\u002Fdoca\u002Ftools\u002F`, not a library you link against. The\nskill uses the same `kind: tool` three-file shape as the rest of\nthe bundle so the agent's task-verb contract\n(`configure \u002F build \u002F modify \u002F run \u002F test \u002F debug`) is uniform\nacross libraries, services, and tools.\n\n## When to load this skill\n\nLoad this skill when the user is — or the agent needs to — invoke\nthe DOCA Comm Channel Admin Tool on a real host or BlueField Arm\nwith DOCA installed (or inside the public NGC DOCA container with\nthe right device passthrough). Concretely:\n\n- Listing currently active comch channels on a host or DPU.\n- Reading the row for one named server or connection from the\n  complete zero-argument scan.\n- Cross-checking the admin tool's view against the program-side\n  connection callback state when the two appear to disagree.\n- Capturing a side-effect-free channel snapshot as prerequisite\n  evidence for a later debug session that crosses program \u002F\n  channel \u002F driver layers.\n\nDo **not** load this skill for general DOCA orientation, the comch\nprogramming API, library install, or comch protocol design. For\nthose, route to\n[`doca-public-knowledge-map`](..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md),\n[`doca-comch`](..\u002F..\u002Flibs\u002Fdoca-comch\u002FSKILL.md), or\n[`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md).\n\n## What this skill provides\n\nThis is a **thin loader**. Substantive material lives in two\ncompanion files:\n\n- `CAPABILITIES.md` — what the Comm Channel Admin Tool reports:\n  the two read-only tables, the version-availability overlay\n  that redirects to [`doca-version`](..\u002F..\u002Fdoca-version\u002FSKILL.md),\n  the layered error taxonomy (tool-not-installed \u002F device-binding\n  \u002F channel-discovery \u002F channel-state-stuck \u002F permission \u002F\n  version \u002F cross-cutting), the tool's role as an observability\n  primitive for [`doca-comch`](..\u002F..\u002Flibs\u002Fdoca-comch\u002FSKILL.md)\n  debug sessions, and the read-only safety policy.\n- `TASKS.md` — step-by-step workflows for the in-scope task verbs:\n  `configure` (route to install), `build` (route to install),\n  `modify` (refuse), `run` (one scan-and-print), `test`\n  (cross-check the printed rows), `debug` (the layered\n  diagnosis ladder), plus a `Deferred task verbs` block and a\n  `Command appendix` that honors the bundle's\n  [`doca-structured-tools-contract`](..\u002F..\u002Fdoca-structured-tools-contract\u002FSKILL.md)\n  preamble.\n\nThe skill assumes a host or BlueField where DOCA is already\ninstalled (or the public NGC DOCA container is running with the\nright device passthrough) and the operator has whatever privileges\nthe public DOCA Comm Channel Admin Tool guide requires.\n\n## What this skill deliberately does not ship\n\nThis skill is **agent guidance**, not a samples or scripts bundle.\nTo keep the boundary clean, it deliberately does not contain — and\npull requests should not add:\n\n- **Verbatim flag inventories, subcommand names, or output column\n  names.** The public DOCA Comm Channel Admin Tool guide on\n  `docs.nvidia.com` and the installed `--help` on the user's\n  version are the joint source of truth; copying them here pins\n  the skill to one release and silently rots when the tool\n  evolves. The skill routes the agent at those sources instead.\n- **Pre-baked example output.** Output is install-, version-, and\n  channel-state-specific. A captured example will mislead an\n  operator on a different platform \u002F state.\n- **Wrappers, parsers, or scripts** in any language that consume\n  the admin tool's output. The output format is documented; users\n  who want to script against it should read the live guide and\n  write the parser against their installed version.\n- **A `samples\u002F` or `reference\u002F` subtree.** This is a thin loader\n  for a documented CLI; substantive material lives on the public\n  page and in `--help`.\n\n## Loading order\n\n1. Read this `SKILL.md` first to confirm the user's question is in\n   scope (the user wants to inventory a comch\n   channel from the outside, not learn the comch API).\n2. **For what the tool reports, version availability, the layered error surface,\n   observability, and safety posture, see\n   [CAPABILITIES.md](CAPABILITIES.md).**\n3. **For the single invocation and cross-check\n   workflow — `configure`, `build`, `modify`, `run`, `test`,\n   `debug`, plus the `Command appendix` — see\n   [TASKS.md](TASKS.md).**\n\n## Related skills\n\n- [`doca-comch`](..\u002F..\u002Flibs\u002Fdoca-comch\u002FSKILL.md) — the library\n  whose channels this tool inventories. Pair them in every\n  triage session: the program-side connection callback and the\n  admin tool's channel state are the two halves of the same\n  picture.\n- [`doca-public-knowledge-map`](..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md)\n  — routing to the public DOCA Comm Channel Admin Tool guide and\n  the rest of the public DOCA documentation set.\n- [`doca-version`](..\u002F..\u002Fdoca-version\u002FSKILL.md) — canonical DOCA\n  version-handling rules. The `## Version compatibility` section\n  in [`CAPABILITIES.md`](CAPABILITIES.md) is a concise overlay\n  that redirects here for the body.\n- [`doca-structured-tools-contract`](..\u002F..\u002Fdoca-structured-tools-contract\u002FSKILL.md)\n  — the bundle's detect → prefer → fall back → report contract for\n  structured helper tools. The Command appendix in\n  [`TASKS.md`](TASKS.md) honors this contract.\n- [`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md) — env preparation,\n  install verification, representor visibility checks, and the\n  *I have no install yet* path with the public NGC DOCA\n  container. This skill assumes its preconditions are satisfied.\n- [`doca-debug`](..\u002F..\u002Fdoca-debug\u002FSKILL.md) — the cross-cutting\n  debug ladder. The Comm Channel Admin Tool slots in at the\n  *runtime* layer as the read-only inventory surface before any\n  code change is recommended.\n",{"data":32,"body":36},{"license":23,"name":4,"description":6,"metadata":33,"compatibility":35},{"kind":34},"tool","Requires DOCA SDK installed at \u002Fopt\u002Fmellanox\u002Fdoca on Linux (Ubuntu 22.04\u002F24.04 or RHEL\u002FSLES) with the Comm Channel tooling subpackage so the CLI is present under \u002Fopt\u002Fmellanox\u002Fdoca\u002Ftools\u002F. Runs from either the x86\u002FArm host or the BlueField Arm side; a live host↔DPU comch channel created via the doca-comch library is needed for non-empty tables.\n",{"type":37,"children":38},"root",[39,48,89,385,392,397,603,609,631,657,689,718,724,729,752,792,798,810,929,934,940,952,1032,1038,1125,1131],{"type":40,"tag":41,"props":42,"children":44},"element","h1",{"id":43},"doca-comm-channel-admin-tool",[45],{"type":46,"value":47},"text","DOCA Comm Channel Admin Tool",{"type":40,"tag":49,"props":50,"children":51},"blockquote",{},[52],{"type":40,"tag":53,"props":54,"children":55},"p",{},[56,62,64,71,73,79,81,87],{"type":40,"tag":57,"props":58,"children":59},"strong",{},[60],{"type":46,"value":61},"Actual binary contract.",{"type":46,"value":63}," ",{"type":40,"tag":65,"props":66,"children":68},"code",{"className":67},[],[69],{"type":46,"value":70},"doca_comm_channel_admin",{"type":46,"value":72}," is one\nzero-application-argument, read-only scan-and-print operation.\nIt scans every comch-capable ",{"type":40,"tag":65,"props":74,"children":76},{"className":75},[],[77],{"type":46,"value":78},"doca_dev",{"type":46,"value":80}," on the current side via\n",{"type":40,"tag":65,"props":82,"children":84},{"className":83},[],[85],{"type":46,"value":86},"resourcedump",{"type":46,"value":88}," (MFT) and prints SERVERS and CONNECTIONS tables.\nIt has no list, inspect, device-scope, drain, restart, or other\napplication operation. This skill does not retain conceptual\nworkflows under invented command names.",{"type":40,"tag":53,"props":90,"children":91},{},[92,97,99,104,106,117,119,124,126,131,133,139,141,147,148,154,156,162,163,169,171,176,178,183,185,190,192,198,200,206,208,214,216,222,224,233,235,245,247,257,259,268,270,276,278,283,285,295,297,302,304,310,312,317,319,325,327,337,339,344,346,354,356,364,366,376,378,383],{"type":40,"tag":57,"props":93,"children":94},{},[95],{"type":46,"value":96},"Where to start:",{"type":46,"value":98}," This is a tool skill for invoking the DOCA Comm\nChannel Admin Tool — the ",{"type":40,"tag":57,"props":100,"children":101},{},[102],{"type":46,"value":103},"read-only inventory",{"type":46,"value":105}," CLI counterpart\nto the ",{"type":40,"tag":107,"props":108,"children":110},"a",{"href":109},"..\u002F..\u002Flibs\u002Fdoca-comch\u002FSKILL.md",[111],{"type":40,"tag":65,"props":112,"children":114},{"className":113},[],[115],{"type":46,"value":116},"doca-comch",{"type":46,"value":118}," library. The\nshipped ",{"type":40,"tag":65,"props":120,"children":122},{"className":121},[],[123],{"type":46,"value":70},{"type":46,"value":125}," binary takes ",{"type":40,"tag":57,"props":127,"children":128},{},[129],{"type":46,"value":130},"no arguments\nbeyond ARGP defaults",{"type":46,"value":132}," (",{"type":40,"tag":65,"props":134,"children":136},{"className":135},[],[137],{"type":46,"value":138},"--help",{"type":46,"value":140},", ",{"type":40,"tag":65,"props":142,"children":144},{"className":143},[],[145],{"type":46,"value":146},"--version",{"type":46,"value":140},{"type":40,"tag":65,"props":149,"children":151},{"className":150},[],[152],{"type":46,"value":153},"--log-level",{"type":46,"value":155},",\n",{"type":40,"tag":65,"props":157,"children":159},{"className":158},[],[160],{"type":46,"value":161},"--sdk-log-level",{"type":46,"value":140},{"type":40,"tag":65,"props":164,"children":166},{"className":165},[],[167],{"type":46,"value":168},"--json",{"type":46,"value":170},") and performs ",{"type":40,"tag":57,"props":172,"children":173},{},[174],{"type":46,"value":175},"one inventory pass",{"type":46,"value":177},"\nper invocation: it walks every ",{"type":40,"tag":65,"props":179,"children":181},{"className":180},[],[182],{"type":46,"value":78},{"type":46,"value":184}," on this side, filters\nto comch-capable devices, shells out to ",{"type":40,"tag":65,"props":186,"children":188},{"className":187},[],[189],{"type":46,"value":86},{"type":46,"value":191}," (MFT) on\neach, and prints two ASCII tables (SERVERS and CONNECTIONS).\nThere is no ",{"type":40,"tag":65,"props":193,"children":195},{"className":194},[],[196],{"type":46,"value":197},"list",{"type":46,"value":199}," subcommand, no ",{"type":40,"tag":65,"props":201,"children":203},{"className":202},[],[204],{"type":46,"value":205},"inspect",{"type":46,"value":207}," subcommand, no\n",{"type":40,"tag":65,"props":209,"children":211},{"className":210},[],[212],{"type":46,"value":213},"drain",{"type":46,"value":215}," flag, and no ",{"type":40,"tag":65,"props":217,"children":219},{"className":218},[],[220],{"type":46,"value":221},"restart",{"type":46,"value":223}," flag — those are not part of the\ntool's surface. Open ",{"type":40,"tag":107,"props":225,"children":227},{"href":226},"TASKS.md",[228],{"type":40,"tag":65,"props":229,"children":231},{"className":230},[],[232],{"type":46,"value":226},{"type":46,"value":234}," and start at\n",{"type":40,"tag":107,"props":236,"children":238},{"href":237},"TASKS.md#run",[239],{"type":40,"tag":65,"props":240,"children":242},{"className":241},[],[243],{"type":46,"value":244},"## run",{"type":46,"value":246}," for the single-shot invocation, or\n",{"type":40,"tag":107,"props":248,"children":250},{"href":249},"TASKS.md#debug",[251],{"type":40,"tag":65,"props":252,"children":254},{"className":253},[],[255],{"type":46,"value":256},"## debug",{"type":46,"value":258}," when the user reports the tool sees\na different channel set than the program. Open\n",{"type":40,"tag":107,"props":260,"children":262},{"href":261},"CAPABILITIES.md",[263],{"type":40,"tag":65,"props":264,"children":266},{"className":265},[],[267],{"type":46,"value":261},{"type":46,"value":269}," when the question is ",{"type":40,"tag":271,"props":272,"children":273},"em",{},[274],{"type":46,"value":275},"what\nthe printed tables actually mean",{"type":46,"value":277}," and ",{"type":40,"tag":271,"props":279,"children":280},{},[281],{"type":46,"value":282},"what is not in this\ntool's scope",{"type":46,"value":284},". If the user has not installed DOCA yet, route to\n",{"type":40,"tag":107,"props":286,"children":288},{"href":287},"..\u002F..\u002Fdoca-setup\u002FSKILL.md",[289],{"type":40,"tag":65,"props":290,"children":292},{"className":291},[],[293],{"type":46,"value":294},"doca-setup",{"type":46,"value":296}," first; if the user\nneeds MFT (",{"type":40,"tag":65,"props":298,"children":300},{"className":299},[],[301],{"type":46,"value":86},{"type":46,"value":303}," on ",{"type":40,"tag":65,"props":305,"children":307},{"className":306},[],[308],{"type":46,"value":309},"PATH",{"type":46,"value":311}," with the privilege documented\nfor the installed release), ",{"type":40,"tag":65,"props":313,"children":315},{"className":314},[],[316],{"type":46,"value":294},{"type":46,"value":318}," + ",{"type":40,"tag":65,"props":320,"children":322},{"className":321},[],[323],{"type":46,"value":324},"doca-public-knowledge-map",{"type":46,"value":326},"\ncover that. If the user is holding pre-2.5 docs that mention\n\"Comm Channel\", route to\n",{"type":40,"tag":107,"props":328,"children":330},{"href":329},"..\u002F..\u002Flibs\u002Fdoca-comch\u002FCAPABILITIES.md#version-compatibility",[331],{"type":40,"tag":65,"props":332,"children":334},{"className":333},[],[335],{"type":46,"value":336},"doca-comch CAPABILITIES.md ## Version compatibility",{"type":46,"value":338},"\nfor the rename rule. If the user wants to ",{"type":40,"tag":271,"props":340,"children":341},{},[342],{"type":46,"value":343},"change",{"type":46,"value":345}," channel\nstate, route to the program-side\nreconnect lifecycle in ",{"type":40,"tag":107,"props":347,"children":348},{"href":109},[349],{"type":40,"tag":65,"props":350,"children":352},{"className":351},[],[353],{"type":46,"value":116},{"type":46,"value":355},"\nor to BlueField mode \u002F driver reload in\n",{"type":40,"tag":107,"props":357,"children":358},{"href":287},[359],{"type":40,"tag":65,"props":360,"children":362},{"className":361},[],[363],{"type":46,"value":294},{"type":46,"value":365}," +\n",{"type":40,"tag":107,"props":367,"children":369},{"href":368},"..\u002F..\u002Fdoca-hardware-safety\u002FSKILL.md",[370],{"type":40,"tag":65,"props":371,"children":373},{"className":372},[],[374],{"type":46,"value":375},"doca-hardware-safety",{"type":46,"value":377}," — ",{"type":40,"tag":57,"props":379,"children":380},{},[381],{"type":46,"value":382},"not",{"type":46,"value":384},"\nto this tool.",{"type":40,"tag":386,"props":387,"children":389},"h2",{"id":388},"example-questions-this-skill-answers-well",[390],{"type":46,"value":391},"Example questions this skill answers well",{"type":40,"tag":53,"props":393,"children":394},{},[395],{"type":46,"value":396},"The CLASSES of admin-tool questions this skill is built to answer,\neach with one worked example. The class is the load-bearing piece;\nthe worked example is one instance.",{"type":40,"tag":398,"props":399,"children":400},"ul",{},[401,448,481,521,561],{"type":40,"tag":402,"props":403,"children":404},"li",{},[405,410,412,417,419,429],{"type":40,"tag":57,"props":406,"children":407},{},[408],{"type":46,"value":409},"\"Which comch servers and connections are currently visible?\"",{"type":46,"value":411}," —\nworked example: ",{"type":40,"tag":271,"props":413,"children":414},{},[415],{"type":46,"value":416},"\"print every server and connection row visible\non this side\"",{"type":46,"value":418},". Answered by the scan-and-print surface in\n",{"type":40,"tag":107,"props":420,"children":422},{"href":421},"CAPABILITIES.md#capabilities-and-modes",[423],{"type":40,"tag":65,"props":424,"children":426},{"className":425},[],[427],{"type":46,"value":428},"CAPABILITIES.md ## Capabilities and modes",{"type":40,"tag":398,"props":430,"children":431},{},[432],{"type":40,"tag":402,"props":433,"children":434},{},[435,437,446],{"type":46,"value":436},"the single invocation in\n",{"type":40,"tag":107,"props":438,"children":439},{"href":237},[440],{"type":40,"tag":65,"props":441,"children":443},{"className":442},[],[444],{"type":46,"value":445},"TASKS.md ## run",{"type":46,"value":447},".",{"type":40,"tag":402,"props":449,"children":450},{},[451,456,458,466],{"type":40,"tag":57,"props":452,"children":453},{},[454],{"type":46,"value":455},"\"What does the tool report for this server or connection?\"",{"type":46,"value":457}," —\nlocate the matching row in the SERVERS or CONNECTIONS table;\nthere is no second per-channel query. Answered by\n",{"type":40,"tag":107,"props":459,"children":460},{"href":421},[461],{"type":40,"tag":65,"props":462,"children":464},{"className":463},[],[465],{"type":46,"value":428},{"type":40,"tag":398,"props":467,"children":468},{},[469],{"type":40,"tag":402,"props":470,"children":471},{},[472,480],{"type":40,"tag":107,"props":473,"children":474},{"href":237},[475],{"type":40,"tag":65,"props":476,"children":478},{"className":477},[],[479],{"type":46,"value":445},{"type":46,"value":447},{"type":40,"tag":402,"props":482,"children":483},{},[484,489,491,496,498,508,510,520],{"type":40,"tag":57,"props":485,"children":486},{},[487],{"type":46,"value":488},"\"How do I know the admin tool's view matches what my Comch\nprogram sees?\"",{"type":46,"value":490}," — worked example: ",{"type":40,"tag":271,"props":492,"children":493},{},[494],{"type":46,"value":495},"\"the program reports\nCONNECTED but the admin tool lists zero channels\"",{"type":46,"value":497},". Answered by\nthe cross-checking pattern in\n",{"type":40,"tag":107,"props":499,"children":501},{"href":500},"TASKS.md#test",[502],{"type":40,"tag":65,"props":503,"children":505},{"className":504},[],[506],{"type":46,"value":507},"TASKS.md ## test",{"type":46,"value":509}," and the representor-binding\nlayer in\n",{"type":40,"tag":107,"props":511,"children":513},{"href":512},"CAPABILITIES.md#error-taxonomy",[514],{"type":40,"tag":65,"props":515,"children":517},{"className":516},[],[518],{"type":46,"value":519},"CAPABILITIES.md ## Error taxonomy",{"type":46,"value":447},{"type":40,"tag":402,"props":522,"children":523},{},[524,529,530,535,537,547,549,559],{"type":40,"tag":57,"props":525,"children":526},{},[527],{"type":46,"value":528},"\"Is this admin tool on my installed DOCA version, and does it\nmatch the comch library version?\"",{"type":46,"value":490},{"type":40,"tag":271,"props":531,"children":532},{},[533],{"type":46,"value":534},"\"is the\ntool available on DOCA 2.4\"",{"type":46,"value":536},". Answered by the overlay in\n",{"type":40,"tag":107,"props":538,"children":540},{"href":539},"CAPABILITIES.md#version-compatibility",[541],{"type":40,"tag":65,"props":542,"children":544},{"className":543},[],[545],{"type":46,"value":546},"CAPABILITIES.md ## Version compatibility",{"type":46,"value":548},",\nwhich redirects to the canonical\n",{"type":40,"tag":107,"props":550,"children":552},{"href":551},"..\u002F..\u002Fdoca-version\u002FSKILL.md",[553],{"type":40,"tag":65,"props":554,"children":556},{"className":555},[],[557],{"type":46,"value":558},"doca-version",{"type":46,"value":560}," rules and adds the\nComm Channel Admin Tool specifics.",{"type":40,"tag":402,"props":562,"children":563},{},[564,569,570,582,584,593,594,602],{"type":40,"tag":57,"props":565,"children":566},{},[567],{"type":46,"value":568},"\"The tool prints nothing — is the install broken or is there\ngenuinely no channel?\"",{"type":46,"value":490},{"type":40,"tag":271,"props":571,"children":572},{},[573,575,580],{"type":46,"value":574},"\"",{"type":40,"tag":65,"props":576,"children":578},{"className":577},[],[579],{"type":46,"value":197},{"type":46,"value":581}," returned an\nempty result on a host with a known-good Comch client\"",{"type":46,"value":583},".\nAnswered by the empty-output interpretation rules in\n",{"type":40,"tag":107,"props":585,"children":586},{"href":249},[587],{"type":40,"tag":65,"props":588,"children":590},{"className":589},[],[591],{"type":46,"value":592},"TASKS.md ## debug",{"type":46,"value":365},{"type":40,"tag":107,"props":595,"children":596},{"href":512},[597],{"type":40,"tag":65,"props":598,"children":600},{"className":599},[],[601],{"type":46,"value":519},{"type":46,"value":447},{"type":40,"tag":386,"props":604,"children":606},{"id":605},"audience",[607],{"type":46,"value":608},"Audience",{"type":40,"tag":53,"props":610,"children":611},{},[612,614,619,621,629],{"type":46,"value":613},"This skill serves ",{"type":40,"tag":57,"props":615,"children":616},{},[617],{"type":46,"value":618},"external operators and AI agents who need to\ninventory a host-DPU comch channel from the outside",{"type":46,"value":620},"\n— after the ",{"type":40,"tag":107,"props":622,"children":623},{"href":109},[624],{"type":40,"tag":65,"props":625,"children":627},{"className":626},[],[628],{"type":46,"value":116},{"type":46,"value":630}," library\nhas been used to create the channel from a program. Concretely:",{"type":40,"tag":398,"props":632,"children":633},{},[634,639,652],{"type":40,"tag":402,"props":635,"children":636},{},[637],{"type":46,"value":638},"A platform operator who runs a Comch-using service on BlueField\nand needs to confirm the channel is healthy before declaring the\nservice ready.",{"type":40,"tag":402,"props":640,"children":641},{},[642,644,650],{"type":46,"value":643},"A developer of a Comch consumer who sees ",{"type":40,"tag":65,"props":645,"children":647},{"className":646},[],[648],{"type":46,"value":649},"DOCA_ERROR_AGAIN",{"type":46,"value":651}," or a\nsilent stall on the program side and wants to read the channel's\nstate from outside the program rather than guessing.",{"type":40,"tag":402,"props":653,"children":654},{},[655],{"type":46,"value":656},"An AI agent capturing the external server\u002Fconnection rows before\nrecommending a program-side code or lifecycle change.",{"type":40,"tag":53,"props":658,"children":659},{},[660,662,666,668,672,674,678,680,688],{"type":46,"value":661},"It is ",{"type":40,"tag":57,"props":663,"children":664},{},[665],{"type":46,"value":382},{"type":46,"value":667}," for users debugging the admin tool itself, ",{"type":40,"tag":57,"props":669,"children":670},{},[671],{"type":46,"value":382},{"type":46,"value":673}," a\nsubstitute for the live public DOCA Comm Channel Admin Tool guide,\nand ",{"type":40,"tag":57,"props":675,"children":676},{},[677],{"type":46,"value":382},{"type":46,"value":679}," the right place for users learning the comch API —\nthat audience belongs in\n",{"type":40,"tag":107,"props":681,"children":682},{"href":109},[683],{"type":40,"tag":65,"props":684,"children":686},{"className":685},[],[687],{"type":46,"value":116},{"type":46,"value":447},{"type":40,"tag":53,"props":690,"children":691},{},[692,694,700,702,708,710,716],{"type":46,"value":693},"The tool is shipped as a CLI binary under\n",{"type":40,"tag":65,"props":695,"children":697},{"className":696},[],[698],{"type":46,"value":699},"\u002Fopt\u002Fmellanox\u002Fdoca\u002Ftools\u002F",{"type":46,"value":701},", not a library you link against. The\nskill uses the same ",{"type":40,"tag":65,"props":703,"children":705},{"className":704},[],[706],{"type":46,"value":707},"kind: tool",{"type":46,"value":709}," three-file shape as the rest of\nthe bundle so the agent's task-verb contract\n(",{"type":40,"tag":65,"props":711,"children":713},{"className":712},[],[714],{"type":46,"value":715},"configure \u002F build \u002F modify \u002F run \u002F test \u002F debug",{"type":46,"value":717},") is uniform\nacross libraries, services, and tools.",{"type":40,"tag":386,"props":719,"children":721},{"id":720},"when-to-load-this-skill",[722],{"type":46,"value":723},"When to load this skill",{"type":40,"tag":53,"props":725,"children":726},{},[727],{"type":46,"value":728},"Load this skill when the user is — or the agent needs to — invoke\nthe DOCA Comm Channel Admin Tool on a real host or BlueField Arm\nwith DOCA installed (or inside the public NGC DOCA container with\nthe right device passthrough). Concretely:",{"type":40,"tag":398,"props":730,"children":731},{},[732,737,742,747],{"type":40,"tag":402,"props":733,"children":734},{},[735],{"type":46,"value":736},"Listing currently active comch channels on a host or DPU.",{"type":40,"tag":402,"props":738,"children":739},{},[740],{"type":46,"value":741},"Reading the row for one named server or connection from the\ncomplete zero-argument scan.",{"type":40,"tag":402,"props":743,"children":744},{},[745],{"type":46,"value":746},"Cross-checking the admin tool's view against the program-side\nconnection callback state when the two appear to disagree.",{"type":40,"tag":402,"props":748,"children":749},{},[750],{"type":46,"value":751},"Capturing a side-effect-free channel snapshot as prerequisite\nevidence for a later debug session that crosses program \u002F\nchannel \u002F driver layers.",{"type":40,"tag":53,"props":753,"children":754},{},[755,757,761,763,772,773,781,783,791],{"type":46,"value":756},"Do ",{"type":40,"tag":57,"props":758,"children":759},{},[760],{"type":46,"value":382},{"type":46,"value":762}," load this skill for general DOCA orientation, the comch\nprogramming API, library install, or comch protocol design. For\nthose, route to\n",{"type":40,"tag":107,"props":764,"children":766},{"href":765},"..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md",[767],{"type":40,"tag":65,"props":768,"children":770},{"className":769},[],[771],{"type":46,"value":324},{"type":46,"value":155},{"type":40,"tag":107,"props":774,"children":775},{"href":109},[776],{"type":40,"tag":65,"props":777,"children":779},{"className":778},[],[780],{"type":46,"value":116},{"type":46,"value":782},", or\n",{"type":40,"tag":107,"props":784,"children":785},{"href":287},[786],{"type":40,"tag":65,"props":787,"children":789},{"className":788},[],[790],{"type":46,"value":294},{"type":46,"value":447},{"type":40,"tag":386,"props":793,"children":795},{"id":794},"what-this-skill-provides",[796],{"type":46,"value":797},"What this skill provides",{"type":40,"tag":53,"props":799,"children":800},{},[801,803,808],{"type":46,"value":802},"This is a ",{"type":40,"tag":57,"props":804,"children":805},{},[806],{"type":46,"value":807},"thin loader",{"type":46,"value":809},". Substantive material lives in two\ncompanion files:",{"type":40,"tag":398,"props":811,"children":812},{},[813,843],{"type":40,"tag":402,"props":814,"children":815},{},[816,821,823,831,833,841],{"type":40,"tag":65,"props":817,"children":819},{"className":818},[],[820],{"type":46,"value":261},{"type":46,"value":822}," — what the Comm Channel Admin Tool reports:\nthe two read-only tables, the version-availability overlay\nthat redirects to ",{"type":40,"tag":107,"props":824,"children":825},{"href":551},[826],{"type":40,"tag":65,"props":827,"children":829},{"className":828},[],[830],{"type":46,"value":558},{"type":46,"value":832},",\nthe layered error taxonomy (tool-not-installed \u002F device-binding\n\u002F channel-discovery \u002F channel-state-stuck \u002F permission \u002F\nversion \u002F cross-cutting), the tool's role as an observability\nprimitive for ",{"type":40,"tag":107,"props":834,"children":835},{"href":109},[836],{"type":40,"tag":65,"props":837,"children":839},{"className":838},[],[840],{"type":46,"value":116},{"type":46,"value":842},"\ndebug sessions, and the read-only safety policy.",{"type":40,"tag":402,"props":844,"children":845},{},[846,851,853,859,861,867,869,875,877,883,885,891,893,899,901,907,909,915,917,927],{"type":40,"tag":65,"props":847,"children":849},{"className":848},[],[850],{"type":46,"value":226},{"type":46,"value":852}," — step-by-step workflows for the in-scope task verbs:\n",{"type":40,"tag":65,"props":854,"children":856},{"className":855},[],[857],{"type":46,"value":858},"configure",{"type":46,"value":860}," (route to install), ",{"type":40,"tag":65,"props":862,"children":864},{"className":863},[],[865],{"type":46,"value":866},"build",{"type":46,"value":868}," (route to install),\n",{"type":40,"tag":65,"props":870,"children":872},{"className":871},[],[873],{"type":46,"value":874},"modify",{"type":46,"value":876}," (refuse), ",{"type":40,"tag":65,"props":878,"children":880},{"className":879},[],[881],{"type":46,"value":882},"run",{"type":46,"value":884}," (one scan-and-print), ",{"type":40,"tag":65,"props":886,"children":888},{"className":887},[],[889],{"type":46,"value":890},"test",{"type":46,"value":892},"\n(cross-check the printed rows), ",{"type":40,"tag":65,"props":894,"children":896},{"className":895},[],[897],{"type":46,"value":898},"debug",{"type":46,"value":900}," (the layered\ndiagnosis ladder), plus a ",{"type":40,"tag":65,"props":902,"children":904},{"className":903},[],[905],{"type":46,"value":906},"Deferred task verbs",{"type":46,"value":908}," block and a\n",{"type":40,"tag":65,"props":910,"children":912},{"className":911},[],[913],{"type":46,"value":914},"Command appendix",{"type":46,"value":916}," that honors the bundle's\n",{"type":40,"tag":107,"props":918,"children":920},{"href":919},"..\u002F..\u002Fdoca-structured-tools-contract\u002FSKILL.md",[921],{"type":40,"tag":65,"props":922,"children":924},{"className":923},[],[925],{"type":46,"value":926},"doca-structured-tools-contract",{"type":46,"value":928},"\npreamble.",{"type":40,"tag":53,"props":930,"children":931},{},[932],{"type":46,"value":933},"The skill assumes a host or BlueField where DOCA is already\ninstalled (or the public NGC DOCA container is running with the\nright device passthrough) and the operator has whatever privileges\nthe public DOCA Comm Channel Admin Tool guide requires.",{"type":40,"tag":386,"props":935,"children":937},{"id":936},"what-this-skill-deliberately-does-not-ship",[938],{"type":46,"value":939},"What this skill deliberately does not ship",{"type":40,"tag":53,"props":941,"children":942},{},[943,945,950],{"type":46,"value":944},"This skill is ",{"type":40,"tag":57,"props":946,"children":947},{},[948],{"type":46,"value":949},"agent guidance",{"type":46,"value":951},", not a samples or scripts bundle.\nTo keep the boundary clean, it deliberately does not contain — and\npull requests should not add:",{"type":40,"tag":398,"props":953,"children":954},{},[955,980,990,1000],{"type":40,"tag":402,"props":956,"children":957},{},[958,963,965,971,973,978],{"type":40,"tag":57,"props":959,"children":960},{},[961],{"type":46,"value":962},"Verbatim flag inventories, subcommand names, or output column\nnames.",{"type":46,"value":964}," The public DOCA Comm Channel Admin Tool guide on\n",{"type":40,"tag":65,"props":966,"children":968},{"className":967},[],[969],{"type":46,"value":970},"docs.nvidia.com",{"type":46,"value":972}," and the installed ",{"type":40,"tag":65,"props":974,"children":976},{"className":975},[],[977],{"type":46,"value":138},{"type":46,"value":979}," on the user's\nversion are the joint source of truth; copying them here pins\nthe skill to one release and silently rots when the tool\nevolves. The skill routes the agent at those sources instead.",{"type":40,"tag":402,"props":981,"children":982},{},[983,988],{"type":40,"tag":57,"props":984,"children":985},{},[986],{"type":46,"value":987},"Pre-baked example output.",{"type":46,"value":989}," Output is install-, version-, and\nchannel-state-specific. A captured example will mislead an\noperator on a different platform \u002F state.",{"type":40,"tag":402,"props":991,"children":992},{},[993,998],{"type":40,"tag":57,"props":994,"children":995},{},[996],{"type":46,"value":997},"Wrappers, parsers, or scripts",{"type":46,"value":999}," in any language that consume\nthe admin tool's output. The output format is documented; users\nwho want to script against it should read the live guide and\nwrite the parser against their installed version.",{"type":40,"tag":402,"props":1001,"children":1002},{},[1003,1024,1026,1031],{"type":40,"tag":57,"props":1004,"children":1005},{},[1006,1008,1014,1016,1022],{"type":46,"value":1007},"A ",{"type":40,"tag":65,"props":1009,"children":1011},{"className":1010},[],[1012],{"type":46,"value":1013},"samples\u002F",{"type":46,"value":1015}," or ",{"type":40,"tag":65,"props":1017,"children":1019},{"className":1018},[],[1020],{"type":46,"value":1021},"reference\u002F",{"type":46,"value":1023}," subtree.",{"type":46,"value":1025}," This is a thin loader\nfor a documented CLI; substantive material lives on the public\npage and in ",{"type":40,"tag":65,"props":1027,"children":1029},{"className":1028},[],[1030],{"type":46,"value":138},{"type":46,"value":447},{"type":40,"tag":386,"props":1033,"children":1035},{"id":1034},"loading-order",[1036],{"type":46,"value":1037},"Loading order",{"type":40,"tag":1039,"props":1040,"children":1041},"ol",{},[1042,1055,1068],{"type":40,"tag":402,"props":1043,"children":1044},{},[1045,1047,1053],{"type":46,"value":1046},"Read this ",{"type":40,"tag":65,"props":1048,"children":1050},{"className":1049},[],[1051],{"type":46,"value":1052},"SKILL.md",{"type":46,"value":1054}," first to confirm the user's question is in\nscope (the user wants to inventory a comch\nchannel from the outside, not learn the comch API).",{"type":40,"tag":402,"props":1056,"children":1057},{},[1058],{"type":40,"tag":57,"props":1059,"children":1060},{},[1061,1063,1067],{"type":46,"value":1062},"For what the tool reports, version availability, the layered error surface,\nobservability, and safety posture, see\n",{"type":40,"tag":107,"props":1064,"children":1065},{"href":261},[1066],{"type":46,"value":261},{"type":46,"value":447},{"type":40,"tag":402,"props":1069,"children":1070},{},[1071],{"type":40,"tag":57,"props":1072,"children":1073},{},[1074,1076,1081,1082,1087,1088,1093,1094,1099,1100,1105,1106,1111,1113,1118,1120,1124],{"type":46,"value":1075},"For the single invocation and cross-check\nworkflow — ",{"type":40,"tag":65,"props":1077,"children":1079},{"className":1078},[],[1080],{"type":46,"value":858},{"type":46,"value":140},{"type":40,"tag":65,"props":1083,"children":1085},{"className":1084},[],[1086],{"type":46,"value":866},{"type":46,"value":140},{"type":40,"tag":65,"props":1089,"children":1091},{"className":1090},[],[1092],{"type":46,"value":874},{"type":46,"value":140},{"type":40,"tag":65,"props":1095,"children":1097},{"className":1096},[],[1098],{"type":46,"value":882},{"type":46,"value":140},{"type":40,"tag":65,"props":1101,"children":1103},{"className":1102},[],[1104],{"type":46,"value":890},{"type":46,"value":155},{"type":40,"tag":65,"props":1107,"children":1109},{"className":1108},[],[1110],{"type":46,"value":898},{"type":46,"value":1112},", plus the ",{"type":40,"tag":65,"props":1114,"children":1116},{"className":1115},[],[1117],{"type":46,"value":914},{"type":46,"value":1119}," — see\n",{"type":40,"tag":107,"props":1121,"children":1122},{"href":226},[1123],{"type":46,"value":226},{"type":46,"value":447},{"type":40,"tag":386,"props":1126,"children":1128},{"id":1127},"related-skills",[1129],{"type":46,"value":1130},"Related skills",{"type":40,"tag":398,"props":1132,"children":1133},{},[1134,1147,1160,1191,1214,1234],{"type":40,"tag":402,"props":1135,"children":1136},{},[1137,1145],{"type":40,"tag":107,"props":1138,"children":1139},{"href":109},[1140],{"type":40,"tag":65,"props":1141,"children":1143},{"className":1142},[],[1144],{"type":46,"value":116},{"type":46,"value":1146}," — the library\nwhose channels this tool inventories. Pair them in every\ntriage session: the program-side connection callback and the\nadmin tool's channel state are the two halves of the same\npicture.",{"type":40,"tag":402,"props":1148,"children":1149},{},[1150,1158],{"type":40,"tag":107,"props":1151,"children":1152},{"href":765},[1153],{"type":40,"tag":65,"props":1154,"children":1156},{"className":1155},[],[1157],{"type":46,"value":324},{"type":46,"value":1159},"\n— routing to the public DOCA Comm Channel Admin Tool guide and\nthe rest of the public DOCA documentation set.",{"type":40,"tag":402,"props":1161,"children":1162},{},[1163,1171,1173,1179,1181,1189],{"type":40,"tag":107,"props":1164,"children":1165},{"href":551},[1166],{"type":40,"tag":65,"props":1167,"children":1169},{"className":1168},[],[1170],{"type":46,"value":558},{"type":46,"value":1172}," — canonical DOCA\nversion-handling rules. The ",{"type":40,"tag":65,"props":1174,"children":1176},{"className":1175},[],[1177],{"type":46,"value":1178},"## Version compatibility",{"type":46,"value":1180}," section\nin ",{"type":40,"tag":107,"props":1182,"children":1183},{"href":261},[1184],{"type":40,"tag":65,"props":1185,"children":1187},{"className":1186},[],[1188],{"type":46,"value":261},{"type":46,"value":1190}," is a concise overlay\nthat redirects here for the body.",{"type":40,"tag":402,"props":1192,"children":1193},{},[1194,1202,1204,1212],{"type":40,"tag":107,"props":1195,"children":1196},{"href":919},[1197],{"type":40,"tag":65,"props":1198,"children":1200},{"className":1199},[],[1201],{"type":46,"value":926},{"type":46,"value":1203},"\n— the bundle's detect → prefer → fall back → report contract for\nstructured helper tools. The Command appendix in\n",{"type":40,"tag":107,"props":1205,"children":1206},{"href":226},[1207],{"type":40,"tag":65,"props":1208,"children":1210},{"className":1209},[],[1211],{"type":46,"value":226},{"type":46,"value":1213}," honors this contract.",{"type":40,"tag":402,"props":1215,"children":1216},{},[1217,1225,1227,1232],{"type":40,"tag":107,"props":1218,"children":1219},{"href":287},[1220],{"type":40,"tag":65,"props":1221,"children":1223},{"className":1222},[],[1224],{"type":46,"value":294},{"type":46,"value":1226}," — env preparation,\ninstall verification, representor visibility checks, and the\n",{"type":40,"tag":271,"props":1228,"children":1229},{},[1230],{"type":46,"value":1231},"I have no install yet",{"type":46,"value":1233}," path with the public NGC DOCA\ncontainer. This skill assumes its preconditions are satisfied.",{"type":40,"tag":402,"props":1235,"children":1236},{},[1237,1247,1249,1254],{"type":40,"tag":107,"props":1238,"children":1240},{"href":1239},"..\u002F..\u002Fdoca-debug\u002FSKILL.md",[1241],{"type":40,"tag":65,"props":1242,"children":1244},{"className":1243},[],[1245],{"type":46,"value":1246},"doca-debug",{"type":46,"value":1248}," — the cross-cutting\ndebug ladder. The Comm Channel Admin Tool slots in at the\n",{"type":40,"tag":271,"props":1250,"children":1251},{},[1252],{"type":46,"value":1253},"runtime",{"type":46,"value":1255}," layer as the read-only inventory surface before any\ncode change is recommended.",{"items":1257,"total":1416},[1258,1276,1294,1305,1317,1331,1344,1358,1371,1382,1396,1405],{"slug":1259,"name":1259,"fn":1260,"description":1261,"org":1262,"tags":1263,"stars":1273,"repoUrl":1274,"updatedAt":1275},"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},[1264,1267,1270],{"name":1265,"slug":1266,"type":15},"Documentation","documentation",{"name":1268,"slug":1269,"type":15},"MCP","mcp",{"name":1271,"slug":1272,"type":15},"Search","search",21777,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNemoClaw","2026-07-20T06:00:01.461044",{"slug":1277,"name":1277,"fn":1278,"description":1279,"org":1280,"tags":1281,"stars":1291,"repoUrl":1292,"updatedAt":1293},"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},[1282,1285,1288],{"name":1283,"slug":1284,"type":15},"Containers","containers",{"name":1286,"slug":1287,"type":15},"Deployment","deployment",{"name":1289,"slug":1290,"type":15},"Python","python",17049,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FMegatron-LM","2026-07-27T06:06:11.249662",{"slug":1295,"name":1295,"fn":1296,"description":1297,"org":1298,"tags":1299,"stars":1291,"repoUrl":1292,"updatedAt":1304},"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},[1300,1303],{"name":1301,"slug":1302,"type":15},"CI\u002FCD","ci-cd",{"name":1286,"slug":1287,"type":15},"2026-07-14T05:25:59.97109",{"slug":1306,"name":1306,"fn":1307,"description":1308,"org":1309,"tags":1310,"stars":1291,"repoUrl":1292,"updatedAt":1316},"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},[1311,1312,1313],{"name":1301,"slug":1302,"type":15},{"name":1286,"slug":1287,"type":15},{"name":1314,"slug":1315,"type":15},"GitHub","github","2026-07-27T06:06:12.278222",{"slug":1318,"name":1318,"fn":1319,"description":1320,"org":1321,"tags":1322,"stars":1291,"repoUrl":1292,"updatedAt":1330},"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},[1323,1326,1327],{"name":1324,"slug":1325,"type":15},"Debugging","debugging",{"name":1314,"slug":1315,"type":15},{"name":1328,"slug":1329,"type":15},"Triage","triage","2026-07-14T05:25:57.442089",{"slug":1332,"name":1332,"fn":1333,"description":1334,"org":1335,"tags":1336,"stars":1291,"repoUrl":1292,"updatedAt":1343},"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},[1337,1340],{"name":1338,"slug":1339,"type":15},"Best Practices","best-practices",{"name":1341,"slug":1342,"type":15},"Code Analysis","code-analysis","2026-07-14T05:25:56.18433",{"slug":1345,"name":1345,"fn":1346,"description":1347,"org":1348,"tags":1349,"stars":1291,"repoUrl":1292,"updatedAt":1357},"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},[1350,1353,1356],{"name":1351,"slug":1352,"type":15},"Machine Learning","machine-learning",{"name":1354,"slug":1355,"type":15},"Migration","migration",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:11.777011",{"slug":1359,"name":1359,"fn":1360,"description":1361,"org":1362,"tags":1363,"stars":1291,"repoUrl":1292,"updatedAt":1370},"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},[1364,1367],{"name":1365,"slug":1366,"type":15},"QA","qa",{"name":1368,"slug":1369,"type":15},"Testing","testing","2026-07-14T05:25:53.673039",{"slug":1372,"name":1372,"fn":1373,"description":1374,"org":1375,"tags":1376,"stars":1291,"repoUrl":1292,"updatedAt":1381},"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},[1377,1378],{"name":1286,"slug":1287,"type":15},{"name":1379,"slug":1380,"type":15},"Infrastructure","infrastructure","2026-07-14T05:25:49.362534",{"slug":1383,"name":1383,"fn":1384,"description":1385,"org":1386,"tags":1387,"stars":1291,"repoUrl":1292,"updatedAt":1395},"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},[1388,1391,1392],{"name":1389,"slug":1390,"type":15},"Code Review","code-review",{"name":1314,"slug":1315,"type":15},{"name":1393,"slug":1394,"type":15},"Pull Requests","pull-requests","2026-07-14T05:26:01.226578",{"slug":1397,"name":1397,"fn":1398,"description":1399,"org":1400,"tags":1401,"stars":1291,"repoUrl":1292,"updatedAt":1404},"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},[1402,1403],{"name":1365,"slug":1366,"type":15},{"name":1368,"slug":1369,"type":15},"2026-07-14T05:25:54.928983",{"slug":1406,"name":1406,"fn":1407,"description":1408,"org":1409,"tags":1410,"stars":1291,"repoUrl":1292,"updatedAt":1415},"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},[1411,1414],{"name":1412,"slug":1413,"type":15},"Automation","automation",{"name":1301,"slug":1302,"type":15},"2026-07-30T05:29:03.275638",496,{"items":1418,"total":1512},[1419,1436,1446,1460,1470,1485,1498],{"slug":1420,"name":1420,"fn":1421,"description":1422,"org":1423,"tags":1424,"stars":20,"repoUrl":21,"updatedAt":1435},"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},[1425,1428,1431,1432],{"name":1426,"slug":1427,"type":15},"Data Analysis","data-analysis",{"name":1429,"slug":1430,"type":15},"Data Engineering","data-engineering",{"name":9,"slug":8,"type":15},{"name":1433,"slug":1434,"type":15},"Performance","performance","2026-07-14T05:28:43.176466",{"slug":1437,"name":1437,"fn":1438,"description":1439,"org":1440,"tags":1441,"stars":20,"repoUrl":21,"updatedAt":1445},"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},[1442,1443,1444],{"name":1286,"slug":1287,"type":15},{"name":1379,"slug":1380,"type":15},{"name":9,"slug":8,"type":15},"2026-07-14T05:29:06.667109",{"slug":1447,"name":1447,"fn":1448,"description":1449,"org":1450,"tags":1451,"stars":20,"repoUrl":21,"updatedAt":1459},"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},[1452,1455,1456],{"name":1453,"slug":1454,"type":15},"Agents","agents",{"name":9,"slug":8,"type":15},{"name":1457,"slug":1458,"type":15},"Research","research","2026-07-14T05:28:06.816956",{"slug":1461,"name":1461,"fn":1462,"description":1463,"org":1464,"tags":1465,"stars":20,"repoUrl":21,"updatedAt":1469},"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},[1466,1467,1468],{"name":1426,"slug":1427,"type":15},{"name":9,"slug":8,"type":15},{"name":1368,"slug":1369,"type":15},"2026-07-17T05:29:03.913266",{"slug":1471,"name":1471,"fn":1472,"description":1473,"org":1474,"tags":1475,"stars":20,"repoUrl":21,"updatedAt":1484},"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},[1476,1477,1480,1481],{"name":1412,"slug":1413,"type":15},{"name":1478,"slug":1479,"type":15},"Imaging","imaging",{"name":9,"slug":8,"type":15},{"name":1482,"slug":1483,"type":15},"Video","video","2026-07-17T05:28:53.905004",{"slug":1486,"name":1486,"fn":1487,"description":1488,"org":1489,"tags":1490,"stars":20,"repoUrl":21,"updatedAt":1497},"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},[1491,1492,1495,1496],{"name":1286,"slug":1287,"type":15},{"name":1493,"slug":1494,"type":15},"Docker","docker",{"name":9,"slug":8,"type":15},{"name":13,"slug":14,"type":15},"2026-07-17T05:28:56.913999",{"slug":1499,"name":1499,"fn":1500,"description":1501,"org":1502,"tags":1503,"stars":20,"repoUrl":21,"updatedAt":1511},"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},[1504,1505,1508],{"name":9,"slug":8,"type":15},{"name":1506,"slug":1507,"type":15},"Quantum Computing","quantum-computing",{"name":1509,"slug":1510,"type":15},"Simulation","simulation","2026-07-14T05:26:58.898253",305]