New: 97,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 Get Started

by NVIDIA in NVIDIA/NeMo-Relay

A skill your agent uses when first-time NeMo Relay users want to try Relay, choose the least-complex supported quick start, or verify initial value through the CLI, a maintained integration, or…

OfficialApache-2.0Auto-check passedAI & LLM Engineering

Install Nemo Relay Get Started

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

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

GitHub CLI
$ gh skill install NVIDIA/NeMo-Relay nemo-relay-get-started --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-get-started .claude/skills/nemo-relay-get-started && 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-get-started
GitHub stars
190
Token cost
~1.8k tokens
SKILL.md length
831 words
Files
8 (incl. references)
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when first-time NeMo Relay users want to try Relay, choose the least-complex supported quick start, or verify initial value through the CLI, a maintained integration, or…

  • Works in 4 steps: CLI try-now (default): choose this for a… → Hermes Agent native path: choose this… → Built-in integrations try-now: choose… → …
  • First-time NeMo Relay users want to try Relay
  • SKILL.md covers Choose A Try-Now Path, Resolve Installation Without…, Apply The Common First-Value… and Continue With One Plugin, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Nemo Relay Get Started is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Use this skill when first-time NeMo Relay users want to try Relay, choose the least-complex supported quick start, or verify initial value through the CLI, a maintained integration, or direct Python, Node.js, or Rust instrumentation before production setup.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `BENCHMARK.md`, `evals/evals.json` and `references/built-in-integrations-try-now.md`).

It sits in AI & LLM Engineering. It works with Python, Rust 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

  • First-time NeMo Relay users want to try Relay
  • Choose the least-complex supported quick start
  • Verify initial value through the CLI
  • A maintained integration

Example prompts

  • “/nemo-relay-get-started”

Requirements

  • Node.js

Workflow steps

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

  1. CLI try-now (default): choose this for a generic "try Relay" request or
  2. Hermes Agent native path: choose this when Hermes Agent owns the
  3. Built-in integrations try-now: choose this when an existing LangChain,
  4. Language-specific manual try-now: choose this when the user's Python,

What it can do on your machine

Read from SKILL.md and the folder at commit 651453f. 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 Get Started loads about 1.8k tokens when it runs, and up to ~6k if it reads all its reference files. Until then it costs about 70 tokens; SKILL.md has 831 words of instructions outside code blocks.

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

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 651453f, republished under its Apache-2.0 licence (© NVIDIA). 831 words, ~1,755 tokens.

Download SKILL.mdSave it as .claude/skills/nemo-relay-get-started/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
nemo-relay-get-started
description
Use this skill when first-time NeMo Relay users want to try Relay, choose the least-complex supported quick start, or verify initial value through the CLI, a maintained integration, or direct Python, Node.js, or Rust instrumentation before production setup.
license
Apache-2.0
metadata.author
NVIDIA Corporation and Affiliates

Get Started With NeMo Relay

Guide a new user to visible Relay value with the least complicated applicable trial. Do not begin with production deployment or Relay's full architecture. Keep the first run focused on one observable success path.

Choose A Try-Now Path

Evaluate these paths in order. Use the first one that fits the user's stated goal and existing environment.

  1. CLI try-now (default): choose this for a generic "try Relay" request or when the user wants value without modifying application code. Run Codex or Claude Code through the local CLI wrapper. Read CLI Try-Now.
  2. Hermes Agent native path: choose this when Hermes Agent owns the execution boundary. Explain that NeMo Relay is built in and requires no separate Relay installation, observability plugin, or Relay CLI setup. State explicitly: "Hermes Agent understands NeMo Relay plugin configurations." Stop after confirming the native integration. Do not provide installation or observability-configuration instructions, and do not continue into the generic plugin progression.
  3. Built-in integrations try-now: choose this when an existing LangChain, LangGraph, Deep Agents, or OpenClaw application owns the execution boundary. Prefer the maintained supported integration over manual wrapping. Read Built-In Integrations Try-Now.
  4. Language-specific manual try-now: choose this when the user's Python, Node.js, or Rust application directly owns its tool or LLM call sites and no maintained integration is the better boundary. Read Manual Language Try-Now.

Do not ask the user to choose among all four when their request, manifest, or framework already identifies the boundary. For an unspecified request, use the CLI path. When more than one CLI agent is available, ask one concise question to select the agent.

