Release Skills
nexmoe/eve
Universal release workflow. An agent skill from nexmoe/eve.
Add or change NeMo Relay packages, package metadata, module paths, generated artifacts, registry output, or release-facing build surfaces, including registering new unified-release surfaces with…
Install Maintain Packaging
$ npx skills add NVIDIA/NeMo-Relay --skill maintain-packaging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/NeMo-Relay maintain-packaging --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/maintain-packaging .claude/skills/maintain-packaging && 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 "maintain-packaging" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-packaging into .claude/skills/maintain-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-packaging", 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/maintain-packagingType 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 maintain-packaging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/NeMo-Relay maintain-packaging --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/maintain-packaging .agents/skills/maintain-packaging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "maintain-packaging" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-packaging into .agents/skills/maintain-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-packaging", 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 maintain-packaging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/NeMo-Relay maintain-packaging --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/maintain-packaging .cursor/skills/maintain-packaging && 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 "maintain-packaging" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-packaging into .cursor/skills/maintain-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-packaging", 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/maintain-packaging--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 maintain-packaging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/NeMo-Relay maintain-packaging --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/maintain-packaging .gemini/skills/maintain-packaging && 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 "maintain-packaging" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-packaging into .gemini/skills/maintain-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-packaging", 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 maintain-packagingInstalls 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 maintain-packaging -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/maintain-packaging .github/skills/maintain-packaging && 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 "maintain-packaging" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-packaging into .github/skills/maintain-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-packaging", 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 maintain-packaging -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 maintain-packaging --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/maintain-packaging .opencode/skills/maintain-packaging && 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 "maintain-packaging" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-packaging into .opencode/skills/maintain-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-packaging", 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
maintain-packaging- GitHub stars
- 192
- Token cost
- ~665 tokens
- SKILL.md length
- 277 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Add or change NeMo Relay packages, package metadata, module paths, generated artifacts, registry output, or release-facing build surfaces, including registering new unified-release surfaces with…
- A standalone project version bump
- SKILL.md covers Audit Areas, Checklist and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Ordinary source builds
What it does
Maintain Packaging is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Add or change NeMo Relay packages, package metadata, module paths, generated artifacts, registry output, or release-facing build surfaces, including registering new unified-release surfaces with version automation. Do not use for a standalone project version bump, ordinary source builds, or tests.
Its SKILL.md is about 670 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. It works with Python and 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
- A standalone project version bump
- Ordinary source builds
Example prompts
- “/maintain-packaging”
Requirements
- Python 3
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
Maintain Packaging loads about 665 tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 277 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). 277 words, ~665 tokens.
Download SKILL.mdSave it as
.claude/skills/maintain-packaging/SKILL.md (or your agent's skills folder).- name
- maintain-packaging
- description
- Add or change NeMo Relay packages, package metadata, module paths, generated artifacts, registry output, or release-facing build surfaces, including registering new unified-release surfaces with version automation. Do not use for a standalone project version bump, ordinary source builds, or tests.
- license
- Apache-2.0
Maintain Release And Packaging Surfaces
Use this skill when a change affects how NeMo Relay is built, packaged, named, or consumed outside the source tree.
Audit Areas
- Rust
Cargo.tomlpackage names and workspace metadata - Python packaging in
pyproject.toml - Python worker plugin SDK packaging in
python/plugin/pyproject.toml - Go module path in
go/nemo_relay/go.mod - Node workspace metadata in root
package.jsonandpackage-lock.json - Node package metadata in
crates/node/package.json - FFI header and library naming
- CI workflows, install commands, and example commands
justfilebuild, test, clean, version, and package recipes for plugin crates and packages- Release tags, release-note surfaces, and registry-facing version translation
Checklist
- Every new package or plugin has an explicit versioning model: either it participates in the unified NeMo Relay release or it has an intentionally independent source of truth
- Package names, import paths, and module names are internally consistent
- Generated artifacts still land where downstream consumers expect
- Docs and examples use the current install/import/build commands
- CI references the same package names as local workflows
- Public packaging changes are reflected in release-facing docs
- For a new unified-release surface, its manifest version, lockfile entry,
and internal NeMo Relay version pins are covered by
set_project_versionin thejustfile; extend the owning helper and its fail-fast field checks in the same change when a value is not derived automatically, without adding a separate test that mirrors the helper's field list -
nemo-relay-pluginRust and Python packages track the project SemVer policy and Python wheels use valid PEP 440 translation - Release tags still use raw SemVer without a leading
v - Release history and release notes still point to GitHub Releases, not
CHANGELOG.mdor docs pages
References
pyproject.tomlpython/plugin/pyproject.tomlgo/nemo_relay/go.modpackage.jsonpackage-lock.jsoncrates/node/package.jsonRELEASING.md.github/workflows/ci_python.yml.github/workflows/ci.yaml.gitlab-ci.ymljustfile
© 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/maintain-packaging of NVIDIA/NeMo-Relay.
Open the folder on GitHubat commit 16d73b4
Compare with similar skills
Maintain Packaging 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 |
|---|---|---|---|---|---|---|
| Maintain Packaging this skillNVIDIA/NeMo-Relay | 192 | — | ~665 | Automated safety check: Pass | Apache-2.0 | |
| Release Skillsnexmoe/eve | 421 | 3 repos | ~3.3k | Automated safety check: Pass | None | |
| RustPython C-API ExpansionRustPython/RustPython | 22k | — | ~831 | Automated safety check: Pass | MIT | |
| jscpd Code Migration Trackerkucherenko/jscpd | 6.4k | — | ~5k | Automated safety check: Pass | MIT | |
| RustPython Stdlib UpgradeRustPython/RustPython | 22k | — | ~876 | Automated safety check: Pass | MIT | |
| Rust Ffiariebovenberg/whenever | 2.4k | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
RustPython C-API Expansion
RustPython/RustPython
Implements missing CPython C-API functions in RustPython's crates/capi, mapping each header to its module with the pyo3-ffi header split.
jscpd Code Migration Tracker
kucherenko/jscpd
Measures a code port between languages or frameworks with jscpd's function-level comparison, porting tests before code and tracking what is left unmatched.
RustPython Stdlib Upgrade
RustPython/RustPython
Upgrades a Python standard library module from CPython into RustPython with update_lib, then triages and marks the tests that still fail.
Rust Ffi
ariebovenberg/whenever
Instructions for using whenever's internal Rust FFI abstractions
Samply
vortex-data/vortex
Analyze Samply Firefox-profiler output, record focused profiles, summarize hot threads/stacks, inspect symbolication, and compare profile evidence before and after a performance change.
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
Categories
Questions about Maintain Packaging
What does Maintain Packaging do?
Add or change NeMo Relay packages, package metadata, module paths, generated artifacts, registry output, or release-facing build surfaces, including registering new unified-release surfaces with…. Maintain Packaging is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Add or change NeMo Relay packages, package metadata, module paths, generated artifacts, registry output, or release-facing build surfaces, including registering new unified-release surfaces with version automation.
When should I use Maintain Packaging?
Maintain Packaging fits situations like: A standalone project version bump; ordinary source builds.
How do I install Maintain Packaging in Claude Code?
Run `npx skills add NVIDIA/NeMo-Relay --skill maintain-packaging -a claude-code`. Or copy the skill folder (.agents/skills/maintain-packaging in NVIDIA/NeMo-Relay) into .claude/skills/maintain-packaging in your project. Claude Code loads it when a task matches its description.
How do I install Maintain Packaging in Codex?
Run `npx skills add NVIDIA/NeMo-Relay --skill maintain-packaging -a codex`. Or copy the skill folder (.agents/skills/maintain-packaging in NVIDIA/NeMo-Relay) into .agents/skills/maintain-packaging in your project. Codex loads it when a task matches its description.
Can I use Maintain Packaging 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 maintain-packaging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maintain-packaging, .gemini/skills/maintain-packaging, .github/skills/maintain-packaging and .opencode/skills/maintain-packaging in your project.
What does Maintain Packaging need to run?
SKILL.md names no scripts, command-line tools or credentials: Maintain Packaging is instructions for the agent only. Our summary lists: Python 3.
Does Maintain Packaging 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 Maintain Packaging 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 Maintain Packaging use?
Maintain Packaging 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 Maintain Packaging use?
About 665 tokens (SKILL.md is roughly 2.7k 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 Maintain Packaging?
Skills that share tags, products or a category with Maintain Packaging: Release Skills (nexmoe/eve, 421 stars), RustPython C-API Expansion (RustPython/RustPython, 22k stars), jscpd Code Migration Tracker (kucherenko/jscpd, 6.4k stars) and RustPython Stdlib Upgrade (RustPython/RustPython, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Maintain Packaging?
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.