Nemo Relay Install
NVIDIA/NeMo-Relay
A skill your agent uses 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…
A skill your agent uses when choosing or running NeMo Relay installation for the CLI, Python, Node.js, Rust, OpenClaw, Hermes, or maintained framework integrations before runtime configuration or…
Install Nemo Relay Install
$ npx skills add NVIDIA/skills --skill nemo-relay-install -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/skills nemo-relay-install --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/nemo-relay-install .claude/skills/nemo-relay-install && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "nemo-relay-install" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/nemo-relay-install into .claude/skills/nemo-relay-install/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-install", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NVIDIA/skills/tree/main/skills/nemo-relay-installType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NVIDIA/skills --skill nemo-relay-install -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/skills nemo-relay-install --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/nemo-relay-install .agents/skills/nemo-relay-install && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nemo-relay-install" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/nemo-relay-install into .agents/skills/nemo-relay-install/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-install", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/skills --skill nemo-relay-install -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/skills nemo-relay-install --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/nemo-relay-install .cursor/skills/nemo-relay-install && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "nemo-relay-install" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/nemo-relay-install into .cursor/skills/nemo-relay-install/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-install", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NVIDIA/skills.git --path skills/nemo-relay-install--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NVIDIA/skills --skill nemo-relay-install -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/skills nemo-relay-install --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/nemo-relay-install .gemini/skills/nemo-relay-install && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "nemo-relay-install" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/nemo-relay-install into .gemini/skills/nemo-relay-install/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-install", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NVIDIA/skills nemo-relay-installInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NVIDIA/skills --skill nemo-relay-install -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/nemo-relay-install .github/skills/nemo-relay-install && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "nemo-relay-install" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/nemo-relay-install into .github/skills/nemo-relay-install/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-install", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/skills --skill nemo-relay-install -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA/skills nemo-relay-install --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/nemo-relay-install .opencode/skills/nemo-relay-install && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "nemo-relay-install" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/nemo-relay-install into .opencode/skills/nemo-relay-install/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-install", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
nemo-relay-install- GitHub stars
- 3.5k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 851 words
- Files
- 9 (incl. references, assets)
- Skills in repo
- 380
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when choosing or running NeMo Relay installation for the CLI, Python, Node.js, Rust, OpenClaw, Hermes, or maintained framework integrations before runtime configuration or…
- Works in 4 steps: CLI for a generic "try Relay" request, a… → Maintained integration when the user… → Language package when a Python, Node.js,… → …
- Running NeMo Relay installation for the CLI
- SKILL.md covers Choose The Install Path, Protect Codex Desktop Continuity, Install And Verify and Use Doctor For CLI Readiness…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Nemo Relay Install is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. 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.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files and assets (for example `BENCHMARK.md`, `assets/codex-desktop-recovery.md` and `evals/evals.json`).
It sits in AI & LLM Engineering. It works with Rust, Python and Node.js. The repository describes itself as: Agent Skills for NVIDIA products — install into Claude Code, Codex, and other coding agents to run Physical AI, robotics, simulation, CUDA, and RAG workflows end to end. The licence is Apache-2.0.
When your agent uses it
- Running NeMo Relay installation for the CLI
- Maintained framework integrations before runtime configuration
- Quick-start setup
Example prompts
- “/nemo-relay-install”
Requirements
- Node.js
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- CLI for a generic "try Relay" request, a temporary coding-agent run, the
- Maintained integration when the user already uses OpenClaw, Hermes,
- Language package when a Python, Node.js, or Rust application directly
- Source checkout only for contributors or unpublished changes. Follow the
What it can do on your machine
Read from SKILL.md and the folder at commit 67a13c0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.nvidia.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Nemo Relay Install loads about 1.7k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 851 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from NVIDIA/skills at commit 67a13c0, republished under its Apache-2.0 licence (© NVIDIA). 851 words, ~1,739 tokens.
Download SKILL.mdSave it as
.claude/skills/nemo-relay-install/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- nemo-relay-install
- description
- 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.
- license
- Apache-2.0
- metadata.author
- NVIDIA Corporation and Affiliates
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:
- CLI for a generic "try Relay" request, a temporary coding-agent run, the local gateway, or explicit persistent host-plugin setup. Read CLI Installation.
- Maintained integration when the user already uses OpenClaw, Hermes, LangChain, LangGraph, or Deep Agents. Read Maintained Integration Installation.
- Language package when a Python, Node.js, or Rust application directly owns its tool or model call sites. Read Language Package Installation.
- 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. The threads are
not deleted.
For Codex Desktop users:
- Recommend temporary transparent run first.
- If the user still wants persistent installation, read the Codex Desktop section in CLI Installation.
- Preview the install and proposed recovery-note location.
- Obtain confirmation before writing either the recovery note or global Codex configuration.
- Render
assets/codex-desktop-recovery.mdasNEMO_RELAY_CODEX_DESKTOP_RECOVERY.mdin the user's workspace root before running the persistent installer. - Do not restart Codex Desktop until the user has the recovery-file path.
Do not directly inspect, copy, delete, edit, or rewrite Codex session files,
private application configuration, or SQLite state to work around the
visibility bug. Supported nemo-relay install, uninstall, and doctor commands
may manage the Relay-generated provider and hook configuration.
Install And Verify
- Inspect the target manifest, environment, operating system, architecture, and existing installation before changing anything.
- Load only the reference for the selected path.
- Preserve the project's existing package manager and virtual environment.
- Use the latest compatible release unless the user or project requires an exact version.
- Show the exact install command before running a remote installer or changing a project manifest.
- Run only the selected path's basic availability check.
- Report what was installed, where it was installed, and the verification result. Then stop.
The primary documented language paths are Rust, Python, and Node.js. Treat Go and raw FFI as source-first advanced surfaces, not normal package installs. Do not treat a first scope, subscriber, gateway, plugin config, or LLM call as installation verification.
Show full SKILL.md (317 more words)Show less
Use Doctor For CLI Readiness And Configuration Issues
Know about nemo-relay doctor, but use it in the right scope:
- Run
nemo-relay doctorwhen the user installed the CLI and reports config, gateway, agent-readiness, plugin, exporter, or model-pricing issues. - Use
nemo-relay doctor --jsonwhen structured output will help an agent inspect checks programmatically. - Use
nemo-relay doctor --plugin claude-code,nemo-relay doctor --plugin codex, ornemo-relay doctor --plugin allonly for persistent host-plugin installations. - Do not require plugin doctor for transparent runs. Transparent-run setup does not require persistent host-plugin state.
- Do not use doctor as proof that a Python, Node.js, or Rust package dependency was installed. Verify those with the language package manager/import checks.
When doctor reports failures, summarize the failed checks and the specific remediation it suggests. Do not loop back to reinstalling every package unless the failed check points to a broken or missing install.
Hand Off After Install
Choose the next workflow from the user's immediate outcome:
- Use
nemo-relay-get-startedfor a first working scope, tool call, LLM call, or trial plugin setup. - Use the NeMo Relay CLI documentation or host-specific setup for a local CLI host-plugin workflow, not application runtime setup.
- Use the matching plugin or instrumentation skill for runtime configuration, plugin files, observability, or adaptive behavior.
Common Mistakes
Avoid these installation-scope mistakes:
- Using repository development setup when the user only needs a published package.
- Installing the CLI when the user needs an application binding, or installing a
binding when the user only needs the local
nemo-relayexecutable. - Treating persistent host-plugin installation as the default way to try Relay, instead of starting with temporary transparent run.
- Pinning old versions unless the user or project explicitly requires that version.
- Continuing into
plugins.toml, middleware registration, scopes, or quick-start examples before the install step has been verified.
Public Docs To Reference
Use these public entry points to confirm current installation guidance:
© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 8 other files (references, assets) in skills/nemo-relay-install of NVIDIA/skills.
- SKILL.md
- BENCHMARK.md
- assets/codex-desktop-recovery.md
- evals/evals.json
- references/cli-install.md
- references/language-packages.md
- references/maintained-integrations.md
- skill-card.md
- skill.oms.sig
Open the folder on GitHubat commit 67a13c0
Compare with similar skills
Nemo Relay Install next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Nemo Relay Install this skillNVIDIA/skills | 3.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Nemo Relay InstallNVIDIA/NeMo-Relay | 192 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Nemo Relay Get StartedNVIDIA/NeMo-Relay | 192 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Release Skillsnexmoe/eve | 421 | 3 repos | ~3.3k | Automated safety check: Pass | None | |
| CI Pipeline Synthesizerkajisho5/ffmpeg-skill | 1.9k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Dbgtheodo-group/debug-that | 158 | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Nemo Relay Get Started
NVIDIA/NeMo-Relay
A skill your agent uses when first-time NeMo Relay users want to try Relay, choose the least-complex supported quick start, or verify initial value through the CLI, a maintained integration, or…
Release Skills
nexmoe/eve
Universal release workflow. An agent skill from nexmoe/eve.
CI Pipeline Synthesizer
kajisho5/ffmpeg-skill
Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects.
Dbg
theodo-group/debug-that
Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.
Dep Auditor
laolaoshiren/claude-code-skills-zh
审计 Node.js、Python、Go、Rust、JVM、Ruby 项目的依赖漏洞、版本健康度与许可证事实；当用户要求检查 package.json、lockfile、requirements、go.mod、Cargo.toml、pom.xml、Gemfile.lock，或生成不改依赖的中文审计报告时使用
More from NVIDIA/skills
All 380 skills in this repo- Official
Vss Deploy Detection Tracking 2D
NVIDIA/skills
A skill your agent uses when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice.
- Official
HSB IP Def File Tool
NVIDIA/skills
Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.
- Official
Isaac Sim Mission Control Showcase
NVIDIA/skills
Runs and validates an end-to-end Mission Control demo in a locally installed Isaac Sim, with a Nova Carter robot driven through a Python server.
- Official
Defect Image Generation with Cosmos AnomalyGen
NVIDIA/skills
Orchestrates defect image generation for PCBA, metal surface and glass inspection with NVIDIA Cosmos AnomalyGen on OSMO, from cold-start Day 0 to real-photo Day 1 labeling.
- Official
Physical AI Video Augmentation on OSMO
NVIDIA/skills
Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.
- Official
TAO Detection KPI Analysis
NVIDIA/skills
Runs NVIDIA TAO Data Services KPI analysis on object detection results, comparing predictions to ground truth and writing per-class precision, recall and AP to a CSV.
Related
Categories
Questions about Nemo Relay Install
What does Nemo Relay Install do?
A skill your agent uses when choosing or running NeMo Relay installation for the CLI, Python, Node.js, Rust, OpenClaw, Hermes, or maintained framework integrations before runtime configuration or…. Nemo Relay Install is an agent skill from NVIDIA/skills, published by the product's own GitHub organization.js, Rust, OpenClaw, Hermes, or maintained framework integrations before runtime configuration or quick-start setup.
When should I use Nemo Relay Install?
Nemo Relay Install fits situations like: running NeMo Relay installation for the CLI; maintained framework integrations before runtime configuration; quick-start setup.
How do I install Nemo Relay Install in Claude Code?
Run `npx skills add NVIDIA/skills --skill nemo-relay-install -a claude-code`. Or copy the skill folder (skills/nemo-relay-install in NVIDIA/skills) into .claude/skills/nemo-relay-install in your project. Claude Code loads it when a task matches its description.
How do I install Nemo Relay Install in Codex?
Run `npx skills add NVIDIA/skills --skill nemo-relay-install -a codex`. Or copy the skill folder (skills/nemo-relay-install in NVIDIA/skills) into .agents/skills/nemo-relay-install in your project. Codex loads it when a task matches its description.
Can I use Nemo Relay Install in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/skills --skill nemo-relay-install -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nemo-relay-install, .gemini/skills/nemo-relay-install, .github/skills/nemo-relay-install and .opencode/skills/nemo-relay-install in your project.
What does Nemo Relay Install need to run?
SKILL.md names no scripts, command-line tools or credentials: Nemo Relay Install is instructions for the agent only. Our summary lists: Node.js.
Does Nemo Relay Install access the network?
SKILL.md names 1 domain. As links in the text: docs.nvidia.com. This is read from the text; nothing was executed.
Is Nemo Relay Install safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Nemo Relay Install use?
Nemo Relay Install is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Nemo Relay Install use?
About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.
What are the alternatives to Nemo Relay Install?
Skills that share tags, products or a category with Nemo Relay Install: Nemo Relay Install (NVIDIA/NeMo-Relay, 192 stars), Nemo Relay Get Started (NVIDIA/NeMo-Relay, 192 stars), Release Skills (nexmoe/eve, 421 stars) and CI Pipeline Synthesizer (kajisho5/ffmpeg-skill, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nemo Relay Install?
NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,539 GitHub stars. The repository holds 380 skills in this directory. The repository was last updated on October 7, 2026.
Source: NVIDIA/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.