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 Instrument Typed Wrappers

by NVIDIA in NVIDIA/NeMo-Relay

A skill your agent uses when adding NeMo Relay typed wrappers, domain types, or provider codecs while preserving JSON middleware semantics and caller-visible behavior.

OfficialApache-2.0Auto-check passed

Install Nemo Relay Instrument Typed Wrappers

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

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

GitHub CLI
$ gh skill install NVIDIA/NeMo-Relay nemo-relay-instrument-typed-wrappers --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-instrument-typed-wrappers .claude/skills/nemo-relay-instrument-typed-wrappers && 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-instrument-typed-wrappers
GitHub stars
192
Token cost
~1.1k tokens
SKILL.md length
511 words
Files
5
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when adding NeMo Relay typed wrappers, domain types, or provider codecs while preserving JSON middleware semantics and caller-visible behavior.

  • Adding NeMo Relay typed wrappers
  • SKILL.md covers Default Guidance, Embedded Codec Model, Key Rules and Choose A Codec, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Provider codecs while preserving JSON middleware semantics and caller-visible behavior

What it does

Nemo Relay Instrument Typed Wrappers is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Use this skill when adding NeMo Relay typed wrappers, domain types, or provider codecs while preserving JSON middleware semantics and caller-visible behavior.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `BENCHMARK.md`, `evals/evals.json` and `skill-card.md`).

It works with 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

  • Adding NeMo Relay typed wrappers
  • Provider codecs while preserving JSON middleware semantics and caller-visible behavior

Example prompts

  • “/nemo-relay-instrument-typed-wrappers”

Requirements

  • Python 3
  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit 804d570. 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

    No URLs in SKILL.md.

    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 Instrument Typed Wrappers loads about 1.1k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 511 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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 804d570, republished under its Apache-2.0 licence (© NVIDIA). 511 words, ~1,103 tokens.

Download SKILL.mdSave it as .claude/skills/nemo-relay-instrument-typed-wrappers/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
nemo-relay-instrument-typed-wrappers
description
Use this skill when adding NeMo Relay typed wrappers, domain types, or provider codecs while preserving JSON middleware semantics and caller-visible behavior.
license
Apache-2.0
metadata.author
NVIDIA Corporation and Affiliates

Use Typed Wrappers And Codecs

Use this skill when an application wants stronger domain types than raw JSON for tool or LLM integration. Keep typed boundaries explicit so middleware still sees predictable JSON.

Default Guidance

  • Prefer plain JSON first for initial adoption.
  • Reach for typed wrappers when the application already has stable domain models.
  • Keep in mind that middleware still operates on JSON, not typed objects.

Embedded Codec Model

  • A typed value codec is a pure boundary translator. It converts application-facing values to JSON before NeMo Relay emits events or runs middleware, then converts JSON back into the framework callback or caller type.
  • Python exposes JsonPassthrough, DataclassCodec, PydanticCodec, and BestEffortAnyCodec. Node.js exposes JsonPassthrough plus custom Codec<T> implementations.
  • Use BestEffortAnyCodec only at boundaries where strict schemas are not available. Prefer dataclass, Pydantic, or explicit Node.js codecs when the framework owns a stable schema.
  • Provider codecs are different from typed value codecs: they normalize provider-specific LLM requests and responses so middleware and subscribers can inspect messages, tools, model names, generation parameters, and response annotations.
  • Built-in provider codecs include OpenAIChatCodec, OpenAIResponsesCodec, and AnthropicMessagesCodec in Python, Node.js, and Rust. Choose the codec that matches the actual provider payload shape.
  • Response codecs annotate LLM end events with fields such as id, model, message, tool_calls, finish_reason, usage, provider-specific data, and extra unmodeled fields. They do not rewrite the caller-visible response.
  • Request codecs run before LLM request intercepts. Intercepts receive both the raw LLMRequest and optional annotated request; encode merges annotated edits back before execution intercepts and the provider callback run.
  • Built-in request codecs guarantee JSON-value identity for an unchanged annotation. They compare edits with a decoded baseline and patch only changed fields, preserving native representation details and unknown fields.
  • Use instructions, portable messages and components, and the tagged api_specific request surface for normalized edits. Provider-only union members use explicit { provider, kind, value } native components. Reserve top-level extra for unknown future fields.
  • The nemo-relay gateway always supplies matching request codecs on Anthropic Messages, OpenAI Chat Completions, and OpenAI Responses generation routes. On those routes, treat raw request.content as read-only and return body edits through the annotated request. Header edits still use the raw request.
Show full SKILL.md (154 more words)Show less

Key Rules

  • Typed wrappers are currently a first-class path for Python and Node.js; Rust uses codec traits directly
  • Request/response conversion belongs in codecs
  • Intercepts and guardrails see JSON values after encoding
  • Changes made by middleware survive into the decode step

Choose A Codec

  • JsonPassthrough for JSON-native values
  • DataclassCodec or PydanticCodec in Python when the models already exist
  • Custom codecs for domain-specific wire shapes
  • BestEffortAnyCodec only when broad flexibility is worth the looser contract
  • Provider codecs for LLM provider payloads, not application domain objects conversion

Validation Checklist

  • Codec output is JSON-compatible
  • Required fields survive toJson/fromJson or decode/encode
  • Middleware sees the expected serialized shape
  • Provider codecs preserve fields they do not understand
  • Response codec failures do not break the underlying LLM call
  • Request codec encode preserves original provider fields unless an intercept intentionally changes them
  • Provider-native components belong to the codec's provider surface
  • Gateway generation intercepts do not mutate raw request.content
  • nemo-relay-instrument-calls
  • nemo-relay-plugin-observability
  • nemo-relay-debug-runtime-integration

