agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/NeMo-Relay/.agents/skills/maintain-optimizer/SKILL.md

maintain-optimizer

Skill238 starsChanged 2 months agoApache-2.0View on GitHub

Change NeMo Relay adaptive configuration, built-in adaptive components, reports, or binding helpers; also use when the task calls this surface optimizer. Do not use for generic plugin changes.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when changing adaptive config schema, built-in sections, shared plugin lifecycle, plugin registration, or binding-native …

    line 10
  2. Distinctive:

    Run adaptive-focused Rust tests

    line 52
  3. Distinctive:

    Run binding tests for every changed adaptive or plugin surface

    line 53
  4. Distinctive:

    Update adaptive docs and any examples in the same branch

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Maintain Adaptive Surfaces

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/configure-plugins/adaptive/configuration.mdx and docs/configure-plugins/about.mdx.

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/configure-plugins/adaptive/configuration.mdx
  • docs/configure-plugins/adaptive/about.mdx
  • docs/configure-plugins/adaptive/acg.mdx
  • docs/configure-plugins/adaptive/adaptive-hints.mdx
  • docs/build-plugins/about.mdx
  • docs/build-plugins/configuration-and-validation.mdx

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free