Agent skill · NVIDIA
nemo-relay-install
Use this skill when choosing or running NeMo Relay installation for the CLI, Python, Node.js, Rust, OpenClaw, Hermes, or maintained framework integrations before runtime configuration or quick-start setup.
What it needs
About 4k tokens when loaded.
What this skill does
Install NeMo Relay Choose the package or executable from the user's desired outcome. Stop after installation and basic availability checks. Do not configure runtime behavior, write plugins.toml, create scopes, register middleware, or build a first app example from this skill. Keep installation separate from first-use instrumentation. Choose The Install Path If the user asks to install NeMo Relay but does not identify a target or desired outcome, ask one short clarifying question before giving commands: Which install path do you want: CLI for coding-agent/local gateway use, language package for a Python/Node.js/Rust app, or framework integration for LangChain, LangGraph, Deep Agents, OpenClaw, or Hermes? Do not ask when the user already names a CLI, language, framework, harness, source checkout, or target project file such as pyproject.toml, package.json, or Cargo.toml. Use this order from least to most application-specific: 1. CLI for a generic "try Relay" request, a temporary coding-agent run, the local gateway, or explicit persistent host-plugin setup. Read CLI Installation. 2. Maintained integration when the user already uses OpenClaw, Hermes, LangChain, LangGraph, or Deep Agents. Read Maintained Integration Installation. 3. Language package when a Python, Node.js, or Rust application directly owns its tool or model call sites. Read Language Package Installation. 4. Source checkout only for contributors or unpublished changes. Follow the repository development guide instead of published package commands. For "try Relay" requests, default to the CLI and temporary transparent run. Do not make persistent host-plugin installation the default. Protect Codex Desktop Continuity Before persistent Codex installation, determine whether the user is operating from Codex Desktop. Persistent nemo-relay install codex changes the active Codex provider and can make the current or older Desktop threads appear missing after restart because of an upstream provider-filtering bug. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/nemo-relay-install