mcpbeat

Maintain Optimizer

nvidia/maintain-optimizer

Maintain or extend the NeMo Relay adaptive surface across config, plugins, docs, and bindings; use this when users still say optimizer

571 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
102
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/NVIDIA/NeMo-Relay --skill maintain-optimizer

The instruction itself

7 sections, as written by the author

Maintain Adaptive Surfaces

Companion Guidance

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.

Public Boundary

The stable adaptive boundary is the config document plus the shared plugin

lifecycle:

  • Config types and policies
  • Built-in adaptive section helpers
  • Plugin registration and composition
  • Plugin lifecycle
  • Reports and diagnostics

There is no separate public adaptive runtime handle.

See docs/plugins/adaptive/configuration.md and

docs/about/concepts/plugins.md.

Keep In Sync

  • crates/adaptive
  • Shared plugin behavior in core and bindings
  • Python adaptive/plugin wrappers in python/nemo_relay/adaptive.py and

python/nemo_relay/plugin.py

  • Go adaptive helpers under go/nemo_relay/adaptive plus shared plugin

helpers in go/nemo_relay

  • Node.js adaptive helpers and plugin wrappers
  • Docs and examples that show canonical config shapes

Checklist

  • [ ] Dynamic config shape still matches the documented canonical model
  • [ ] Typed helper constructors still map cleanly to the same config document
  • [ ] Plugin lifecycle is consistent across languages
  • [ ] Plugin context surfaces remain aligned
  • [ ] Validation/report behavior remains documented and tested
  • [ ] Any new component kind has docs, examples, and binding coverage

Validation

  • Run adaptive-focused Rust tests
  • Run binding tests for every changed adaptive or plugin surface
  • Update adaptive docs and any examples in the same branch

References

  • docs/plugins/adaptive/configuration.md
  • docs/plugins/adaptive/about.md
  • docs/plugins/adaptive/acg.md
  • docs/plugins/adaptive/adaptive-hints.md
  • docs/build-plugins/basic-guide.md
  • docs/build-plugins/validate-configuration.md
  • docs/about/concepts/plugins.md
  • validate-change

How to use it

Copy the folder

Take nvidia/maintain-optimizer from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.