Maintain NeMo Relay dynamic plugin loaders, manifests, Rust native SDKs, gRPC worker protocol, Python worker SDK, docs, tests, and release workflow coverage
NVIDIA/NeMo-Relay
SkillsMP has collected 28 skills from NVIDIA/NeMo-Relay. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 28
- GitHub stars
- 132
- GitHub forks
- 63
Skills in this repository
Showing 28 of 28 collected skills.
Use this skill when assessing, extending, or implementing NeMo Relay support in an agent harness or agent framework, including coding agents and orchestration runtimes, when the host lacks Relay support or an existing integration needs deeper coverage. It…
Add or change a public NeMo Relay API surface across the core runtime and every affected binding
Add a new guardrail or intercept type to the NeMo Relay middleware pipeline
Contribute documentation or example changes that stay aligned with NeMo Relay public behavior
Contribute a new or updated third-party framework integration for NeMo Relay
Maintain or extend NeMo Relay observability surfaces across ATIF and typed OpenTelemetry projections
Choose and run the right NeMo Relay validation matrix for a change instead of using one fixed test list
Prepare, open, create, publish, update, or edit a NeMo Relay pull request or PR body with the right tests, docs, contributor hygiene, and repository pull request template
Use this skill when choosing or running NeMo Relay installation for the CLI, Python, Node.js, Rust, OpenClaw, or maintained framework integrations, or when explaining Hermes Agent's built-in Relay integration.
Build and test the NeMo Relay Python binding and worker plugin SDK; use for python/nemo_relay, python/plugin, or crates/python changes
Build and test NeMo Relay Rust core, adaptive, and dynamic plugin crates; use for crates/core, crates/adaptive, crates/plugin, crates/worker, crates/worker-proto, crates/types, or shared runtime changes
Use this skill when choosing or configuring NeMo Relay 0.6 or 0.7 observability through the built-in plugin, subscribers, or exporters, including raw ATOF events, ATIF trajectories, OpenTelemetry, OpenInference, or custom event handling.
Review documentation, examples, and docs-heavy changes for NVIDIA technical writing style, terminology, and repo accuracy
Prepare a NeMo Relay code freeze by creating the release branch, updating nightly alpha branch config, bumping main to the next version, and opening the required PR
Use this skill when adding NeMo Relay typed wrappers, domain types, or provider codecs while preserving JSON middleware semantics and caller-visible behavior.
Compare 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…
Maintain or extend the NeMo Relay adaptive surface across config, plugins, docs, and bindings; use this when users still say optimizer
Maintain NeMo Relay package metadata, module paths, generated artifacts, and release-facing build surfaces
Perform a coordinated repository, package, crate, module, or symbol rename across NeMo Relay
Update the NeMo Relay project version across Cargo, Node, and lockfiles without leaving release surfaces out of sync
Maintain and review NeMo Relay GitHub Actions workflows with explicit per-job permissions, pinned action SHAs, deterministic caching, reusable workflow permission boundaries, and local validation
Contribute a new NeMo Relay public API surface safely, with binding parity and docs in mind
Make a small, reviewable NeMo Relay bug fix without widening scope unnecessarily
Build and test the NeMo Relay FFI surface; use this for crates/ffi changes, header generation, or ABI-facing validation
Build and test the NeMo Relay Go binding; use this for go/nemo_relay changes or Go-facing integration checks
Build and test the NeMo Relay Node.js binding; use this for crates/node changes or Node-facing integration checks
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.