[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-nvidia-nvshmem-docs":3,"mdc--5a6yyt-key":36,"related-repo-nvidia-nvshmem-docs":596,"related-org-nvidia-nvshmem-docs":679},{"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":31,"sourceUrl":34,"mdContent":35},"nvshmem-docs","fetch official NVSHMEM documentation","Find version-aware official NVSHMEM and NVSHMEM4Py documentation for releases, installation, APIs, runtime settings, transports, containers, and troubleshooting.",{"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,19],{"name":13,"slug":14,"type":15},"Documentation","documentation","tag",{"name":17,"slug":18,"type":15},"Reference","reference",{"name":9,"slug":8,"type":15},579,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnvshmem","2026-08-31T09:19:00.214841","Apache-2.0",104,[26,27,28,29,8,30],"communciations","cpp","cuda","deep-learning","python",{"repoUrl":21,"stars":20,"forks":24,"topics":32,"description":33},[26,27,28,29,8,30],"NVIDIA NVSHMEM is a parallel programming interface for NVIDIA GPUs based on OpenSHMEM. NVSHMEM can significantly reduce multi-process communication and coordination overheads by allowing programmers to perform one-sided communication from within CUDA kernels and on CUDA streams.","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnvshmem\u002Ftree\u002FHEAD\u002Fskills\u002Fnvshmem-docs","---\nname: nvshmem-docs\ndescription: Find version-aware official NVSHMEM and NVSHMEM4Py documentation for releases, installation, APIs, runtime settings, transports, containers, and troubleshooting.\nlicense: Apache-2.0\nmetadata:\n  version: \"1.0.0\"\n  author: NVIDIA NVSHMEM Team \u003Cnvshmem@nvidia.com>\n  tags:\n    - nvshmem\n    - docs\n---\n\n# NVSHMEM Documentation\n\n## Purpose\n\nFind and summarize version-aware official NVSHMEM and NVSHMEM4Py documentation. Fetch and cite the most specific live pages; do not make technical claims from memory, search snippets, or the bundled topic map.\n\n## Prerequisites\n\nRequire [topic-map.md](references\u002Ftopic-map.md) and a retrieval tool that can open public NVIDIA HTTPS documentation. No API key or account is required. Support only NVSHMEM versions whose major version is 3 or later; reject a requested version below 3 before looking up documentation.\n\n## Instructions\n\nRead the topic map for every request to resolve the topic and candidate pages. Use it only for routing; it is not evidence.\n\n### Choose the documentation edition\n\nNormalize an optional leading `v`. Use `latest` when no version is requested. For an exact `MAJOR.MINOR.PATCH` version, first use its archive. Replace the literal `VERSION` in each archive URL below with the normalized NVSHMEM version (for example, `3.7.1` becomes `https:\u002F\u002Farchive.docs.nvidia.com\u002Fnvshmem\u002Fapi\u002F3.7.1\u002Findex.html`):\n\n| Content | Latest | Exact-version archive |\n| --- | --- | --- |\n| API reference, concepts, usage, and runtime settings | `https:\u002F\u002Fdocs.nvidia.com\u002Fnvshmem\u002Fapi\u002Flatest\u002F` | `https:\u002F\u002Farchive.docs.nvidia.com\u002Fnvshmem\u002Fapi\u002FVERSION\u002Findex.html` |\n| Release notes, installation, best practices, and support | `https:\u002F\u002Fdocs.nvidia.com\u002Fnvshmem\u002Frelease-notes-install-guide\u002F` | `https:\u002F\u002Farchive.docs.nvidia.com\u002Fnvshmem\u002FVERSION\u002Findex.html` |\n\nFor a `MAJOR.MINOR` value, ask for the patch only when an exact archived edition is necessary. Start at the selected root and follow its table of contents because internal paths can differ between editions. For cross-cutting questions, use both documentation sets from the same edition.\n\nWhen an exact archive is unavailable, inspect the relevant `latest` root and its official release\u002Fversion information. If it identifies the requested version as the current release, use that latest documentation and state that the requested version is served from `latest` rather than an archive. If `latest` identifies a different version, report that the requested archive is unavailable; offer the different latest documentation only as clearly labeled current context. Never silently use latest documentation for another version.\n\n### Retrieve and answer\n\n1. Infer the topic and optional version from the user or invoking skill, then route it with the topic map.\n2. Open the appropriate root above and the relevant topic page in that edition. If an exact archive is unavailable, resolve whether `latest` is the requested version before using it as evidence.\n3. Answer concisely with direct official links. State the documentation version when one was requested or applicability matters.\n4. If an exact archive cannot be retrieved and latest is a different version, say so. Offer clearly labeled latest context only if useful.\n\nIf live pages cannot be retrieved, return the appropriate root links, state that their contents were not verified, and avoid documentation-backed technical claims.\n\n### Handle NVSHMEM4Py\n\nFor an NVSHMEM4Py request with no version, use the latest documentation. If an NVSHMEM version is requested, use that NVSHMEM documentation edition without resolving the NVSHMEM4Py package version. Only when an NVSHMEM4Py version or version compatibility is requested, resolve the independent version pair from the live compatibility guide—never infer or hard-code it—and use the resolved NVSHMEM version to select an archive. Ask only when a bare version is ambiguous or multiple NVSHMEM releases match.\n\nUnprefixed topic-map gates apply to NVSHMEM. Prefix a Python-only gate with `nvshmem4py:`, compare it only with the NVSHMEM4Py version, and name the version axis in the answer.\n\n### Check version gates\n\nWhen a routed topic-map row has `introduced_in` or `removed_in`, verify the gate from its live official evidence and always report it. Compare NVSHMEM gates by `MAJOR.MINOR` and `nvshmem4py:` gates by the full package version. Report a mismatch when the requested version is before `introduced_in` or at\u002Fafter `removed_in`; otherwise report no mismatch. Use a compact form such as `Version gate: introduced in 3.7; requested 3.5 — mismatch.`\n\nDo not perform a broader availability search merely because a version was supplied. Only do so when the user explicitly asks whether an ungated feature or exact symbol is available, introduced, removed, or supported. Then inspect the requested archive and matching release notes. Absence from a page or search result is inconclusive; if evidence is not decisive, say availability could not be established.\n\nFor NVIDIA HPC SDK containers, use the official NGC catalog and HPC SDK documentation for container procedures. Do not infer the bundled NVSHMEM version from an image tag unless an official page states it.\n\n## Limitations\n\n- Documentation does not prove installed binaries, container contents, configuration, runtime behavior, or performance.\n- A missing page, symbol, or search result does not prove unavailability.\n- Technical answers require retrieved live official evidence; the topic map is only a routing index.\n\n## Troubleshooting\n\n| Error | Cause | Solution |\n| --- | --- | --- |\n| Topic-map route fails | Documentation moved | Navigate the selected edition's live table of contents. |\n| Exact archive fails | The edition is unavailable, is the current unarchived release, or retrieval failed | Inspect `latest` to identify its version. Use it only when it matches the request; otherwise report the failure and offer it only as clearly labeled current context. |\n| Requested NVSHMEM version is below 3.0 | Unsupported documentation edition | Reject the request; do not search archive or latest documentation. |\n| Version is ambiguous | Component was not named | Ask whether it is an NVSHMEM or NVSHMEM4Py version. |\n| Compatibility is unresolved | No unique live compatibility row exists | Report the candidates or uncertainty; do not infer a pair. |\n\n## Examples\n\n```text\nUse $nvshmem-docs to explain NVSHMEM_THREAD_SERIALIZED.\nUse $nvshmem-docs to find NVSHMEM4Py installation documentation for NVSHMEM 3.5.21.\nUse $nvshmem-docs to check whether NVSHMEM4Py 0.2.2 is compatible with NVSHMEM 3.6.5.\n```\n",{"data":37,"body":44},{"name":4,"description":6,"license":23,"metadata":38},{"version":39,"author":40,"tags":41},"1.0.0","NVIDIA NVSHMEM Team \u003Cnvshmem@nvidia.com>",[42,43],"nvshmem","docs",{"type":45,"children":46},"root",[47,56,63,69,75,89,95,100,107,161,246,259,285,291,323,328,334,339,352,358,413,418,423,429,448,454,578,584],{"type":48,"tag":49,"props":50,"children":52},"element","h1",{"id":51},"nvshmem-documentation",[53],{"type":54,"value":55},"text","NVSHMEM Documentation",{"type":48,"tag":57,"props":58,"children":60},"h2",{"id":59},"purpose",[61],{"type":54,"value":62},"Purpose",{"type":48,"tag":64,"props":65,"children":66},"p",{},[67],{"type":54,"value":68},"Find and summarize version-aware official NVSHMEM and NVSHMEM4Py documentation. Fetch and cite the most specific live pages; do not make technical claims from memory, search snippets, or the bundled topic map.",{"type":48,"tag":57,"props":70,"children":72},{"id":71},"prerequisites",[73],{"type":54,"value":74},"Prerequisites",{"type":48,"tag":64,"props":76,"children":77},{},[78,80,87],{"type":54,"value":79},"Require ",{"type":48,"tag":81,"props":82,"children":84},"a",{"href":83},"references\u002Ftopic-map.md",[85],{"type":54,"value":86},"topic-map.md",{"type":54,"value":88}," and a retrieval tool that can open public NVIDIA HTTPS documentation. No API key or account is required. Support only NVSHMEM versions whose major version is 3 or later; reject a requested version below 3 before looking up documentation.",{"type":48,"tag":57,"props":90,"children":92},{"id":91},"instructions",[93],{"type":54,"value":94},"Instructions",{"type":48,"tag":64,"props":96,"children":97},{},[98],{"type":54,"value":99},"Read the topic map for every request to resolve the topic and candidate pages. Use it only for routing; it is not evidence.",{"type":48,"tag":101,"props":102,"children":104},"h3",{"id":103},"choose-the-documentation-edition",[105],{"type":54,"value":106},"Choose the documentation edition",{"type":48,"tag":64,"props":108,"children":109},{},[110,112,119,121,127,129,135,137,143,145,151,153,159],{"type":54,"value":111},"Normalize an optional leading ",{"type":48,"tag":113,"props":114,"children":116},"code",{"className":115},[],[117],{"type":54,"value":118},"v",{"type":54,"value":120},". Use ",{"type":48,"tag":113,"props":122,"children":124},{"className":123},[],[125],{"type":54,"value":126},"latest",{"type":54,"value":128}," when no version is requested. For an exact ",{"type":48,"tag":113,"props":130,"children":132},{"className":131},[],[133],{"type":54,"value":134},"MAJOR.MINOR.PATCH",{"type":54,"value":136}," version, first use its archive. Replace the literal ",{"type":48,"tag":113,"props":138,"children":140},{"className":139},[],[141],{"type":54,"value":142},"VERSION",{"type":54,"value":144}," in each archive URL below with the normalized NVSHMEM version (for example, ",{"type":48,"tag":113,"props":146,"children":148},{"className":147},[],[149],{"type":54,"value":150},"3.7.1",{"type":54,"value":152}," becomes ",{"type":48,"tag":113,"props":154,"children":156},{"className":155},[],[157],{"type":54,"value":158},"https:\u002F\u002Farchive.docs.nvidia.com\u002Fnvshmem\u002Fapi\u002F3.7.1\u002Findex.html",{"type":54,"value":160},"):",{"type":48,"tag":162,"props":163,"children":164},"table",{},[165,189],{"type":48,"tag":166,"props":167,"children":168},"thead",{},[169],{"type":48,"tag":170,"props":171,"children":172},"tr",{},[173,179,184],{"type":48,"tag":174,"props":175,"children":176},"th",{},[177],{"type":54,"value":178},"Content",{"type":48,"tag":174,"props":180,"children":181},{},[182],{"type":54,"value":183},"Latest",{"type":48,"tag":174,"props":185,"children":186},{},[187],{"type":54,"value":188},"Exact-version archive",{"type":48,"tag":190,"props":191,"children":192},"tbody",{},[193,220],{"type":48,"tag":170,"props":194,"children":195},{},[196,202,211],{"type":48,"tag":197,"props":198,"children":199},"td",{},[200],{"type":54,"value":201},"API reference, concepts, usage, and runtime settings",{"type":48,"tag":197,"props":203,"children":204},{},[205],{"type":48,"tag":113,"props":206,"children":208},{"className":207},[],[209],{"type":54,"value":210},"https:\u002F\u002Fdocs.nvidia.com\u002Fnvshmem\u002Fapi\u002Flatest\u002F",{"type":48,"tag":197,"props":212,"children":213},{},[214],{"type":48,"tag":113,"props":215,"children":217},{"className":216},[],[218],{"type":54,"value":219},"https:\u002F\u002Farchive.docs.nvidia.com\u002Fnvshmem\u002Fapi\u002FVERSION\u002Findex.html",{"type":48,"tag":170,"props":221,"children":222},{},[223,228,237],{"type":48,"tag":197,"props":224,"children":225},{},[226],{"type":54,"value":227},"Release notes, installation, best practices, and support",{"type":48,"tag":197,"props":229,"children":230},{},[231],{"type":48,"tag":113,"props":232,"children":234},{"className":233},[],[235],{"type":54,"value":236},"https:\u002F\u002Fdocs.nvidia.com\u002Fnvshmem\u002Frelease-notes-install-guide\u002F",{"type":48,"tag":197,"props":238,"children":239},{},[240],{"type":48,"tag":113,"props":241,"children":243},{"className":242},[],[244],{"type":54,"value":245},"https:\u002F\u002Farchive.docs.nvidia.com\u002Fnvshmem\u002FVERSION\u002Findex.html",{"type":48,"tag":64,"props":247,"children":248},{},[249,251,257],{"type":54,"value":250},"For a ",{"type":48,"tag":113,"props":252,"children":254},{"className":253},[],[255],{"type":54,"value":256},"MAJOR.MINOR",{"type":54,"value":258}," value, ask for the patch only when an exact archived edition is necessary. Start at the selected root and follow its table of contents because internal paths can differ between editions. For cross-cutting questions, use both documentation sets from the same edition.",{"type":48,"tag":64,"props":260,"children":261},{},[262,264,269,271,276,278,283],{"type":54,"value":263},"When an exact archive is unavailable, inspect the relevant ",{"type":48,"tag":113,"props":265,"children":267},{"className":266},[],[268],{"type":54,"value":126},{"type":54,"value":270}," root and its official release\u002Fversion information. If it identifies the requested version as the current release, use that latest documentation and state that the requested version is served from ",{"type":48,"tag":113,"props":272,"children":274},{"className":273},[],[275],{"type":54,"value":126},{"type":54,"value":277}," rather than an archive. If ",{"type":48,"tag":113,"props":279,"children":281},{"className":280},[],[282],{"type":54,"value":126},{"type":54,"value":284}," identifies a different version, report that the requested archive is unavailable; offer the different latest documentation only as clearly labeled current context. Never silently use latest documentation for another version.",{"type":48,"tag":101,"props":286,"children":288},{"id":287},"retrieve-and-answer",[289],{"type":54,"value":290},"Retrieve and answer",{"type":48,"tag":292,"props":293,"children":294},"ol",{},[295,301,313,318],{"type":48,"tag":296,"props":297,"children":298},"li",{},[299],{"type":54,"value":300},"Infer the topic and optional version from the user or invoking skill, then route it with the topic map.",{"type":48,"tag":296,"props":302,"children":303},{},[304,306,311],{"type":54,"value":305},"Open the appropriate root above and the relevant topic page in that edition. If an exact archive is unavailable, resolve whether ",{"type":48,"tag":113,"props":307,"children":309},{"className":308},[],[310],{"type":54,"value":126},{"type":54,"value":312}," is the requested version before using it as evidence.",{"type":48,"tag":296,"props":314,"children":315},{},[316],{"type":54,"value":317},"Answer concisely with direct official links. State the documentation version when one was requested or applicability matters.",{"type":48,"tag":296,"props":319,"children":320},{},[321],{"type":54,"value":322},"If an exact archive cannot be retrieved and latest is a different version, say so. Offer clearly labeled latest context only if useful.",{"type":48,"tag":64,"props":324,"children":325},{},[326],{"type":54,"value":327},"If live pages cannot be retrieved, return the appropriate root links, state that their contents were not verified, and avoid documentation-backed technical claims.",{"type":48,"tag":101,"props":329,"children":331},{"id":330},"handle-nvshmem4py",[332],{"type":54,"value":333},"Handle NVSHMEM4Py",{"type":48,"tag":64,"props":335,"children":336},{},[337],{"type":54,"value":338},"For an NVSHMEM4Py request with no version, use the latest documentation. If an NVSHMEM version is requested, use that NVSHMEM documentation edition without resolving the NVSHMEM4Py package version. Only when an NVSHMEM4Py version or version compatibility is requested, resolve the independent version pair from the live compatibility guide—never infer or hard-code it—and use the resolved NVSHMEM version to select an archive. Ask only when a bare version is ambiguous or multiple NVSHMEM releases match.",{"type":48,"tag":64,"props":340,"children":341},{},[342,344,350],{"type":54,"value":343},"Unprefixed topic-map gates apply to NVSHMEM. Prefix a Python-only gate with ",{"type":48,"tag":113,"props":345,"children":347},{"className":346},[],[348],{"type":54,"value":349},"nvshmem4py:",{"type":54,"value":351},", compare it only with the NVSHMEM4Py version, and name the version axis in the answer.",{"type":48,"tag":101,"props":353,"children":355},{"id":354},"check-version-gates",[356],{"type":54,"value":357},"Check version gates",{"type":48,"tag":64,"props":359,"children":360},{},[361,363,369,371,377,379,384,386,391,393,398,400,405,407],{"type":54,"value":362},"When a routed topic-map row has ",{"type":48,"tag":113,"props":364,"children":366},{"className":365},[],[367],{"type":54,"value":368},"introduced_in",{"type":54,"value":370}," or ",{"type":48,"tag":113,"props":372,"children":374},{"className":373},[],[375],{"type":54,"value":376},"removed_in",{"type":54,"value":378},", verify the gate from its live official evidence and always report it. Compare NVSHMEM gates by ",{"type":48,"tag":113,"props":380,"children":382},{"className":381},[],[383],{"type":54,"value":256},{"type":54,"value":385}," and ",{"type":48,"tag":113,"props":387,"children":389},{"className":388},[],[390],{"type":54,"value":349},{"type":54,"value":392}," gates by the full package version. Report a mismatch when the requested version is before ",{"type":48,"tag":113,"props":394,"children":396},{"className":395},[],[397],{"type":54,"value":368},{"type":54,"value":399}," or at\u002Fafter ",{"type":48,"tag":113,"props":401,"children":403},{"className":402},[],[404],{"type":54,"value":376},{"type":54,"value":406},"; otherwise report no mismatch. Use a compact form such as ",{"type":48,"tag":113,"props":408,"children":410},{"className":409},[],[411],{"type":54,"value":412},"Version gate: introduced in 3.7; requested 3.5 — mismatch.",{"type":48,"tag":64,"props":414,"children":415},{},[416],{"type":54,"value":417},"Do not perform a broader availability search merely because a version was supplied. Only do so when the user explicitly asks whether an ungated feature or exact symbol is available, introduced, removed, or supported. Then inspect the requested archive and matching release notes. Absence from a page or search result is inconclusive; if evidence is not decisive, say availability could not be established.",{"type":48,"tag":64,"props":419,"children":420},{},[421],{"type":54,"value":422},"For NVIDIA HPC SDK containers, use the official NGC catalog and HPC SDK documentation for container procedures. Do not infer the bundled NVSHMEM version from an image tag unless an official page states it.",{"type":48,"tag":57,"props":424,"children":426},{"id":425},"limitations",[427],{"type":54,"value":428},"Limitations",{"type":48,"tag":430,"props":431,"children":432},"ul",{},[433,438,443],{"type":48,"tag":296,"props":434,"children":435},{},[436],{"type":54,"value":437},"Documentation does not prove installed binaries, container contents, configuration, runtime behavior, or performance.",{"type":48,"tag":296,"props":439,"children":440},{},[441],{"type":54,"value":442},"A missing page, symbol, or search result does not prove unavailability.",{"type":48,"tag":296,"props":444,"children":445},{},[446],{"type":54,"value":447},"Technical answers require retrieved live official evidence; the topic map is only a routing index.",{"type":48,"tag":57,"props":449,"children":451},{"id":450},"troubleshooting",[452],{"type":54,"value":453},"Troubleshooting",{"type":48,"tag":162,"props":455,"children":456},{},[457,478],{"type":48,"tag":166,"props":458,"children":459},{},[460],{"type":48,"tag":170,"props":461,"children":462},{},[463,468,473],{"type":48,"tag":174,"props":464,"children":465},{},[466],{"type":54,"value":467},"Error",{"type":48,"tag":174,"props":469,"children":470},{},[471],{"type":54,"value":472},"Cause",{"type":48,"tag":174,"props":474,"children":475},{},[476],{"type":54,"value":477},"Solution",{"type":48,"tag":190,"props":479,"children":480},{},[481,499,524,542,560],{"type":48,"tag":170,"props":482,"children":483},{},[484,489,494],{"type":48,"tag":197,"props":485,"children":486},{},[487],{"type":54,"value":488},"Topic-map route fails",{"type":48,"tag":197,"props":490,"children":491},{},[492],{"type":54,"value":493},"Documentation moved",{"type":48,"tag":197,"props":495,"children":496},{},[497],{"type":54,"value":498},"Navigate the selected edition's live table of contents.",{"type":48,"tag":170,"props":500,"children":501},{},[502,507,512],{"type":48,"tag":197,"props":503,"children":504},{},[505],{"type":54,"value":506},"Exact archive fails",{"type":48,"tag":197,"props":508,"children":509},{},[510],{"type":54,"value":511},"The edition is unavailable, is the current unarchived release, or retrieval failed",{"type":48,"tag":197,"props":513,"children":514},{},[515,517,522],{"type":54,"value":516},"Inspect ",{"type":48,"tag":113,"props":518,"children":520},{"className":519},[],[521],{"type":54,"value":126},{"type":54,"value":523}," to identify its version. Use it only when it matches the request; otherwise report the failure and offer it only as clearly labeled current context.",{"type":48,"tag":170,"props":525,"children":526},{},[527,532,537],{"type":48,"tag":197,"props":528,"children":529},{},[530],{"type":54,"value":531},"Requested NVSHMEM version is below 3.0",{"type":48,"tag":197,"props":533,"children":534},{},[535],{"type":54,"value":536},"Unsupported documentation edition",{"type":48,"tag":197,"props":538,"children":539},{},[540],{"type":54,"value":541},"Reject the request; do not search archive or latest documentation.",{"type":48,"tag":170,"props":543,"children":544},{},[545,550,555],{"type":48,"tag":197,"props":546,"children":547},{},[548],{"type":54,"value":549},"Version is ambiguous",{"type":48,"tag":197,"props":551,"children":552},{},[553],{"type":54,"value":554},"Component was not named",{"type":48,"tag":197,"props":556,"children":557},{},[558],{"type":54,"value":559},"Ask whether it is an NVSHMEM or NVSHMEM4Py version.",{"type":48,"tag":170,"props":561,"children":562},{},[563,568,573],{"type":48,"tag":197,"props":564,"children":565},{},[566],{"type":54,"value":567},"Compatibility is unresolved",{"type":48,"tag":197,"props":569,"children":570},{},[571],{"type":54,"value":572},"No unique live compatibility row exists",{"type":48,"tag":197,"props":574,"children":575},{},[576],{"type":54,"value":577},"Report the candidates or uncertainty; do not infer a pair.",{"type":48,"tag":57,"props":579,"children":581},{"id":580},"examples",[582],{"type":54,"value":583},"Examples",{"type":48,"tag":585,"props":586,"children":591},"pre",{"className":587,"code":589,"language":54,"meta":590},[588],"language-text","Use $nvshmem-docs to explain NVSHMEM_THREAD_SERIALIZED.\nUse $nvshmem-docs to find NVSHMEM4Py installation documentation for NVSHMEM 3.5.21.\nUse $nvshmem-docs to check whether NVSHMEM4Py 0.2.2 is compatible with NVSHMEM 3.6.5.\n","",[592],{"type":48,"tag":113,"props":593,"children":594},{"__ignoreMap":590},[595],{"type":54,"value":589},{"items":597,"total":678},[598,612,626,632,644,656,668],{"slug":599,"name":599,"fn":600,"description":601,"org":602,"tags":603,"stars":20,"repoUrl":21,"updatedAt":611},"nvshmem-collect-performance-data","collect NVSHMEM performance metrics","Collect and package NVSHMEM put\u002Fget bandwidth, latency, and other perftest results with system and topology evidence for performance sanity checks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[604,607,608],{"name":605,"slug":606,"type":15},"Monitoring","monitoring",{"name":9,"slug":8,"type":15},{"name":609,"slug":610,"type":15},"Performance","performance","2026-08-31T09:19:00.917887",{"slug":613,"name":613,"fn":614,"description":615,"org":616,"tags":617,"stars":20,"repoUrl":21,"updatedAt":625},"nvshmem-configure-nic-pe-mapping","configure NVSHMEM NIC-to-PE mappings","Recommend NVSHMEM NIC-to-PE mappings and environment exports. Use for HCA selection, multi-NIC configuration, or topology-based mapping diagnostics.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[618,621,624],{"name":619,"slug":620,"type":15},"Configuration","configuration",{"name":622,"slug":623,"type":15},"Networking","networking",{"name":9,"slug":8,"type":15},"2026-08-31T09:19:06.10294",{"slug":4,"name":4,"fn":5,"description":6,"org":627,"tags":628,"stars":20,"repoUrl":21,"updatedAt":22},{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[629,630,631],{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},{"name":17,"slug":18,"type":15},{"slug":633,"name":633,"fn":634,"description":635,"org":636,"tags":637,"stars":20,"repoUrl":21,"updatedAt":643},"nvshmem-enable-tma","optimize NVSHMEM CUDA kernels for TMA","Prepare or review NVSHMEM CUDA kernels for TMA SMEM registration and direct-SMEM transfers. Do not use for unrelated CUDA tuning.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[638,641,642],{"name":639,"slug":640,"type":15},"Engineering","engineering",{"name":9,"slug":8,"type":15},{"name":609,"slug":610,"type":15},"2026-08-31T09:18:50.449676",{"slug":645,"name":645,"fn":646,"description":647,"org":648,"tags":649,"stars":20,"repoUrl":21,"updatedAt":655},"nvshmem-get-started","onboard developers to NVSHMEM","Guide NVSHMEM beginners through fit assessment, mental models, first C\u002FC++ or Python NVSHMEM programs, compilation, launching, and next steps. Use for onboarding.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[650,651,652],{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},{"name":653,"slug":654,"type":15},"Onboarding","onboarding","2026-08-31T09:18:55.48573",{"slug":657,"name":657,"fn":658,"description":659,"org":660,"tags":661,"stars":20,"repoUrl":21,"updatedAt":667},"nvshmem-install","install and validate NVSHMEM","Plan and validate NVSHMEM and NVSHMEM4Py installations. Use for package, container, or source deployments.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[662,665,666],{"name":663,"slug":664,"type":15},"Deployment","deployment",{"name":639,"slug":640,"type":15},{"name":9,"slug":8,"type":15},"2026-08-31T09:18:50.105521",{"slug":669,"name":669,"fn":670,"description":671,"org":672,"tags":673,"stars":20,"repoUrl":21,"updatedAt":677},"nvshmem-select-remote-transport","select NVSHMEM remote transport configurations","Select an NVSHMEM remote transport from target system and kernel evidence. Use for inter-node selection, compatibility checks, or configuration.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[674,675,676],{"name":619,"slug":620,"type":15},{"name":9,"slug":8,"type":15},{"name":609,"slug":610,"type":15},"2026-08-31T09:18:59.493722",9,{"items":680,"total":834},[681,697,712,723,735,749,762,776,789,800,814,823],{"slug":682,"name":682,"fn":683,"description":684,"org":685,"tags":686,"stars":694,"repoUrl":695,"updatedAt":696},"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},[687,688,691],{"name":13,"slug":14,"type":15},{"name":689,"slug":690,"type":15},"MCP","mcp",{"name":692,"slug":693,"type":15},"Search","search",21777,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNemoClaw","2026-08-25T03:29:57.273192",{"slug":698,"name":698,"fn":699,"description":700,"org":701,"tags":702,"stars":709,"repoUrl":710,"updatedAt":711},"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},[703,706,707],{"name":704,"slug":705,"type":15},"Containers","containers",{"name":663,"slug":664,"type":15},{"name":708,"slug":30,"type":15},"Python",17049,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FMegatron-LM","2026-07-27T06:06:11.249662",{"slug":713,"name":713,"fn":714,"description":715,"org":716,"tags":717,"stars":709,"repoUrl":710,"updatedAt":722},"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},[718,721],{"name":719,"slug":720,"type":15},"CI\u002FCD","ci-cd",{"name":663,"slug":664,"type":15},"2026-07-14T05:25:59.97109",{"slug":724,"name":724,"fn":725,"description":726,"org":727,"tags":728,"stars":709,"repoUrl":710,"updatedAt":734},"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},[729,730,731],{"name":719,"slug":720,"type":15},{"name":663,"slug":664,"type":15},{"name":732,"slug":733,"type":15},"GitHub","github","2026-08-28T14:38:16.959248",{"slug":736,"name":736,"fn":737,"description":738,"org":739,"tags":740,"stars":709,"repoUrl":710,"updatedAt":748},"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},[741,744,745],{"name":742,"slug":743,"type":15},"Debugging","debugging",{"name":732,"slug":733,"type":15},{"name":746,"slug":747,"type":15},"Triage","triage","2026-07-14T05:25:57.442089",{"slug":750,"name":750,"fn":751,"description":752,"org":753,"tags":754,"stars":709,"repoUrl":710,"updatedAt":761},"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},[755,758],{"name":756,"slug":757,"type":15},"Best Practices","best-practices",{"name":759,"slug":760,"type":15},"Code Analysis","code-analysis","2026-07-14T05:25:56.18433",{"slug":763,"name":763,"fn":764,"description":765,"org":766,"tags":767,"stars":709,"repoUrl":710,"updatedAt":775},"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, including the mechanical steps for transferring an existing pretrain_gpt.py launch script.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[768,771,774],{"name":769,"slug":770,"type":15},"Machine Learning","machine-learning",{"name":772,"slug":773,"type":15},"Migration","migration",{"name":9,"slug":8,"type":15},"2026-08-21T03:36:57.470256",{"slug":777,"name":777,"fn":778,"description":779,"org":780,"tags":781,"stars":709,"repoUrl":710,"updatedAt":788},"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},[782,785],{"name":783,"slug":784,"type":15},"QA","qa",{"name":786,"slug":787,"type":15},"Testing","testing","2026-07-14T05:25:53.673039",{"slug":790,"name":790,"fn":791,"description":792,"org":793,"tags":794,"stars":709,"repoUrl":710,"updatedAt":799},"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},[795,796],{"name":663,"slug":664,"type":15},{"name":797,"slug":798,"type":15},"Infrastructure","infrastructure","2026-07-14T05:25:49.362534",{"slug":801,"name":801,"fn":802,"description":803,"org":804,"tags":805,"stars":709,"repoUrl":710,"updatedAt":813},"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},[806,809,810],{"name":807,"slug":808,"type":15},"Code Review","code-review",{"name":732,"slug":733,"type":15},{"name":811,"slug":812,"type":15},"Pull Requests","pull-requests","2026-08-25T03:29:16.211287",{"slug":815,"name":815,"fn":816,"description":817,"org":818,"tags":819,"stars":709,"repoUrl":710,"updatedAt":822},"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},[820,821],{"name":783,"slug":784,"type":15},{"name":786,"slug":787,"type":15},"2026-07-14T05:25:54.928983",{"slug":824,"name":824,"fn":825,"description":826,"org":827,"tags":828,"stars":709,"repoUrl":710,"updatedAt":833},"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},[829,832],{"name":830,"slug":831,"type":15},"Automation","automation",{"name":719,"slug":720,"type":15},"2026-07-30T05:29:03.275638",563]