© 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 4 other files in skills/nemo-relay-instrument-typed-wrappers of NVIDIA/NeMo-Relay.

  • SKILL.md
  • BENCHMARK.md
  • evals/evals.json
  • skill-card.md
  • skill.oms.sig

Open the folder on GitHubat commit 804d570

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 Instrument Typed Wrappers 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 Instrument Typed Wrappers compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nemo Relay Instrument Typed Wrappers this skillNVIDIA/NeMo-Relay192—~1.1kAutomated safety check: PassApache-2.0
Web Access via Browser CDPeze-is/web-access9.1k4 repos~2.2kAutomated safety check: PassMIT
Knap Markdown Templateskepano/obsidian-skills49k2 repos~986Automated safety check: PassMIT
Chart Visualizationbytedance/deer-flow84k1 repos~840Automated safety check: PassMIT
Electron Multi-Process ArchitectureiOfficeAI/AionUi33k1 repos~1.8kAutomated safety check: PassApache-2.0
Chrome CDP Browser Controlzenstory-ai/oh-story-claudecode7.4k2 repos~1.2kAutomated safety check: PassMIT

Similar skills

  • Web Access via Browser CDP

    eze-is/web-access

    Routes every web task, from searching to logged-in browsing, through a tiered choice of search, fetch, curl or a real Chrome or Edge session driven over CDP.

    9.1k GitHub starsUsed in 4 repos~2.2k tokens
    Productivity & AutomationAuto-check passed

  • Knap Markdown Templates

    kepano/obsidian-skills

    Renders Markdown notes from Knap templates and JSON data on the command line, including notes built from Defuddle web page output.

    49k GitHub starsUsed in 2 repos~986 tokens
    Documents & OfficeAuto-check passed

  • Chart Visualization

    bytedance/deer-flow

    Picks a suitable chart type from 26 options for your data, maps the data to that chart's parameters and generates a chart image through a JavaScript script.

    84k GitHub starsUsed in 1 repo~840 tokens
    Data & AnalyticsAuto-check passed

  • Electron Multi-Process Architecture

    iOfficeAI/AionUi

    Tells the agent where new code belongs in an Electron multi-process project and which APIs each process may use, with rules for new bridges, services, agents and workers.

    33k GitHub starsUsed in 1 repo~1.8k tokens
    DevelopmentAuto-check passed

  • Chrome CDP Browser Control

    zenstory-ai/oh-story-claudecode

    Drives a Chrome window over the DevTools Protocol with the agent-browser CLI, so the agent can reuse your logged-in sessions, read pages and pull tokens.

    7.4k GitHub starsUsed in 2 repos~1.2k tokens
    Productivity & AutomationAuto-check passed

  • DeerFlow Smoke Test

    bytedance/deer-flow

    Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.

    84k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-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.

    192 GitHub stars~575 tokensUpdated 2 days ago
    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 2 days ago
    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 2 days ago
    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 2 days ago
    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 2 days ago
    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…

    192 GitHub stars~1.7k tokensUpdated 2 days ago
    Auto-check passed

Works with

Questions about Nemo Relay Instrument Typed Wrappers

What does Nemo Relay Instrument Typed Wrappers do?

A skill your agent uses when adding NeMo Relay typed wrappers, domain types, or provider codecs while preserving JSON middleware semantics and caller-visible behavior. Nemo Relay Instrument Typed Wrappers is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Use this skill when adding NeMo Relay typed wrappers, domain types, or provider codecs while preserving JSON middleware semantics and caller-visible behavior.

When should I use Nemo Relay Instrument Typed Wrappers?

Nemo Relay Instrument Typed Wrappers fits situations like: adding NeMo Relay typed wrappers; provider codecs while preserving JSON middleware semantics and caller-visible behavior.

How do I install Nemo Relay Instrument Typed Wrappers in Claude Code?

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

How do I install Nemo Relay Instrument Typed Wrappers in Codex?

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

Can I use Nemo Relay Instrument Typed Wrappers 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-instrument-typed-wrappers -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-instrument-typed-wrappers, .gemini/skills/nemo-relay-instrument-typed-wrappers, .github/skills/nemo-relay-instrument-typed-wrappers and .opencode/skills/nemo-relay-instrument-typed-wrappers in your project.

What does Nemo Relay Instrument Typed Wrappers need to run?

SKILL.md names no scripts, command-line tools or credentials: Nemo Relay Instrument Typed Wrappers is instructions for the agent only. Our summary lists: Python 3; Node.js.

Does Nemo Relay Instrument Typed Wrappers access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Nemo Relay Instrument Typed Wrappers 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 Instrument Typed Wrappers use?

Nemo Relay Instrument Typed Wrappers 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 Instrument Typed Wrappers use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nemo Relay Instrument Typed Wrappers?

Skills that share tags, products or a category with Nemo Relay Instrument Typed Wrappers: Web Access via Browser CDP (eze-is/web-access, 9.1k stars), Knap Markdown Templates (kepano/obsidian-skills, 49k stars), Chart Visualization (bytedance/deer-flow, 84k stars) and Electron Multi-Process Architecture (iOfficeAI/AionUi, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nemo Relay Instrument Typed Wrappers?

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 9, 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.