New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Nemo Relay Install

by NVIDIA in 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…

OfficialApache-2.0Auto-check passedAI & LLM Engineering

Install Nemo Relay Install

skills CLI
$ npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-install -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/NeMo-Relay nemo-relay-install --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/nemo-relay-install .claude/skills/nemo-relay-install && rm -rf skills-src

Use ~/.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/

Facts

Skill name
nemo-relay-install
GitHub stars
192
Token cost
~1.7k tokens
SKILL.md length
854 words
Files
9 (incl. references, assets)
Skills in repo
30
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, or maintained framework integrations, or when explaining Hermes Agent's…

  • 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/NeMo-Relay, 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, or maintained framework integrations, or when explaining Hermes Agent's built-in Relay integration.

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, covering Building AI agents. It works with Rust, Python and Node.js. The repository describes itself as: Multi-language agent runtime and library for execution scope management, lifecycle events, and middleware on tool and LLM calls. The licence is Apache-2.0.

When your agent uses it

  • Running NeMo Relay installation for the CLI
  • Maintained framework integrations
  • Explaining Hermes Agents built-in Relay integration

Example prompts

  • “/nemo-relay-install”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. CLI for a generic "try Relay" request, a temporary coding-agent run, the
  2. Maintained integration when the user already uses OpenClaw, Hermes,
  3. Language package when a Python, Node.js, or Rust application directly
  4. 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 16d73b4. 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 57 tokens; SKILL.md has 854 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.5k

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/NeMo-Relay at commit 16d73b4, republished under its Apache-2.0 licence (© NVIDIA). 854 words, ~1,746 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, or maintained framework integrations, or when explaining Hermes Agent's built-in Relay integration.
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 built-in Hermes Agent support?

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:

  1. CLI for a generic "try Relay" request, a temporary coding-agent run, the local gateway, or explicit persistent host-plugin setup. Read CLI Installation.
  2. Maintained integration when the user already uses OpenClaw, Hermes, LangChain, LangGraph, or Deep Agents. Read Maintained Integration Installation.
  3. Language package when a Python, Node.js, or Rust application directly owns its tool or model call sites. Read Language Package Installation.
  4. 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:

  1. Recommend temporary transparent run first.
  2. If the user still wants persistent installation, read the Codex Desktop section in CLI Installation.
  3. Preview the install and proposed recovery-note location.
  4. Obtain confirmation before writing either the recovery note or global Codex configuration.
  5. Render assets/codex-desktop-recovery.md as NEMO_RELAY_CODEX_DESKTOP_RECOVERY.md in the user's workspace root before running the persistent installer.
  6. 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

  1. Inspect the target manifest, environment, operating system, architecture, and existing installation before changing anything.
  2. Load only the reference for the selected path.
  3. Preserve the project's existing package manager and virtual environment.
  4. Use the latest compatible release unless the user or project requires an exact version.
  5. Show the exact install command before running a remote installer or changing a project manifest.
  6. Run only the selected path's basic availability check.
  7. 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 doctor when the user installed the CLI and reports config, gateway, agent-readiness, plugin, exporter, or model-pricing issues.
  • Use nemo-relay doctor --json when structured output will help an agent inspect checks programmatically.
  • Use nemo-relay doctor --plugin claude-code, nemo-relay doctor --plugin codex, or nemo-relay doctor --plugin all only 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-started for 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-relay executable.
  • 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/NeMo-Relay.

  • 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 16d73b4

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.

Nemo Relay Install compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nemo Relay Install this skillNVIDIA/NeMo-Relay192—~1.7kAutomated safety check: PassApache-2.0
Deploy AI Agentbolivian-peru/os-moda119—~1.1kAutomated safety check: PassApache-2.0
Logfire Instrumentationpydantic/skills140—~6.1kAutomated safety check: PassMIT
Edgeone Makers ToolsTencentEdgeOne/edgeone-makers-tools1.9k—~395Automated safety check: PassMIT
Nemo Relay InstallNVIDIA/skills3.5k—~1.7kAutomated safety check: PassApache-2.0
Release Skillsnexmoe/eve4213 repos~3.3kAutomated safety check: PassNone

