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
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
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