Nemo Relay Install
NVIDIAOfficialCreated by NVIDIA Corporation and Affiliates
- Skill
- Workflow
- Software development
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The nemo-relay-install skill provides a structured procedure for identifying, installing, and verifying the appropriate NeMo Relay component. It ensures that the installation aligns with the user's specific runtime, language, or framework requirements by consulting official documentation and current release metadata. The skill emphasizes environment preservation, avoiding unnecessary configuration, and verifying installations through documented checks before handing off to further setup steps.
What it does
- Disambiguates user needs to select between CLI, language bindings, or framework integrations.
- Resolves the latest stable release requirements using official metadata and documentation.
- Preserves existing project environments, package managers, and virtual environments.
- Executes installation commands based on verified, target-specific instructions.
- Performs documented availability checks to confirm successful installation.
- Provides a safe path for persistent host integrations with recovery documentation.
When to use it
- When you need to install NeMo Relay for a specific agent runtime, language, or framework.
- When you need to verify if a runtime or environment is ready for NeMo Relay.
- When you are setting up a coding-agent host integration or CLI tool.
- When you need to ensure your project's existing package manager is respected during installation.
Advantages
- Prevents environment pollution by respecting existing package managers and lockfiles.
- Ensures installation of the latest stable version rather than relying on outdated cached data.
- Provides a clear, safe path for sensitive persistent host changes with recovery planning.
- Reduces errors by requiring explicit target identification before installation.
Usage examples
- “How do I install NeMo Relay for my Python project?”
- The agent will inspect your project's environment, identify the appropriate Python binding, and provide the correct installation command based on your current package manager.
- “I need to set up the NeMo Relay CLI on my machine.”
- The agent will guide you through the CLI installation process, verify the executable's availability, and confirm the installation without modifying your existing model configurations.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/nemo-relay-install/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip nemo-relay-install.zip -d .agents/skills
Documentation by NVIDIA Corporation and Affiliates
Install NeMo Relay
Resolve what the user needs, install the appropriate current stable package or executable, verify availability, and stop. Installation does not include a first application, plugin configuration, scopes, or a model-consuming trial.
Disambiguate Before Installing
Establish the desired outcome and the boundary that owns execution before selecting a Relay type. Inspect available project context, but do not assume that a Python manifest means the user wants a Python binding rather than Relay for their coding agent.
When the target is unclear, ask one concise question:
Are you adding Relay to an existing agent runtime or framework, integrating it into your own application, or using its CLI or local gateway?
Resolve the named runtime, framework, language, or plugin only as far as needed to select its installation instructions. Preserve an explicit choice or an earlier handoff; do not repeat questions already answered. A generic "install Relay" or "try Relay" request alone does not authorize choosing the CLI.
| Established target | Reference |
|---|---|
| CLI, coding-agent wrapper, or persistent host integration | CLI Installation |
| Native agent integration, framework integration, or plugin bundle | Maintained Integrations |
| Application-owned language binding | Language Packages |
| Explicit contributor or source-build request | Current repository development guide |
Resolve Current Stable Requirements
Read the current installation guide for the selected target. Resolve prerequisites from the selected release's installation sections, support matrix, and package metadata rather than a remembered standalone prerequisites page. Confirm the latest published stable release using release metadata, official releases, and the relevant package registry. Check the target's actual platform assets and package availability, not just a repository version or a pending PR.
Default to the latest published stable release, excluding prereleases unless explicitly requested. Preserve explicit user or project version constraints.
Derive operating-system, architecture, language, host, and dependency requirements from that release's documentation and metadata at execution time.
Do not copy version pins or minimum-version tables into this skill. Retain a specific version note only for an established incompatibility, with its source.
A quick-start example's pin does not override the stable default. If its requirements conflict with the selected release or project, explain the mismatch and resolve the choice before installing.
Native or dependency-managed integrations may own their Relay dependency. Follow that supported relationship rather than installing a second runtime.
Resolve independently released bundles separately and check compatibility. Their release number need not match Relay's.
Resolve the documentation version explicitly: an unversioned page may display an older stable guide. When rendered documentation is inaccessible or lacks the selected path, use the official repository at the matching release tag; use its development branch only for an explicitly requested development workflow. A cached release redirect alone does not establish the latest version.
If current sources cannot be checked, state what is unverified. Do not infer the newest release or requirements from this skill, an old checkout, a generated benchmark, or a source-built quick-start test.
Install And Verify
Inspect the environment, existing installation, manifest, and authoritative package manager. Load only the relevant reference and current target-specific documentation. Preserve the project's manager and virtual environment.
Derive the install command from those sources, preview it, and proceed within existing authorization. For remote installers, separate download, review, and execution; use the resolved release's installer and integrity checks rather than executing an unreviewed default-branch response.
Use only the documented availability check for the chosen target. Diagnose a failed check at that boundary instead of reinstalling unrelated packages. Report the resolved release, installation location, and verification evidence. Do not configure export, launch a gateway, or make a model call as an install check.
Persistent Codex Desktop Continuity
Persistent Codex setup can change the provider used to display Desktop conversations. Before that path, read the continuity section in CLI Installation, check the referenced upstream issue's applicability, and explain any relevant risk.
Retain the recovery-note and explicit confirmation gate before global changes. Do not inspect, copy, delete, or rewrite private session storage or SQLite state as a visibility workaround. Use supported Relay install, uninstall, and diagnostic commands.
Hand Off
For a first working example, hand off to nemo-relay-get-started with the
chosen target, resolved release, environment, and verified installation.
Continue from the appropriate guide step without repeating selection.
For durable export, instrumentation expansion, or plugin behavior, use the matching workflow. Do not repeat installation when it is already complete.
Files
- ATTRIBUTION.mdAdded by AutoGineer939 B
- BENCHMARK.md9.8 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md5.8 KiB
- assets/codex-desktop-recovery.md3.9 KiB
- evals/evals.json13.0 KiB
- references/cli-install.md3.5 KiB
- references/language-packages.md2.1 KiB
- references/maintained-integrations.md3.0 KiB
- skill-card.md4.8 KiB
- skill.oms.sig5.4 KiB
evals/evals.json
[
{
"id": "nemo-relay-install-001",
"question": "I want to install the NeMo Relay CLI on macOS so I can get the nemo-relay command. I do not need app instrumentation yet.",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Resolve the latest published stable CLI and its actual platform requirements from current official sources; install and verify only the executable.",
"expected_behavior": [
"Read the installation skill and CLI reference",
"Check current release metadata, the selected asset, and the release's prerequisites",
"Derive the install command from the current guide and review a remote installer before execution",
"Verify executable availability without configuring plugins or running a model",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-002",
"question": "My Python app has pyproject.toml and poetry.lock. Add Relay as a dependency, but do not configure observability.",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Preserve Poetry, resolve the current stable Python package and its requirements, and verify it in the project environment.",
"expected_behavior": [
"Recognize an explicitly requested application dependency",
"Inspect authoritative project metadata and resolve any manager conflict",
"Use the current package instructions with Poetry rather than introducing another manager",
"Verify package availability through the Poetry environment and stop before runtime configuration",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-003",
"question": "My Rust service needs the Relay core package. Adaptive tuning might come later.",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Use current stable crate metadata and installation guidance to add only the required core dependency.",
"expected_behavior": [
"Preserve the Cargo workspace and explicit project constraints",
"Resolve current toolchain requirements instead of quoting a minimum from the skill",
"Do not add adaptive packages solely because they may be useful later",
"Verify dependency resolution without implementing a first workflow",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-004",
"question": "We use LangChain and Deep Agents. Install the maintained integration dependencies, without wiring callbacks.",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Read current integration installation instructions and install only the framework dependencies needed by the project.",
"expected_behavior": [
"Read the maintained-integrations reference and current target-specific docs",
"Preserve the project's authoritative Python manager",
"Derive the needed extras and provider dependencies from current sources",
"Stop before callbacks, plugin activation, or model calls",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-005",
"question": "Relay is already installed. I need plugin configuration for export and adaptive behavior.",
"expected_skill": null,
"expected_script": null,
"ground_truth": "Recognize that installation is complete and route configuration to the appropriate follow-up workflow.",
"expected_behavior": [
"Do not invoke installation as the primary workflow or repeat package commands",
"Distinguish dependency installation from runtime configuration",
"Use targeted plugin or instrumentation guidance",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-006",
"question": "Can you install NeMo Relay?",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Disambiguate the intended runtime, framework, application binding, or CLI use before choosing packages.",
"expected_behavior": [
"Ask one concise question about the intended outcome or execution boundary",
"Do not default to the CLI or provide an installer before the target is established",
"Use existing conversation context to avoid repeating an answered question",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-007",
"question": "I am in a Python repository and just want to try Relay. What should I install?",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Treat the manifest as context rather than authorization to select a Python binding or CLI.",
"expected_behavior": [
"Ask whether Relay is for an agent runtime, framework, direct application integration, or gateway use",
"Do not silently choose the CLI because this is a generic trial",
"Do not infer a binding solely from the Python manifest",
"Install only after establishing the actual target",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-008",
"question": "I installed the CLI, but my gateway or config seems broken. Should I reinstall everything?",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Use current documented diagnostics at the failed readiness or configuration boundary without reinstalling unrelated packages.",
"expected_behavior": [
"Confirm what is installed and which operation failed",
"Read current diagnostic guidance for the selected mode",
"Distinguish executable readiness from persistent host or gateway configuration",
"Do not use CLI diagnostics as proof that an unrelated language package is installed",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-009",
"question": "Make Relay persistent in Codex Desktop, where I am having this conversation.",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Check current persistent-install guidance and the provider-filtering issue, preview the change, and preserve the recovery-note and confirmation gate.",
"expected_behavior": [
"Check applicability of the referenced continuity issue rather than asserting the bug is current solely from the skill",
"Explain any relevant provider/history risk and temporary alternative",
"Obtain explicit confirmation covering the recovery note and global change",
"Render and verify the workspace recovery note before the supported installer runs",
"Give the recovery-file path before a requested restart and avoid private session storage",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-010",
"question": "My conversations disappeared after persistent Relay setup in Codex Desktop. Help undo it.",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Check the documented provider-visibility issue and supported recovery path without assuming data deletion or modifying private storage.",
"expected_behavior": [
"Read current recovery and diagnostic documentation",
"Explain hidden-versus-deleted uncertainty using the observed setup",
"Use the supported uninstall or continuation route after fully quitting Desktop",
"Do not inspect, copy, rewrite, or delete session files or SQLite state",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-011",
"question": "Install dependencies for the LangChain NVIDIA quick start in this Poetry project. Do not run the example yet.",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Resolve stable package requirements and provider extras from current documentation while preserving Poetry.",
"expected_behavior": [
"Read the current installation and matching integration guidance",
"Derive framework and provider dependencies from the selected sources rather than a stored extras recipe",
"Use the latest published stable release unless an explicit project constraint applies",
"Do not let an example pin silently override the stable default",
"Verify in the Poetry environment without a model call",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-012",
"question": "Install the published Switchyard plugin for Relay. I do not want a source build.",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Resolve compatible current stable CLI and plugin-bundle releases independently, verify integrity, and stop at availability.",
"expected_behavior": [
"Read the current bundle and platform documentation",
"Do not assume plugin and Relay release numbers match",
"Check the selected platform's actual release assets and checksum procedure",
"Preserve the manifest/library bundle layout documented for that release",
"Do not enable routing, start a gateway, or broaden attestation policy as an installation check",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-013",
"question": "A pending quick-start guide pins an unpublished Relay build. I asked for a normal stable install.",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Default to the latest published stable release and its actual requirements, explaining why the pending guide does not establish publication or override the requested default.",
"expected_behavior": [
"Check official release and package metadata for the chosen target",
"Do not install a prerelease or source build merely to reproduce a pending guide",
"Use documentation compatible with the resolved stable release",
"Report a platform or package publication gap rather than claiming success",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-014",
"question": "Hermes is already installed. Install Relay for its native quick start.",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Read current native-integration requirements, check host readiness, and avoid a duplicate dependency installation.",
"expected_behavior": [
"Check current Hermes integration guidance and whether the host manages Relay",
"Verify native readiness through the documented host checks",
"Do not install the former observability plugin or a CLI wrapper as a substitute for native support",
"Hand local export and the first run to get-started with the established target",
"Preserves unrelated files and settings, respects existing authorization, and does not expose credentials or complete captured payloads"
]
},
{
"id": "nemo-relay-install-015",
"question": "The prerequisites link is unavailable and the public docs display an older release than the live package registry. Preview the current stable CLI installation.",
"expected_skill": "nemo-relay-install",
"expected_script": null,
"ground_truth": "Resolve the latest published stable release by cross-checking live official release and registry metadata, then obtain compatible installation and platform requirements from release-matched official source rather than an old prerequisite table.",
"expected_behavior": [
"Do not treat a cached latest-release redirect or default documentation version as authoritative by itself",
"Check actual selected-platform release assets and package availability",
"Use the matching release tag when rendered documentation is inaccessible or incomplete",
"State any still-unverified requirements rather than inventing a minimum version"
]
}
]
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- NVIDIA Corporation and Affiliates
- Publisher
- NVIDIA (Official)
- Source
- NVIDIA/skills · skills/nemo-relay-install · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by NVIDIA Corporation and Affiliates or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download nemo-relay-install.zip