Menu
Maintain or extend the NeMo Relay adaptive surface across config, plugins, docs, and bindings; use this when users still say optimizer
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | maintain-optimizer |
| description | Maintain or extend the NeMo Relay adaptive surface across config, plugins, docs, and bindings; use this when users still say optimizer |
| author | NVIDIA Corporation and Affiliates |
| license | Apache-2.0 |
Use karpathy-guidelines alongside this skill for implementation or review
work. Keep changes scoped, surface assumptions, and define focused validation
before editing.
Use this skill when changing adaptive config schema, built-in sections, shared plugin lifecycle, plugin registration, or binding-native helper APIs.
The stable adaptive boundary is the config document plus the shared plugin lifecycle:
There is no separate public adaptive runtime handle.
See docs/plugins/adaptive/configuration.md and
docs/about/concepts/plugins.md.
crates/adaptivepython/nemo_relay/adaptive.py and
python/nemo_relay/plugin.pygo/nemo_relay/adaptive plus shared plugin
helpers in go/nemo_relaydocs/plugins/adaptive/configuration.mddocs/plugins/adaptive/about.mddocs/plugins/adaptive/acg.mddocs/plugins/adaptive/adaptive-hints.mddocs/build-plugins/basic-guide.mddocs/build-plugins/validate-configuration.mddocs/about/concepts/plugins.mdvalidate-changeCompare NeMo Relay release branches and draft or update the documentation-site release notes. Use when preparing a release-notes update under docs/about-nemo-relay/release-notes, reviewing release-to-release changes, or gathering evidence for a current release summary.
Contribute documentation or example changes that stay aligned with NeMo Relay public behavior
Build and package reusable NeMo Relay runtime behavior as a config-activated plugin with validation and rollback-safe registration
Add or change a public NeMo Relay API surface across the core runtime and every affected binding
Maintain or extend NeMo Relay observability surfaces across ATIF, OpenTelemetry, and OpenInference
Maintain NeMo Relay package metadata, module paths, generated artifacts, and release-facing build surfaces