Similar skills

  • Deploy AI Agent

    bolivian-peru/os-moda

    Deploy and manage AI agent workloads with GPU checks, API key management, and health monitoring

    119 GitHub stars~1.1k tokensUpdated 3 mo ago
    AI & LLM EngineeringAuto-check passed

  • Logfire Instrumentation

    pydantic/skills

    Official

    Add Pydantic Logfire observability to application code — traces, logs, metrics, and AI/agent spans.

    140 GitHub stars~6.1k tokensUpdated 6 days ago
    AI & LLM EngineeringAuto-check passed

  • Edgeone Makers Tools

    TencentEdgeOne/edgeone-makers-tools

    EdgeOne Makers 全栈开发技能包 —— 涵盖 AI Agent 开发（DeepAgents、LangGraph、 Claude SDK、OpenAI Agents、CrewAI）、云函数（Node.js/Go/Python）、边缘函数、 KV 存储、中间件及快速部署，帮助 AI 编程助手准确高效地在 EdgeOne 平台上构建和发布应用。

    1.9k GitHub stars~395 tokensUpdated today
    AI & LLM EngineeringAuto-check passed

  • Nemo Relay Install

    NVIDIA/skills

    Official

    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…

    3.5k GitHub stars~1.7k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

  • Release Skills

    nexmoe/eve

    Universal release workflow. An agent skill from nexmoe/eve.

    421 GitHub starsUsed in 3 repos~3.3k tokens
    DevelopmentAuto-check passed

  • CI Pipeline Synthesizer

    kajisho5/ffmpeg-skill

    Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects.

    1.9k GitHub starsUsed in 1 repo~1.1k tokens
    DevOps & CloudAuto-check passed

More from NVIDIA/NeMo-Relay

All 30 skills in this repo

  • Draft Release Notes

    NVIDIA/NeMo-Relay

    Official

    Compare NeMo Relay release refs and draft the current documentation release-notes page from verified repository evidence.

    192 GitHub stars~575 tokensUpdated today
    Auto-check passed

  • Nemo Relay Migrate From Flow

    NVIDIA/NeMo-Relay

    Official

    A skill your agent uses when migrating applications, examples, integrations, documentation, manifests, or repository code from NeMo Flow to NeMo Relay across Python, Rust, Node.js, Go, C FFI, CLI…

    192 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Add Middleware

    NVIDIA/NeMo-Relay

    Official

    Add a new NeMo Relay guardrail or intercept type, registration surface, or pipeline stage.

    192 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Contribute Docs

    NVIDIA/NeMo-Relay

    Official

    Author or edit NeMo Relay documentation or examples when repository-specific MDX, public API, integration, or release-history conventions matter.

    192 GitHub stars~710 tokensUpdated today
    Auto-check passed

  • Maintain CI

    NVIDIA/NeMo-Relay

    Official

    Change or review NeMo Relay GitHub Actions workflows where permissions, pinned actions, caching, reusable workflows, or release gates require repository-specific handling.

    192 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Nemo Relay Plugin Build

    NVIDIA/NeMo-Relay

    Official

    A skill your agent uses when building or packaging reusable NeMo Relay runtime behavior as an embedded configuration component or a manifest-backed rustdynamic native or worker gRPC plugin, with…

    192 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Works with

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, or maintained framework integrations, or when explaining Hermes Agent's…. Nemo Relay Install is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization.js, Rust, OpenClaw, or maintained framework integrations, or when explaining Hermes Agent's built-in Relay integration.

When should I use Nemo Relay Install?

Nemo Relay Install fits situations like: running NeMo Relay installation for the CLI; maintained framework integrations; explaining Hermes Agents built-in Relay integration.

How do I install Nemo Relay Install in Claude Code?

Run `npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-install -a claude-code`. Or copy the skill folder (skills/nemo-relay-install in NVIDIA/NeMo-Relay) 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/NeMo-Relay --skill nemo-relay-install -a codex`. Or copy the skill folder (skills/nemo-relay-install in NVIDIA/NeMo-Relay) 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/NeMo-Relay --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: Deploy AI Agent (bolivian-peru/os-moda, 119 stars), Logfire Instrumentation (pydantic/skills, 140 stars), Edgeone Makers Tools (TencentEdgeOne/edgeone-makers-tools, 1.9k stars) and Nemo Relay Install (NVIDIA/skills, 3.5k 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/NeMo-Relay, which has 192 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 8, 2026.

Source: NVIDIA/NeMo-Relay on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.