Nemo Relay Get Started
NVIDIAOfficialCreated by NVIDIA Corporation and Affiliates
- Skill
- Tool integration
- Automation and integrations
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The nemo-relay-get-started skill assists new users in navigating the NeMo Relay ecosystem by identifying the correct quick-start guide based on their specific runtime, framework, or application environment. It focuses on providing a structured, evidence-based path to verify a successful initial integration. The skill emphasizes adherence to official documentation, version compatibility, and the use of guide-specific verification steps, ensuring that users establish a working proof-of-concept without unnecessary configuration or production-level complexity.
What it does
- Identifies the appropriate quick-start guide based on user goals and environment.
- Routes users to specific trial paths for CLI, agent runtimes, frameworks, or manual integrations.
- Ensures commands and configurations are derived directly from the selected guide's current version.
- Facilitates guide-based verification to confirm successful integration.
- Provides guidance on transitioning from an initial trial to further plugin configuration.
- Maintains project continuity by preserving existing settings and workflows.
When to use it
- When a user is new to NeMo Relay and needs help selecting a starting point.
- When a user needs to verify their first working integration with NeMo Relay.
- When a user requires assistance following a specific quick-start guide for their environment.
- When a user needs to confirm that their initial setup meets the guide's success criteria.
Advantages
- Reduces setup friction by providing a clear, guided path for initial integration.
- Ensures technical accuracy by relying on version-matched, official documentation.
- Prevents configuration errors by adhering to guide-specific prerequisites and verification steps.
- Maintains the integrity of the user's existing project environment.
- Provides a clear progression path from initial proof to broader instrumentation.
Usage examples
- “I am new to NeMo Relay and want to try it with LangChain. How do I get started?”
- The agent identifies the LangChain quick-start guide, verifies the installed release compatibility, and walks the user through the specific attachment and verification steps for LangChain.
- “I need to set up NeMo Relay for my Hermes runtime. What is the first step?”
- The agent routes the user to the Hermes-specific quick-start guide, ensuring the user follows the native integration path rather than installing unnecessary wrappers.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/nemo-relay-get-started/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip nemo-relay-get-started.zip -d .agents/skills
Documentation by NVIDIA Corporation and Affiliates
Get Started With NeMo Relay
Help the user choose and follow the maintained quick-start guide that fits their existing runtime, framework, plugin, or application. The guide owns the implementation; this skill owns selection, continuity, and evidence.
Select The Guide
Read the current quick-start index. Use the user's stated goal and existing environment to find the smallest applicable path. Preserve a target established in conversation or installation.
When the boundary is unclear, ask one concise question before choosing. Do not infer that every generic "try Relay" request means a coding-agent demo, or introduce a framework just to demonstrate Relay.
Use these references only for target-specific routing and cautions:
| Established boundary | Reference |
|---|---|
| Local coding agent or CLI | CLI Trial |
| Native agent runtime or managed plugin | Agent Runtime Trial |
| Maintained framework integration | Framework Trial |
| Switchyard routing | Switchyard Trial |
| Application-owned language calls | Language Trial |
Follow The Current Guide
Read the selected guide before proposing commands or configuration, including its prerequisites, sample files, run instructions, verification, and limitations. Use documentation compatible with the installed stable release. The current published guide is the normal source; use an explicitly requested pending PR or other supplied revision as such, without treating it as published support. Resolve the documentation version instead of assuming an unversioned URL is current. When rendered documentation is inaccessible or omits the selected path, use the official source at the matching release tag, or the development checkout for an explicitly requested development preview. A failed HTTP request alone does not prove that a guide was removed; check its index and source.
Keep commands and referenced sample files from the same guide revision. If working from source, resolve its referenced files in that checkout. Do not reconstruct the recipe from this skill, an older session, or a benchmark. If the guide cannot be read or its sample files are unavailable, state the gap rather than inventing instructions.
For missing dependencies, use nemo-relay-install with the already-selected
target. Its default is the latest published stable release, subject to explicit
user or project constraints. Preserve a successful install and continue at
the next appropriate guide step; do not repeat target selection.
A guide's example pin is not an instruction to downgrade or use an unpublished release. If the guide and installed release are incompatible, resolve that mismatch using current release documentation before proceeding.
Execute And Verify
Use Guide-Based First-Value Checks while adapting only what the user's existing environment requires.
Explain the guide's attachment boundary and proposed changes. Preserve the project's manager, unrelated settings, and existing artifacts. Proceed within existing authorization, honoring requests to preview or stop before a live run.
Follow the selected guide's configuration, execution, shutdown, and verification steps. Derive file locations, schemas, commands, prompts, lifecycle expectations, and output formats from that guide rather than imposing a shared recipe. Run only the chosen path and report the evidence it actually establishes.
Successful application output alone is not proof that Relay captured the work. Use fresh evidence and the guide's own success criteria. Do not demand model credentials, a tool call, ATIF, or another exporter when that guide does not.
After The First Proof
Stop the initial trial when the guide's success checks pass. Explain the observed value and Relay's progression: attach once, then extend supported behavior through plugin configuration.
Resolve plugin and integration documentation for the installed Relay release, including any explicit version constraint, before suggesting one next plugin for the user's goal. Use the stable plugin overview only after confirming compatibility with that release; otherwise use the release-matched documentation or official source. Do not repeat Observability setup if the guide already established it, or offer capabilities unsupported by the selected integration.
Hand broader instrumentation to nemo-relay-instrument-calls, unsupported
framework work to nemo-relay-integrate-upstream, and additional export to
nemo-relay-plugin-observability. Persistent host setup belongs to
nemo-relay-install, including its applicable Codex Desktop continuity gate.
Production deployment and multiple new behaviors belong to follow-up work.
Files
- ATTRIBUTION.mdAdded by AutoGineer951 B
- BENCHMARK.md11.3 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md5.3 KiB
- evals/evals.json19.1 KiB
- references/agent-runtimes-try-now.md1.8 KiB
- references/built-in-integrations-try-now.md1.4 KiB
- references/cli-try-now.md1.8 KiB
- references/first-value.md2.6 KiB
- references/manual-language-try-now.md1.5 KiB
- references/switchyard-try-now.md1.7 KiB
- skill-card.md4.8 KiB
- skill.oms.sig5.9 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-get-started · 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-get-started.zip