Agent skill · NVIDIA
nemo-relay-plugin-build
Use this skill when building or packaging reusable NeMo Relay runtime behavior as an embedded configuration component or a manifest-backed `rust_dynamic` native or `worker` gRPC plugin, with deterministic validation and rollback-safe registration.
What it needs
About 6k tokens when loaded.
What this skill does
Build a Plugin Use this skill when a user wants to package reusable NeMo Relay runtime behavior behind plugin configuration. Keep reusable plugin behavior separate from one-off application startup code. Use This When Use this skill when the behavior should be activated by shared config and reused across applications, teams, or process startup paths. Common cases: Register subscribers, guardrails, intercepts, or a small bundle of related runtime behavior. Validate operator-supplied config before changing runtime behavior. Give reusable behavior a stable plugin kind and activation lifecycle. Package behavior that should be enabled, disabled, or rolled out through plugin config rather than repeated application startup code. Do Not Use This When Do not build a plugin when a narrower NeMo Relay surface is enough: One request or tenant needs temporary behavior -> use scope-local middleware. The user only needs first-time scopes, tool calls, or LLM calls -> nemo-relay-instrument-calls. The user only needs to choose an exporter path -> nemo-relay-plugin-observability. The behavior depends on live callables, provider clients, file handles, credentials, or framework objects inside config. Choose A Delivery Model Choose the delivery model before designing config or registration: Embedded component: Use the shared plugin document when behavior ships with the Relay host application. Follow the embedded component model below. Discoverable dynamic package: Use a relay-plugin.toml manifest when the plugin ships independently of the host. Use rustdynamic for a trusted in-process native Rust library, or worker for a local grpc-v1 worker. Read the public native dynamic-plugin or gRPC worker guide before designing the package boundary. Do not reproduce native ABI or worker-protocol details from memory. Native plugins are trusted C-ABI extensions that run in the Relay process and are not sandboxed. Worker plugins provide process isolation, not a security sandbox. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/nemo-relay-plugin-build