Official agent skill

Rename Surfaces

Rename a NeMo Relay repository, package, crate, module, public symbol, import path, or brand surface across multiple consumers.

OfficialApache-2.0Auto-check passed

Install Rename Surfaces

skills CLI

$ npx skills add NVIDIA/NeMo-Relay --skill rename-surfaces -a claude-code

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

GitHub CLI

$ gh skill install NVIDIA/NeMo-Relay rename-surfaces --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/.agents/skills/rename-surfaces .claude/skills/rename-surfaces && 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/

Paste into Claude Code

Install the "rename-surfaces" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/rename-surfaces into .claude/skills/rename-surfaces/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rename-surfaces", 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

$skill-installer install https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/rename-surfaces

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

skills CLI

$ npx skills add NVIDIA/NeMo-Relay --skill rename-surfaces -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install NVIDIA/NeMo-Relay rename-surfaces --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/rename-surfaces .agents/skills/rename-surfaces && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "rename-surfaces" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/rename-surfaces into .agents/skills/rename-surfaces/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rename-surfaces", 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.

skills CLI

$ npx skills add NVIDIA/NeMo-Relay --skill rename-surfaces -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install NVIDIA/NeMo-Relay rename-surfaces --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/rename-surfaces .cursor/skills/rename-surfaces && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "rename-surfaces" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/rename-surfaces into .cursor/skills/rename-surfaces/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rename-surfaces", 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

$ gemini skills install https://github.com/NVIDIA/NeMo-Relay.git --path .agents/skills/rename-surfaces

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add NVIDIA/NeMo-Relay --skill rename-surfaces -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install NVIDIA/NeMo-Relay rename-surfaces --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/rename-surfaces .gemini/skills/rename-surfaces && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "rename-surfaces" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/rename-surfaces into .gemini/skills/rename-surfaces/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rename-surfaces", 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.

GitHub CLI

$ gh skill install NVIDIA/NeMo-Relay rename-surfaces

Installs 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).

skills CLI

$ npx skills add NVIDIA/NeMo-Relay --skill rename-surfaces -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/rename-surfaces .github/skills/rename-surfaces && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "rename-surfaces" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/rename-surfaces into .github/skills/rename-surfaces/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rename-surfaces", 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.

skills CLI

$ npx skills add NVIDIA/NeMo-Relay --skill rename-surfaces -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install NVIDIA/NeMo-Relay rename-surfaces --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/rename-surfaces .opencode/skills/rename-surfaces && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "rename-surfaces" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/rename-surfaces into .opencode/skills/rename-surfaces/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rename-surfaces", 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: rename-surfaces
GitHub stars: 192
Token cost: ~390 tokens
SKILL.md length: 164 words
Files: 1
Skills in repo: 30
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Rename a NeMo Relay repository, package, crate, module, public symbol, import path, or brand surface across multiple consumers.

A file-local private rename
SKILL.md covers Rename Buckets To Audit, Rules, Checklist and References
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Rename Surfaces is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Rename a NeMo Relay repository, package, crate, module, public symbol, import path, or brand surface across multiple consumers. Do not use for a file-local private rename.

Its SKILL.md is about 390 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

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

A file-local private rename

Example prompts

“/rename-surfaces”

Requirements

Python 3

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

Rename Surfaces loads about 390 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 164 words of instructions outside code blocks.

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

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). 164 words, ~390 tokens.

