Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
Add or change a public NeMo Relay runtime API across Rust and affected language bindings when no more specific maintainer skill owns the domain.
Install Add Binding Feature
$ npx skills add NVIDIA/NeMo-Relay --skill add-binding-feature -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/NeMo-Relay add-binding-feature --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/add-binding-feature .claude/skills/add-binding-feature && rm -rf skills-srcUse ~/.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/
Install the "add-binding-feature" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/add-binding-feature into .claude/skills/add-binding-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-binding-feature", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/add-binding-featureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NVIDIA/NeMo-Relay --skill add-binding-feature -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/NeMo-Relay add-binding-feature --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/add-binding-feature .agents/skills/add-binding-feature && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "add-binding-feature" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/add-binding-feature into .agents/skills/add-binding-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-binding-feature", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/NeMo-Relay --skill add-binding-feature -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/NeMo-Relay add-binding-feature --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/add-binding-feature .cursor/skills/add-binding-feature && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "add-binding-feature" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/add-binding-feature into .cursor/skills/add-binding-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-binding-feature", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NVIDIA/NeMo-Relay.git --path .agents/skills/add-binding-feature--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NVIDIA/NeMo-Relay --skill add-binding-feature -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/NeMo-Relay add-binding-feature --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/add-binding-feature .gemini/skills/add-binding-feature && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "add-binding-feature" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/add-binding-feature into .gemini/skills/add-binding-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-binding-feature", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NVIDIA/NeMo-Relay add-binding-featureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NVIDIA/NeMo-Relay --skill add-binding-feature -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/add-binding-feature .github/skills/add-binding-feature && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "add-binding-feature" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/add-binding-feature into .github/skills/add-binding-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-binding-feature", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/NeMo-Relay --skill add-binding-feature -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA/NeMo-Relay add-binding-feature --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/add-binding-feature .opencode/skills/add-binding-feature && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "add-binding-feature" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/add-binding-feature into .opencode/skills/add-binding-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-binding-feature", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
add-binding-feature- GitHub stars
- 192
- Token cost
- ~1.1k tokens
- SKILL.md length
- 457 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Add or change a public NeMo Relay runtime API across Rust and affected language bindings when no more specific maintainer skill owns the domain.
- Works in 6 steps: Core Rust → FFI / shared C surface, when affected → Language-native bindings → …
- Middleware additions
- SKILL.md covers Implementation Order, Naming Conventions, Parity Checklist and Decision Points, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Add Binding Feature is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Add or change a public NeMo Relay runtime API across Rust and affected language bindings when no more specific maintainer skill owns the domain. Do not use for middleware additions, internal refactors, binding-local fixes, or docs-only changes.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Refactoring. It works with Rust. 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
- Middleware additions
- Internal refactors
- Binding-local fixes
- Docs-only changes
Example prompts
- “/add-binding-feature”
Requirements
- Python 3
- Node.js
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Core Rust
- FFI / shared C surface, when affected
- Language-native bindings
- Language wrapper helpers
- Docs and examples
- Validation
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
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
Add Binding Feature loads about 1.1k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 457 words of instructions outside code blocks.
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). 457 words, ~1,132 tokens.
Download SKILL.mdSave it as
.claude/skills/add-binding-feature/SKILL.md (or your agent's skills folder).- name
- add-binding-feature
- description
- Add or change a public NeMo Relay runtime API across Rust and affected language bindings when no more specific maintainer skill owns the domain. Do not use for middleware additions, internal refactors, binding-local fixes, or docs-only changes.
- license
- Apache-2.0
Add a Binding Feature
Use this skill when a change affects the public runtime surface and must stay in parity across the Rust core, FFI, and one or more bindings.
Do not use this skill for:
- Internal-only core refactors with no public API change
- New middleware contracts, which use the middleware-specific workflow
- Binding-local bug fixes that do not change shared behavior
- Docs-only or example-only updates
Implementation Order
- Core Rust
Implement the behavior first in
crates/core/src/api/and related core modules such ascrates/core/src/api/runtime/,crates/core/src/codec/, orcrates/core/src/json.rs. - FFI / shared C surface, when affected
Update
crates/ffiand its generated header only when the capability is exposed through the C ABI or Go binding. - Language-native bindings Update each binding that exposes the capability; leave unrelated bindings unchanged.
- Language wrapper helpers Update Python wrapper modules, Go shorthand packages, typed helpers, or adaptive/plugin helpers if the new behavior belongs there.
- Docs and examples Update reference docs, language-binding docs, and examples when the public surface or expected usage changed.
- Validation Follow the repository validation policy for the surfaces whose public or observable behavior changed.
Naming Conventions
| Layer | Convention | Example |
|---|---|---|
| Rust | snake_case | nemo_relay_tool_call |
| C FFI | nemo_relay_ prefix | nemo_relay_tool_call |
| Python | snake_case | nemo_relay.tools.call |
| Go | PascalCase | nemo_relay.ToolCall |
| Node.js | camelCase | toolCall |
Parity Checklist
- Core function with doc comment in
crates/core/src/api/ - Runtime callback/state, codec, JSON, or event/tool/LLM/scope types added in the relevant core module if needed
- FFI wrapper and generated header updated if the C ABI changes
- Python native binding, wrapper, docstring, and stubs updated if exposed
- Go wrapper and shorthand package updated if the experimental Go surface exposes the capability
- Node.js native binding and wrapper updated if exposed
- Typed wrapper or adaptive/plugin helper surfaces updated when applicable
- Meaningful tests added in every affected language surface
- SPDX license header on any new files
- Relevant pages under
docs/reference/updated -
README.md,docs/getting-started/, or binding-level READMEs updated if behavior differs by language - Relevant getting-started, README, or example docs updated if usage changed
Show full SKILL.md (135 more words)Show less
Decision Points
Lock these before implementing:
- Which bindings actually expose the new surface?
- Is the change part of the plain JSON API, typed wrappers, adaptive/plugin helpers, or observability helpers?
- Does the new API need manual lifecycle and managed execute variants, or only one of them?
- Does the new behavior change event fields, metadata, or scope expectations?
- If tool execution is affected, does every callback, continuation, managed
return, and manual end surface use the canonical
ToolExecutionResultcontract and preserve its opaque annotation? - Are docs/examples required because the intended usage changed?
Key References
- Architecture:
docs/about-nemo-relay/architecture.mdx - Reference index:
docs/reference/api/index.mdx - Getting started and binding status:
README.md,docs/getting-started/quick-start/index.mdx,docs/reference/support-matrix.mdx - Typed wrappers and codecs:
docs/integrate-into-frameworks/using-codecs.mdx,docs/integrate-into-frameworks/provider-codecs.mdx - Adaptive config/plugins:
docs/configure-plugins/about.mdx,docs/build-plugins/about.mdx,docs/configure-plugins/adaptive/configuration.mdx - Existing pattern: follow a surface already implemented across core, FFI, Python, Go, and Node.js rather than inventing a new shape
© 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
Just SKILL.md in .agents/skills/add-binding-feature of NVIDIA/NeMo-Relay.
Open the folder on GitHubat commit 16d73b4
Compare with similar skills
Add Binding Feature 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Add Binding Feature this skillNVIDIA/NeMo-Relay | 192 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Rust Best Practicesfarm-fe/farm | 5.6k | 3 repos | ~1.1k | Automated safety check: Pass | MIT | |
| RTK Rust Design Patternsrtk-ai/rtk | 83k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| RTK Rust Code Simplifierrtk-ai/rtk | 83k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Rust Hygiene Audittsz-org/tsz | 577 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
RTK Rust Design Patterns
rtk-ai/rtk
Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.
RTK Rust Code Simplifier
rtk-ai/rtk
Reviews RTK's Rust code for over-engineering and verbose patterns, applying idioms like iterator chains and early returns while protecting a specific list of constraints from being simplified away.
Rust Hygiene Audit
tsz-org/tsz
Run a deep DRY + code-hygiene audit of the Rust workspace and turn the findings into verified, deduplicated, hierarchical GitHub tech-debt issues.
Coding Agent
mastra-ai/mastra
Authoring playbook for building agents that write, edit, review, or refactor code.
More from NVIDIA/NeMo-Relay
All 30 skills in this repo- Official
Draft Release Notes
NVIDIA/NeMo-Relay
Compare NeMo Relay release refs and draft the current documentation release-notes page from verified repository evidence.
- Official
Nemo Relay Migrate From Flow
NVIDIA/NeMo-Relay
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…
- Official
Add Middleware
NVIDIA/NeMo-Relay
Add a new NeMo Relay guardrail or intercept type, registration surface, or pipeline stage.
- Official
Contribute Docs
NVIDIA/NeMo-Relay
Author or edit NeMo Relay documentation or examples when repository-specific MDX, public API, integration, or release-history conventions matter.
- Official
Maintain CI
NVIDIA/NeMo-Relay
Change or review NeMo Relay GitHub Actions workflows where permissions, pinned actions, caching, reusable workflows, or release gates require repository-specific handling.
- Official
Nemo Relay Install
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…
Related
Works with
Categories
Questions about Add Binding Feature
What does Add Binding Feature do?
Add or change a public NeMo Relay runtime API across Rust and affected language bindings when no more specific maintainer skill owns the domain. Add Binding Feature is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Add or change a public NeMo Relay runtime API across Rust and affected language bindings when no more specific maintainer skill owns the domain.
When should I use Add Binding Feature?
Add Binding Feature fits situations like: middleware additions; internal refactors; binding-local fixes; docs-only changes.
How do I install Add Binding Feature in Claude Code?
Run `npx skills add NVIDIA/NeMo-Relay --skill add-binding-feature -a claude-code`. Or copy the skill folder (.agents/skills/add-binding-feature in NVIDIA/NeMo-Relay) into .claude/skills/add-binding-feature in your project. Claude Code loads it when a task matches its description.
How do I install Add Binding Feature in Codex?
Run `npx skills add NVIDIA/NeMo-Relay --skill add-binding-feature -a codex`. Or copy the skill folder (.agents/skills/add-binding-feature in NVIDIA/NeMo-Relay) into .agents/skills/add-binding-feature in your project. Codex loads it when a task matches its description.
Can I use Add Binding Feature 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 add-binding-feature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-binding-feature, .gemini/skills/add-binding-feature, .github/skills/add-binding-feature and .opencode/skills/add-binding-feature in your project.
What does Add Binding Feature need to run?
SKILL.md names no scripts, command-line tools or credentials: Add Binding Feature is instructions for the agent only. Our summary lists: Python 3; Node.js.
Does Add Binding Feature 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 Add Binding Feature 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 Add Binding Feature use?
Add Binding Feature 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 Add Binding Feature use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Add Binding Feature?
Skills that share tags, products or a category with Add Binding Feature: Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Rust Best Practices (farm-fe/farm, 5.6k stars), RTK Rust Design Patterns (rtk-ai/rtk, 83k stars) and RTK Rust Code Simplifier (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Add Binding Feature?
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.