[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-nvidia-nemo-relay-plugin-adaptive-tuning":3,"mdc-106yiq-key":52,"related-repo-nvidia-nemo-relay-plugin-adaptive-tuning":502,"related-org-nvidia-nemo-relay-plugin-adaptive-tuning":613},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":47,"sourceUrl":50,"mdContent":51},"nemo-relay-plugin-adaptive-tuning","evaluate adaptive NeMo Relay plugin behavior","Use this skill when baseline NeMo Relay instrumentation exists and the user wants to configure or evaluate adaptive plugin behavior, including telemetry, state, adaptive_hints, tool_parallelism, ACG, hint consumption, or measured rollout.",{"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,20],{"name":13,"slug":14,"type":15},"Performance","performance","tag",{"name":9,"slug":8,"type":15},{"name":18,"slug":19,"type":15},"Engineering","engineering",{"name":21,"slug":22,"type":15},"AI Infrastructure","ai-infrastructure",75,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Relay","2026-07-17T05:30:26.085261","Apache-2.0",41,[29,30,31,32,33,34,35,36,37,38,39,8,40,41,42,43,44,45,46],"agents","ai","atif","atof","claude-code","codex","deepagents","hermes-agent","langchain","langgraph","middleware","observability","openclaw","openinference","optimization","otel","runtime","security",{"repoUrl":24,"stars":23,"forks":27,"topics":48,"description":49},[29,30,31,32,33,34,35,36,37,38,39,8,40,41,42,43,44,45,46],"Multi-language agent runtime and library for execution scope management, lifecycle events, and middleware on tool and LLM calls.","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Relay\u002Ftree\u002FHEAD\u002Fskills\u002Fnemo-relay-plugin-adaptive-tuning","---\nname: nemo-relay-plugin-adaptive-tuning\ndescription: Use this skill when baseline NeMo Relay instrumentation exists and the user wants to configure or evaluate adaptive plugin behavior, including telemetry, state, adaptive_hints, tool_parallelism, ACG, hint consumption, or measured rollout.\nlicense: Apache-2.0\nmetadata:\n  author: NVIDIA Corporation and Affiliates\n---\n\n# Tune Adaptive Plugin Behavior\n\n## Use This When\n\nUse this skill when a user has baseline NeMo Relay instrumentation and wants to\nimprove latency, parallelism, prompt-cache behavior, or model-request behavior\nfrom runtime signals.\nKeep adaptive behavior measured against a known baseline.\n\n## Do Not Use This When\n\nDo not use this skill when the application is not instrumented yet. Start with\n`nemo-relay-instrument-calls` or `nemo-relay-get-started` first.\n\n## Default Guidance\n\n- Observe first, compare against a baseline, then enable one behavior change at\n  a time.\n- Use the adaptive plugin component rather than inventing separate tuning logic\n  or hand-registering adaptive behavior at every call site.\n- Start with in-memory state and telemetry-only behavior for local development.\n- Move to persistent state only when learned signals must survive restarts or be\n  shared across workers.\n- Add active behavior only after representative runtime events show what should\n  change.\n\n## Embedded Adaptive Model\n\n- Adaptive behavior is configured through the first-party plugin component with\n  kind `adaptive`.\n- Adaptive requires existing NeMo Relay scopes and at least one relevant\n  managed tool or LLM lifecycle event stream because it learns from runtime\n  signals.\n- Main configuration areas are state, telemetry, adaptive hints, tool\n  parallelism, Adaptive Cache Governor (ACG), and rollout policy.\n- State backends are `in_memory` and `redis`.\n- Tool-parallelism modes are `observe_only`, `inject_hints`, and `schedule`.\n- Adaptive Cache Governor providers are `passthrough`, `anthropic`, and\n  `openai`; omit ACG until prompt-cache planning is needed.\n- Helper APIs exist in Rust `nemo_relay_adaptive`, Python `nemo_relay.adaptive`,\n  and Node.js `nemo-relay-node\u002Fadaptive`. Go and raw FFI are\n  source-first or advanced surfaces.\n\n## Default Path\n\nUse this rollout sequence:\n\n1. Confirm the app emits scope events and the managed tool or LLM events needed\n   for the behavior being evaluated. Do not require both call types when the\n   workflow uses only one.\n2. Capture a baseline for the workflow you want to improve.\n3. Enable adaptive telemetry with in-memory state.\n4. Read `references\u002Fconfig.md` when exact plugin configuration fields are needed.\n5. Run representative traffic and inspect reports or runtime events.\n6. If configuration validation fails or expected events are absent, return the\n   diagnostics and stop. Keep the last known working configuration active.\n7. Before enabling scheduling, verify tool idempotency and race behavior. Before\n   enabling ACG, verify that provider request payloads are stable.\n8. Enable the smallest behavior change in config.\n9. Read `references\u002Fhints.md` when application logic consumes adaptive hints,\n   tool-parallelism guidance, or ACG diagnostics.\n10. Compare results against the baseline. If latency, correctness, or failure\n    rate regresses, restore the last known working configuration and retain the\n    sanitized diagnostics for review.\n\n## Failure Modes To Avoid\n\n- Do not enable scheduling before tool idempotency and race behavior are known.\n- Do not enable prompt-cache planning before provider payloads are stable.\n- Do not treat adaptive hints as mandatory instructions unless the consuming\n  path explicitly defines that contract.\n- Do not use environment variables as the primary adaptive configuration model.\n- Do not tune from a single run or unrepresentative traffic.\n- Do not suppress or replace original tool and model errors.\n- Do not add retries until the call owner defines their safety.\n- Revert adaptive behavior when it increases the failure rate.\n\n## Load A Reference When\n\n- You need the exact adaptive config shape -> `references\u002Fconfig.md`\n- You need to consume adaptive hints or scheduling guidance in app logic ->\n  `references\u002Fhints.md`\n\n## Use Another Skill When\n\n- You need to build reusable plugin behavior instead of configuring the built-in\n  adaptive component -> `nemo-relay-plugin-build`\n\n## Related Skills\n\n- `nemo-relay-get-started`\n- `nemo-relay-instrument-calls`\n- `nemo-relay-plugin-observability`\n- `nemo-relay-plugin-build`\n",{"data":53,"body":56},{"name":4,"description":6,"license":26,"metadata":54},{"author":55},"NVIDIA Corporation and Affiliates",{"type":57,"children":58},"root",[59,68,75,81,87,109,115,145,151,282,288,293,362,368,411,417,440,446,460,466],{"type":60,"tag":61,"props":62,"children":64},"element","h1",{"id":63},"tune-adaptive-plugin-behavior",[65],{"type":66,"value":67},"text","Tune Adaptive Plugin Behavior",{"type":60,"tag":69,"props":70,"children":72},"h2",{"id":71},"use-this-when",[73],{"type":66,"value":74},"Use This When",{"type":60,"tag":76,"props":77,"children":78},"p",{},[79],{"type":66,"value":80},"Use this skill when a user has baseline NeMo Relay instrumentation and wants to\nimprove latency, parallelism, prompt-cache behavior, or model-request behavior\nfrom runtime signals.\nKeep adaptive behavior measured against a known baseline.",{"type":60,"tag":69,"props":82,"children":84},{"id":83},"do-not-use-this-when",[85],{"type":66,"value":86},"Do Not Use This When",{"type":60,"tag":76,"props":88,"children":89},{},[90,92,99,101,107],{"type":66,"value":91},"Do not use this skill when the application is not instrumented yet. Start with\n",{"type":60,"tag":93,"props":94,"children":96},"code",{"className":95},[],[97],{"type":66,"value":98},"nemo-relay-instrument-calls",{"type":66,"value":100}," or ",{"type":60,"tag":93,"props":102,"children":104},{"className":103},[],[105],{"type":66,"value":106},"nemo-relay-get-started",{"type":66,"value":108}," first.",{"type":60,"tag":69,"props":110,"children":112},{"id":111},"default-guidance",[113],{"type":66,"value":114},"Default Guidance",{"type":60,"tag":116,"props":117,"children":118},"ul",{},[119,125,130,135,140],{"type":60,"tag":120,"props":121,"children":122},"li",{},[123],{"type":66,"value":124},"Observe first, compare against a baseline, then enable one behavior change at\na time.",{"type":60,"tag":120,"props":126,"children":127},{},[128],{"type":66,"value":129},"Use the adaptive plugin component rather than inventing separate tuning logic\nor hand-registering adaptive behavior at every call site.",{"type":60,"tag":120,"props":131,"children":132},{},[133],{"type":66,"value":134},"Start with in-memory state and telemetry-only behavior for local development.",{"type":60,"tag":120,"props":136,"children":137},{},[138],{"type":66,"value":139},"Move to persistent state only when learned signals must survive restarts or be\nshared across workers.",{"type":60,"tag":120,"props":141,"children":142},{},[143],{"type":66,"value":144},"Add active behavior only after representative runtime events show what should\nchange.",{"type":60,"tag":69,"props":146,"children":148},{"id":147},"embedded-adaptive-model",[149],{"type":66,"value":150},"Embedded Adaptive Model",{"type":60,"tag":116,"props":152,"children":153},{},[154,167,172,177,197,225,253],{"type":60,"tag":120,"props":155,"children":156},{},[157,159,165],{"type":66,"value":158},"Adaptive behavior is configured through the first-party plugin component with\nkind ",{"type":60,"tag":93,"props":160,"children":162},{"className":161},[],[163],{"type":66,"value":164},"adaptive",{"type":66,"value":166},".",{"type":60,"tag":120,"props":168,"children":169},{},[170],{"type":66,"value":171},"Adaptive requires existing NeMo Relay scopes and at least one relevant\nmanaged tool or LLM lifecycle event stream because it learns from runtime\nsignals.",{"type":60,"tag":120,"props":173,"children":174},{},[175],{"type":66,"value":176},"Main configuration areas are state, telemetry, adaptive hints, tool\nparallelism, Adaptive Cache Governor (ACG), and rollout policy.",{"type":60,"tag":120,"props":178,"children":179},{},[180,182,188,190,196],{"type":66,"value":181},"State backends are ",{"type":60,"tag":93,"props":183,"children":185},{"className":184},[],[186],{"type":66,"value":187},"in_memory",{"type":66,"value":189}," and ",{"type":60,"tag":93,"props":191,"children":193},{"className":192},[],[194],{"type":66,"value":195},"redis",{"type":66,"value":166},{"type":60,"tag":120,"props":198,"children":199},{},[200,202,208,210,216,218,224],{"type":66,"value":201},"Tool-parallelism modes are ",{"type":60,"tag":93,"props":203,"children":205},{"className":204},[],[206],{"type":66,"value":207},"observe_only",{"type":66,"value":209},", ",{"type":60,"tag":93,"props":211,"children":213},{"className":212},[],[214],{"type":66,"value":215},"inject_hints",{"type":66,"value":217},", and ",{"type":60,"tag":93,"props":219,"children":221},{"className":220},[],[222],{"type":66,"value":223},"schedule",{"type":66,"value":166},{"type":60,"tag":120,"props":226,"children":227},{},[228,230,236,237,243,245,251],{"type":66,"value":229},"Adaptive Cache Governor providers are ",{"type":60,"tag":93,"props":231,"children":233},{"className":232},[],[234],{"type":66,"value":235},"passthrough",{"type":66,"value":209},{"type":60,"tag":93,"props":238,"children":240},{"className":239},[],[241],{"type":66,"value":242},"anthropic",{"type":66,"value":244},", and\n",{"type":60,"tag":93,"props":246,"children":248},{"className":247},[],[249],{"type":66,"value":250},"openai",{"type":66,"value":252},"; omit ACG until prompt-cache planning is needed.",{"type":60,"tag":120,"props":254,"children":255},{},[256,258,264,266,272,274,280],{"type":66,"value":257},"Helper APIs exist in Rust ",{"type":60,"tag":93,"props":259,"children":261},{"className":260},[],[262],{"type":66,"value":263},"nemo_relay_adaptive",{"type":66,"value":265},", Python ",{"type":60,"tag":93,"props":267,"children":269},{"className":268},[],[270],{"type":66,"value":271},"nemo_relay.adaptive",{"type":66,"value":273},",\nand Node.js ",{"type":60,"tag":93,"props":275,"children":277},{"className":276},[],[278],{"type":66,"value":279},"nemo-relay-node\u002Fadaptive",{"type":66,"value":281},". Go and raw FFI are\nsource-first or advanced surfaces.",{"type":60,"tag":69,"props":283,"children":285},{"id":284},"default-path",[286],{"type":66,"value":287},"Default Path",{"type":60,"tag":76,"props":289,"children":290},{},[291],{"type":66,"value":292},"Use this rollout sequence:",{"type":60,"tag":294,"props":295,"children":296},"ol",{},[297,302,307,312,325,330,335,340,345,357],{"type":60,"tag":120,"props":298,"children":299},{},[300],{"type":66,"value":301},"Confirm the app emits scope events and the managed tool or LLM events needed\nfor the behavior being evaluated. Do not require both call types when the\nworkflow uses only one.",{"type":60,"tag":120,"props":303,"children":304},{},[305],{"type":66,"value":306},"Capture a baseline for the workflow you want to improve.",{"type":60,"tag":120,"props":308,"children":309},{},[310],{"type":66,"value":311},"Enable adaptive telemetry with in-memory state.",{"type":60,"tag":120,"props":313,"children":314},{},[315,317,323],{"type":66,"value":316},"Read ",{"type":60,"tag":93,"props":318,"children":320},{"className":319},[],[321],{"type":66,"value":322},"references\u002Fconfig.md",{"type":66,"value":324}," when exact plugin configuration fields are needed.",{"type":60,"tag":120,"props":326,"children":327},{},[328],{"type":66,"value":329},"Run representative traffic and inspect reports or runtime events.",{"type":60,"tag":120,"props":331,"children":332},{},[333],{"type":66,"value":334},"If configuration validation fails or expected events are absent, return the\ndiagnostics and stop. Keep the last known working configuration active.",{"type":60,"tag":120,"props":336,"children":337},{},[338],{"type":66,"value":339},"Before enabling scheduling, verify tool idempotency and race behavior. Before\nenabling ACG, verify that provider request payloads are stable.",{"type":60,"tag":120,"props":341,"children":342},{},[343],{"type":66,"value":344},"Enable the smallest behavior change in config.",{"type":60,"tag":120,"props":346,"children":347},{},[348,349,355],{"type":66,"value":316},{"type":60,"tag":93,"props":350,"children":352},{"className":351},[],[353],{"type":66,"value":354},"references\u002Fhints.md",{"type":66,"value":356}," when application logic consumes adaptive hints,\ntool-parallelism guidance, or ACG diagnostics.",{"type":60,"tag":120,"props":358,"children":359},{},[360],{"type":66,"value":361},"Compare results against the baseline. If latency, correctness, or failure\nrate regresses, restore the last known working configuration and retain the\nsanitized diagnostics for review.",{"type":60,"tag":69,"props":363,"children":365},{"id":364},"failure-modes-to-avoid",[366],{"type":66,"value":367},"Failure Modes To Avoid",{"type":60,"tag":116,"props":369,"children":370},{},[371,376,381,386,391,396,401,406],{"type":60,"tag":120,"props":372,"children":373},{},[374],{"type":66,"value":375},"Do not enable scheduling before tool idempotency and race behavior are known.",{"type":60,"tag":120,"props":377,"children":378},{},[379],{"type":66,"value":380},"Do not enable prompt-cache planning before provider payloads are stable.",{"type":60,"tag":120,"props":382,"children":383},{},[384],{"type":66,"value":385},"Do not treat adaptive hints as mandatory instructions unless the consuming\npath explicitly defines that contract.",{"type":60,"tag":120,"props":387,"children":388},{},[389],{"type":66,"value":390},"Do not use environment variables as the primary adaptive configuration model.",{"type":60,"tag":120,"props":392,"children":393},{},[394],{"type":66,"value":395},"Do not tune from a single run or unrepresentative traffic.",{"type":60,"tag":120,"props":397,"children":398},{},[399],{"type":66,"value":400},"Do not suppress or replace original tool and model errors.",{"type":60,"tag":120,"props":402,"children":403},{},[404],{"type":66,"value":405},"Do not add retries until the call owner defines their safety.",{"type":60,"tag":120,"props":407,"children":408},{},[409],{"type":66,"value":410},"Revert adaptive behavior when it increases the failure rate.",{"type":60,"tag":69,"props":412,"children":414},{"id":413},"load-a-reference-when",[415],{"type":66,"value":416},"Load A Reference When",{"type":60,"tag":116,"props":418,"children":419},{},[420,430],{"type":60,"tag":120,"props":421,"children":422},{},[423,425],{"type":66,"value":424},"You need the exact adaptive config shape -> ",{"type":60,"tag":93,"props":426,"children":428},{"className":427},[],[429],{"type":66,"value":322},{"type":60,"tag":120,"props":431,"children":432},{},[433,435],{"type":66,"value":434},"You need to consume adaptive hints or scheduling guidance in app logic ->\n",{"type":60,"tag":93,"props":436,"children":438},{"className":437},[],[439],{"type":66,"value":354},{"type":60,"tag":69,"props":441,"children":443},{"id":442},"use-another-skill-when",[444],{"type":66,"value":445},"Use Another Skill When",{"type":60,"tag":116,"props":447,"children":448},{},[449],{"type":60,"tag":120,"props":450,"children":451},{},[452,454],{"type":66,"value":453},"You need to build reusable plugin behavior instead of configuring the built-in\nadaptive component -> ",{"type":60,"tag":93,"props":455,"children":457},{"className":456},[],[458],{"type":66,"value":459},"nemo-relay-plugin-build",{"type":60,"tag":69,"props":461,"children":463},{"id":462},"related-skills",[464],{"type":66,"value":465},"Related Skills",{"type":60,"tag":116,"props":467,"children":468},{},[469,477,485,494],{"type":60,"tag":120,"props":470,"children":471},{},[472],{"type":60,"tag":93,"props":473,"children":475},{"className":474},[],[476],{"type":66,"value":106},{"type":60,"tag":120,"props":478,"children":479},{},[480],{"type":60,"tag":93,"props":481,"children":483},{"className":482},[],[484],{"type":66,"value":98},{"type":60,"tag":120,"props":486,"children":487},{},[488],{"type":60,"tag":93,"props":489,"children":491},{"className":490},[],[492],{"type":66,"value":493},"nemo-relay-plugin-observability",{"type":60,"tag":120,"props":495,"children":496},{},[497],{"type":60,"tag":93,"props":498,"children":500},{"className":499},[],[501],{"type":66,"value":459},{"items":503,"total":612},[504,518,534,553,567,580,595],{"slug":505,"name":505,"fn":506,"description":507,"org":508,"tags":509,"stars":23,"repoUrl":24,"updatedAt":517},"nemo-relay-debug-runtime-integration","debug NeMo Relay runtime integrations","Use this skill when NeMo Relay is installed or imported but application-side runtime behavior is missing or incorrect, including load failures, inactive scopes, missing events, and plugin or adaptive wiring problems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[510,513,514,516],{"name":511,"slug":512,"type":15},"Debugging","debugging",{"name":18,"slug":19,"type":15},{"name":515,"slug":39,"type":15},"Middleware",{"name":9,"slug":8,"type":15},"2026-07-17T05:30:27.286964",{"slug":106,"name":106,"fn":519,"description":520,"org":521,"tags":522,"stars":23,"repoUrl":24,"updatedAt":533},"get started with NeMo Relay","Use this skill when first-time NeMo Relay users want to try Relay, choose the least-complex supported quick start, or verify initial value through the CLI, a maintained integration, or direct Python, Node.js, or Rust instrumentation before production setup.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[523,526,527,530],{"name":524,"slug":525,"type":15},"CLI","cli",{"name":9,"slug":8,"type":15},{"name":528,"slug":529,"type":15},"Onboarding","onboarding",{"name":531,"slug":532,"type":15},"Python","python","2026-07-23T05:43:39.488827",{"slug":535,"name":535,"fn":536,"description":537,"org":538,"tags":539,"stars":23,"repoUrl":24,"updatedAt":552},"nemo-relay-install","install NeMo Relay for various environments","Use this skill when choosing or running NeMo Relay installation for the CLI, Python, Node.js, Rust, OpenClaw, Hermes, or maintained framework integrations before runtime configuration or quick-start setup.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[540,541,544,547,548,549],{"name":524,"slug":525,"type":15},{"name":542,"slug":543,"type":15},"Deployment","deployment",{"name":545,"slug":546,"type":15},"Node.js","nodejs",{"name":9,"slug":8,"type":15},{"name":531,"slug":532,"type":15},{"name":550,"slug":551,"type":15},"Rust","rust","2026-07-17T05:30:31.443244",{"slug":98,"name":98,"fn":554,"description":555,"org":556,"tags":557,"stars":23,"repoUrl":24,"updatedAt":566},"instrument LLM calls with NeMo Relay","Use this skill when an application owns tool or LLM\u002Fprovider call sites and needs to wrap them with NeMo Relay scopes and managed execution APIs for lifecycle events, middleware, or guardrails.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[558,561,564,565],{"name":559,"slug":560,"type":15},"Automation","automation",{"name":562,"slug":563,"type":15},"LLM","llm",{"name":515,"slug":39,"type":15},{"name":9,"slug":8,"type":15},"2026-07-17T05:30:29.31214",{"slug":568,"name":568,"fn":569,"description":570,"org":571,"tags":572,"stars":23,"repoUrl":24,"updatedAt":579},"nemo-relay-instrument-context-isolation","isolate NeMo Relay execution contexts","Use this skill when concurrent requests, async tasks, threads, workers, goroutines, or agents need independent NeMo Relay scope stacks and correct ancestry propagation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[573,576,577,578],{"name":574,"slug":575,"type":15},"Concurrency","concurrency",{"name":18,"slug":19,"type":15},{"name":515,"slug":39,"type":15},{"name":9,"slug":8,"type":15},"2026-07-17T05:30:33.080543",{"slug":581,"name":581,"fn":582,"description":583,"org":584,"tags":585,"stars":23,"repoUrl":24,"updatedAt":594},"nemo-relay-instrument-typed-wrappers","instrument NeMo Relay typed wrappers","Use this skill when adding NeMo Relay typed wrappers, domain types, or provider codecs while preserving JSON middleware semantics and caller-visible behavior.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[586,589,592,593],{"name":587,"slug":588,"type":15},"API Development","api-development",{"name":590,"slug":591,"type":15},"JSON","json",{"name":515,"slug":39,"type":15},{"name":9,"slug":8,"type":15},"2026-07-23T05:43:40.456621",{"slug":596,"name":596,"fn":597,"description":598,"org":599,"tags":600,"stars":23,"repoUrl":24,"updatedAt":611},"nemo-relay-migrate-from-flow","migrate applications from NeMo Flow to Relay","Use this skill when migrating applications, examples, integrations, documentation, manifests, or repository code from NeMo Flow to NeMo Relay across Python, Rust, Node.js, Go, C FFI, CLI, configuration, and observability surfaces.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[601,604,607,608,609,610],{"name":602,"slug":603,"type":15},"Go","go",{"name":605,"slug":606,"type":15},"Migration","migration",{"name":545,"slug":546,"type":15},{"name":9,"slug":8,"type":15},{"name":531,"slug":532,"type":15},{"name":550,"slug":551,"type":15},"2026-07-17T05:30:28.259456",10,{"items":614,"total":763},[615,633,647,658,670,682,695,707,720,731,745,754],{"slug":616,"name":616,"fn":617,"description":618,"org":619,"tags":620,"stars":630,"repoUrl":631,"updatedAt":632},"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},[621,624,627],{"name":622,"slug":623,"type":15},"Documentation","documentation",{"name":625,"slug":626,"type":15},"MCP","mcp",{"name":628,"slug":629,"type":15},"Search","search",21777,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNemoClaw","2026-07-20T06:00:01.461044",{"slug":634,"name":634,"fn":635,"description":636,"org":637,"tags":638,"stars":644,"repoUrl":645,"updatedAt":646},"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},[639,642,643],{"name":640,"slug":641,"type":15},"Containers","containers",{"name":542,"slug":543,"type":15},{"name":531,"slug":532,"type":15},17049,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FMegatron-LM","2026-07-27T06:06:11.249662",{"slug":648,"name":648,"fn":649,"description":650,"org":651,"tags":652,"stars":644,"repoUrl":645,"updatedAt":657},"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},[653,656],{"name":654,"slug":655,"type":15},"CI\u002FCD","ci-cd",{"name":542,"slug":543,"type":15},"2026-07-14T05:25:59.97109",{"slug":659,"name":659,"fn":660,"description":661,"org":662,"tags":663,"stars":644,"repoUrl":645,"updatedAt":669},"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},[664,665,666],{"name":654,"slug":655,"type":15},{"name":542,"slug":543,"type":15},{"name":667,"slug":668,"type":15},"GitHub","github","2026-07-27T06:06:12.278222",{"slug":671,"name":671,"fn":672,"description":673,"org":674,"tags":675,"stars":644,"repoUrl":645,"updatedAt":681},"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},[676,677,678],{"name":511,"slug":512,"type":15},{"name":667,"slug":668,"type":15},{"name":679,"slug":680,"type":15},"Triage","triage","2026-07-14T05:25:57.442089",{"slug":683,"name":683,"fn":684,"description":685,"org":686,"tags":687,"stars":644,"repoUrl":645,"updatedAt":694},"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},[688,691],{"name":689,"slug":690,"type":15},"Best Practices","best-practices",{"name":692,"slug":693,"type":15},"Code Analysis","code-analysis","2026-07-14T05:25:56.18433",{"slug":696,"name":696,"fn":697,"description":698,"org":699,"tags":700,"stars":644,"repoUrl":645,"updatedAt":706},"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},[701,704,705],{"name":702,"slug":703,"type":15},"Machine Learning","machine-learning",{"name":605,"slug":606,"type":15},{"name":9,"slug":8,"type":15},"2026-07-17T06:07:11.777011",{"slug":708,"name":708,"fn":709,"description":710,"org":711,"tags":712,"stars":644,"repoUrl":645,"updatedAt":719},"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},[713,716],{"name":714,"slug":715,"type":15},"QA","qa",{"name":717,"slug":718,"type":15},"Testing","testing","2026-07-14T05:25:53.673039",{"slug":721,"name":721,"fn":722,"description":723,"org":724,"tags":725,"stars":644,"repoUrl":645,"updatedAt":730},"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},[726,727],{"name":542,"slug":543,"type":15},{"name":728,"slug":729,"type":15},"Infrastructure","infrastructure","2026-07-14T05:25:49.362534",{"slug":732,"name":732,"fn":733,"description":734,"org":735,"tags":736,"stars":644,"repoUrl":645,"updatedAt":744},"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},[737,740,741],{"name":738,"slug":739,"type":15},"Code Review","code-review",{"name":667,"slug":668,"type":15},{"name":742,"slug":743,"type":15},"Pull Requests","pull-requests","2026-07-14T05:26:01.226578",{"slug":746,"name":746,"fn":747,"description":748,"org":749,"tags":750,"stars":644,"repoUrl":645,"updatedAt":753},"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},[751,752],{"name":714,"slug":715,"type":15},{"name":717,"slug":718,"type":15},"2026-07-14T05:25:54.928983",{"slug":755,"name":755,"fn":756,"description":757,"org":758,"tags":759,"stars":644,"repoUrl":645,"updatedAt":762},"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},[760,761],{"name":559,"slug":560,"type":15},{"name":654,"slug":655,"type":15},"2026-07-30T05:29:03.275638",496]