Download SKILL.mdSave it as .claude/skills/rename-surfaces/SKILL.md (or your agent's skills folder).

name: rename-surfaces
description: Rename a NeMo Relay repository, package, crate, module, public symbol, import path, or brand surface across multiple consumers. Do not use for a file-local private rename.
license: Apache-2.0

Perform A Repo Rename Or Surface Rename

Use this skill for coordinated naming changes such as repository renames, crate prefix changes, package/module renames, import-path changes, FFI symbol renames, or branding text updates that must preserve functional identifiers.

Rename Buckets To Audit

Repository references
Rust crate names and module prefixes
Python package name and top-level module
Go module path and package paths
Node package names
C header names and symbol prefixes
Docs, examples, CI, and integration packages

Rules

Separate branding text from functional identifiers.
Preserve repository and import paths exactly where code depends on them.
Update generated or generated-from-build surfaces such as crates/ffi/nemo_relay.h through the proper build step.
Search for old names after the rename and validate every public language surface.

Checklist

Manifests updated
Source imports and symbol names updated
Docs and examples updated
Integration packages and scripts updated
No stale old names remain in tracked files where they would break behavior
Every surface changed by the rename has focused validation

References

README.md
docs/getting-started/quick-start/index.mdx
docs/reference/api/index.mdx

Files

Just SKILL.md in .agents/skills/rename-surfaces of NVIDIA/NeMo-Relay.

Open the folder on GitHubat commit 804d570

Compare with similar skills

Rename Surfaces 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.

Rename Surfaces compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Rename Surfaces this skillNVIDIA/NeMo-Relay	192	—	~390	Automated safety check: Pass	Apache-2.0	today
Nemo Relay InstallNVIDIA/skills	3.5k	—	~1.7k	Automated safety check: Pass	Apache-2.0	today
Workspace Surface Auditaffaan-m/ECC	276k	3 repos	~1.3k	Automated safety check: Notes	MIT	4 days ago
Es Modulesthedaviddias/Front-End-Checklist	74k	—	~482	Automated safety check: Pass	MIT	2 days ago
Splitting Oversized ModulesPostHog/posthog	40k	—	~2.2k	Automated safety check: Pass	Custom licence	today
Abp Moduleabpframework/abp	14k	—	~1.6k	Automated safety check: Pass	LGPL-3.0	today

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 today
AI & LLM EngineeringAuto-check passed
Workspace Surface Audit
affaan-m/ECC
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows.
276k GitHub starsUsed in 3 repos~1.3k tokens
Agent WorkflowsAuto-check: notes
Es Modules
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Use ES modules (import/export).
74k GitHub stars~482 tokensUpdated 2 days ago
Auto-check passed
Splitting Oversized Modules
PostHog/posthog
Official
Split an oversized Python module (a thousand-plus-line logic.py, models.py, api.py, or its test file) into a package of one module per concern, mechanically and provably without changing behavior.
40k GitHub stars~2.2k tokensUpdated today
Frontend & DesignAuto-check passed
Abp Module
abpframework/abp
ABP reusable Module solution template - EF Core + MongoDB dual support, virtual methods for extensibility, DbTablePrefix, module options pattern, entity extension, separate connection string.
14k GitHub stars~1.6k tokensUpdated today
DatabasesAuto-check passed
Surface
srid/emanote
How a downstream app consumes the shared @kolu/surface stack (@kolu/surface · surface-app · surface-nix-host · surface-mcp) — declaring a typed reactive surface, serving it, consuming it (SolidJS…
963 GitHub stars~1.5k tokensUpdated 2 mo ago
Auto-check passed

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 today
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 today
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 today
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 today
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 today
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 today
Auto-check passed

Questions about Rename Surfaces

What does Rename Surfaces do?

Rename a NeMo Relay repository, package, crate, module, public symbol, import path, or brand surface across multiple consumers. Rename Surfaces is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Rename a NeMo Relay repository, package, crate, module, public symbol, import path, or brand surface across multiple consumers.

When should I use Rename Surfaces?

Rename Surfaces fits situations like: A file-local private rename.

How do I install Rename Surfaces in Claude Code?

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

How do I install Rename Surfaces in Codex?

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

Can I use Rename Surfaces 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 rename-surfaces -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rename-surfaces, .gemini/skills/rename-surfaces, .github/skills/rename-surfaces and .opencode/skills/rename-surfaces in your project.

What does Rename Surfaces need to run?

SKILL.md names no scripts, command-line tools or credentials: Rename Surfaces is instructions for the agent only. Our summary lists: Python 3.

Does Rename Surfaces 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 Rename Surfaces 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 Rename Surfaces use?

Rename Surfaces 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 Rename Surfaces use?

About 390 tokens (SKILL.md is roughly 1.6k 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 Rename Surfaces?

Skills that share tags, products or a category with Rename Surfaces: Nemo Relay Install (NVIDIA/skills, 3.5k stars), Workspace Surface Audit (affaan-m/ECC, 276k stars), Es Modules (thedaviddias/Front-End-Checklist, 74k stars) and Splitting Oversized Modules (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rename Surfaces?

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.

Install Rename Surfaces

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Perform A Repo Rename Or Surface Rename

Rename Buckets To Audit

Rules

Checklist

References

Files

Compare with similar skills

Similar skills

More from NVIDIA/NeMo-Relay

Questions about Rename Surfaces