AutoGineer
Generated banner for Nemo Relay Install
Generated logo for Nemo Relay Install

Nemo Relay Install

NVIDIAOfficialCreated by NVIDIA Corporation and Affiliates

  • Skill
  • Workflow
  • Software development
  • Apache-2.0
  • Medium risk
Download ZIP

From the author

Use this skill when choosing or running NeMo Relay installation for an agent runtime, application language, framework integration, or plugin bundle, or checking a runtime's native Relay readiness. Do not use it for first-run instrumentation or export configuration.
— the description by NVIDIA Corporation and Affiliates

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

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/nvidia/nemo-relay-install/download

  2. Unzip 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 targetReference
CLI, coding-agent wrapper, or persistent host integrationCLI Installation
Native agent integration, framework integration, or plugin bundleMaintained Integrations
Application-owned language bindingLanguage Packages
Explicit contributor or source-build requestCurrent 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

references/language-packages.md

<!-- SPDX-FileCopyrightText: Copyright (c) 2026, NVIDIA CORPORATION & AFFILIATES. All rights reserved. SPDX-License-Identifier: Apache-2.0 -->

Language Package Installation

Use this path when the user's application owns the calls and needs a Relay binding. Establish that intent before inferring an install type from a manifest.

Read the current installation guide for the selected language, together with the selected release's package metadata and linked support requirements. Resolve the latest published stable package and derive its runtime requirements from current package metadata and release documentation. Do not retain a package-version or language-minimum table here.

Preserve The Authoritative Environment

  • Python: inspect project instructions, pyproject.toml, manager-specific configuration, and lockfiles. Preserve the established manager and virtual environment rather than introducing another dependency workflow.

  • Node.js: inspect package.json, especially packageManager, and the lockfiles. Preserve the declared manager and its dependency conventions.

  • Rust: inspect Cargo.toml, the workspace, toolchain configuration, and lockfile. Add only the runtime crates needed for the selected outcome.

When manager declarations and lockfiles conflict, explain the conflict and resolve which is authoritative before changing the project. Do not initialize another manifest or lockfile in an existing project.

Use the selected manager's syntax for the resolved stable dependency, respecting explicit project constraints. A newer repository version or quick-start pin is not evidence that a package has been published.

Verify availability in the actual target environment: an import or module-load check, or package-manager resolution as documented for that binding. Do not accidentally verify a system interpreter instead of the project environment.

Stop before scopes, tool/model examples, plugin configuration, or adaptive behavior. Pass the selected language, environment, and installed version to the matching quick-start guide through nemo-relay-get-started.

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