Resolve Installation Without Looping

Select the try-now path before choosing an install package.

  • CLI path -> verify nemo-relay --version; if missing, use nemo-relay-install for the CLI outcome.
  • Hermes Agent native path -> do not install or configure Relay separately.
  • Built-in integration path -> use nemo-relay-install for the named framework or harness package.
  • Manual language path -> use nemo-relay-install for the detected language package.

If installation already succeeded, preserve the chosen path and continue from its next step. Do not ask the install-path question again or bounce between the install and get-started skills.

Apply The Common First-Value Contract

Do not apply this section to the Hermes Agent native path.

Follow the selected reference, then:

  1. Inspect the target environment and existing Relay configuration before proposing changes. Treat repository-local .nemo-relay/config.toml and .nemo-relay/plugins.toml as unsupported project configuration. Do not create, edit, merge, or trust those files as active Relay configuration.
  2. Explain the attachment boundary and show the exact minimal change.
  3. Obtain confirmation before writing configuration, modifying application code, or launching a model-consuming run.
  4. Use a non-sensitive, read-only trial and exercise one representative tool and LLM path when the selected surface exposes both.
  5. Verify observable evidence from the selected path rather than treating a successful application result as proof that Relay is active.
  6. Summarize the captured root, tool, and model relationships without dumping prompts, credentials, or complete event payloads.

Explain only the concepts visible in the result: the chosen attachment boundary, scopes and parentage, captured lifecycle events, and how subscribers or the Observability plugin make those events inspectable. Keep instrumentation and export distinct.

Show full SKILL.md (301 more words)Show less

Continue With One Plugin

Do not apply this section to the Hermes Agent native path.

Stop the initial try-now workflow when the selected path's success checks pass. Then make one additional built-in plugin the primary suggested next step.

Explain Relay's core progression: instrument an execution boundary once, then change or extend behavior through plugin configuration without repeatedly rewriting those call sites. Easy plugin configuration and reconfiguration is the main value to demonstrate after the first observable proof.

If the selected path did not use plugin-managed Observability, add it first to establish the reusable plugin path. If Observability already produced the proof, ask what outcome matters next and recommend exactly one plugin:

  • Adaptive -> adaptive runtime behavior and optimization
  • NeMo Guardrails -> policy checks around managed execution
  • PII Redaction -> sanitization of sensitive observability payloads
  • Model Pricing -> cost estimates for managed LLM responses

Use the plugin overview to select the next component. Preview its smallest configuration, obtain confirmation, and verify its behavior before layering in another plugin.

Use another handoff only after the user accepts or declines plugin progression, or when the demonstrated boundary does not yet cover the intended workflow:

  • Direct application expansion -> nemo-relay-instrument-calls
  • Unsupported framework or harness integration -> nemo-relay-integrate-upstream
  • Additional exporters or durable observability configuration -> nemo-relay-plugin-observability
  • A different package or supported integration -> nemo-relay-install
  • Persistent Claude Code or Codex loading -> nemo-relay-install; for Codex Desktop, complete its recovery-note safety gate before changing global config
  • Missing hooks, gateway traffic, or events -> nemo-relay doctor, nemo-relay doctor --json, or nemo-relay-debug-runtime-integration

Do not configure production OTLP backends, model pricing, guardrails, adaptive tuning, custom plugins, Go or FFI examples during the quick start. Mention optional plugins only after the initial proof and add only the one the user selects.

Public Entry Points

Use these public entry points for current product documentation:

© 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 7 other files (references) in skills/nemo-relay-get-started of NVIDIA/NeMo-Relay.

  • SKILL.md
  • BENCHMARK.md
  • evals/evals.json
  • references/built-in-integrations-try-now.md
  • references/cli-try-now.md
  • references/manual-language-try-now.md
  • skill-card.md
  • skill.oms.sig

