Agent skill · NVIDIA

nemo-relay-get-started

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.

What it needs

About 4k tokens when loaded.

What this skill does

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. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills NVIDIA/nemo-relay-get-started

View the source on GitHub

Browse the @skills marketplace