Agent skill · writing content · nvidia
nemo-relay-get-started
Use this skill when first-time NeMo Relay users want help selecting and following an appropriate quick-start guide or verifying their first working integration. Do not use it for production rollout or broad integration development.
Why this skill is useful
Provides specific guidance on using NeMo Relay with CLI, integrations, and language-specific implementations that the AI wouldn't reliably generate on its own.
What it needs
Requires nemo-relay installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/nemo-relay-get-started