Open the folder on GitHubat commit 651453f

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in NVIDIA/NeMo-Relay, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Nemo Relay Get Started 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 Get Started compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nemo Relay Get Started this skillNVIDIA/NeMo-Relay190—~1.8kAutomated safety check: PassApache-2.0
Nemo Relay InstallNVIDIA/skills3.5k—~1.7kAutomated safety check: PassApache-2.0
CI Pipeline Synthesizerkajisho5/ffmpeg-skill1.9k1 repos~1.1kAutomated safety check: PassMIT
Examples Checkereclipse-ankaios/ankaios125—~2kAutomated safety check: PassApache-2.0
Universal Project Release WorkflowJimLiu/baoyu-skills26k—~4.9kAutomated safety check: PassMIT
Deploy To Tempsgotempsh/temps822—~1.3kAutomated safety check: NotesApache-2.0

Similar skills

  • 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 yesterday
    AI & LLM EngineeringAuto-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

  • Examples Checker

    eclipse-ankaios/ankaios

    Check Ankaios examples by building and running each example in the devcontainer and validating they work correctly.

    125 GitHub stars~2k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • Universal Project Release Workflow

    JimLiu/baoyu-skills

    Detects a project's version file and changelog format, then runs a release: bumping the version, writing release notes and creating GitHub releases, including backfill.

    26k GitHub stars~4.9k tokensUpdated 27 days ago
    DevelopmentAuto-check passed

  • Deploy To Temps

    gotempsh/temps

    Deploy applications to the Temps platform with automatic framework detection, Dockerfile generation, and container orchestration.

    822 GitHub stars~1.3k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Writing Dockerfiles

    ancoleman/ai-design-components

    Writing optimized, secure, multi-stage Dockerfiles with language-specific patterns (Python, Node.js, Go, Rust), BuildKit features, and distroless images.

    526 GitHub stars~3.2k tokensUpdated 10 mo ago
    DevOps & CloudAuto-check: notes

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.

    190 GitHub stars~575 tokensUpdated yesterday
    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…

    190 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

  • Add Middleware

    NVIDIA/NeMo-Relay

    Official

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

    190 GitHub stars~1.2k tokensUpdated yesterday
    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.

    190 GitHub stars~710 tokensUpdated yesterday
    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.

    190 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

  • Nemo Relay Install

    NVIDIA/NeMo-Relay

    Official

    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…

    190 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Nemo Relay Get Started

What does Nemo Relay Get Started do?

A skill your agent uses when first-time NeMo Relay users want to try Relay, choose the least-complex supported quick start, or verify initial value through the CLI, a maintained integration, or…. Nemo Relay Get Started is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization.js, or Rust instrumentation before production setup.

When should I use Nemo Relay Get Started?

Nemo Relay Get Started fits situations like: first-time NeMo Relay users want to try Relay; choose the least-complex supported quick start; verify initial value through the CLI; A maintained integration.

How do I install Nemo Relay Get Started in Claude Code?

Run `npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-get-started -a claude-code`. Or copy the skill folder (skills/nemo-relay-get-started in NVIDIA/NeMo-Relay) into .claude/skills/nemo-relay-get-started in your project. Claude Code loads it when a task matches its description.

How do I install Nemo Relay Get Started in Codex?

Run `npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-get-started -a codex`. Or copy the skill folder (skills/nemo-relay-get-started in NVIDIA/NeMo-Relay) into .agents/skills/nemo-relay-get-started in your project. Codex loads it when a task matches its description.

Can I use Nemo Relay Get Started 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-get-started -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-get-started, .gemini/skills/nemo-relay-get-started, .github/skills/nemo-relay-get-started and .opencode/skills/nemo-relay-get-started in your project.

What does Nemo Relay Get Started need to run?

SKILL.md names no scripts, command-line tools or credentials: Nemo Relay Get Started is instructions for the agent only. Our summary lists: Node.js.

Does Nemo Relay Get Started 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 Get Started 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 Get Started use?

Nemo Relay Get Started 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 Get Started use?

About 1.8k 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 4.2k tokens, read only when the agent opens those files.

What are the alternatives to Nemo Relay Get Started?

Skills that share tags, products or a category with Nemo Relay Get Started: Nemo Relay Install (NVIDIA/skills, 3.5k stars), CI Pipeline Synthesizer (kajisho5/ffmpeg-skill, 1.9k stars), Examples Checker (eclipse-ankaios/ankaios, 125 stars) and Universal Project Release Workflow (JimLiu/baoyu-skills, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nemo Relay Get Started?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/NeMo-Relay, which has 190 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 7, 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.