Official agent skill

Create Release Tag

Create and push a signed, annotated NeMo Relay stable tag, then prepare an unpublished GitHub Release draft for review.

OfficialApache-2.0Auto-check passedDevelopment

Install Create Release Tag

skills CLI

$ npx skills add NVIDIA/NeMo-Relay --skill create-release-tag -a claude-code

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

GitHub CLI

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

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 create-release-tag -a codex

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

GitHub CLI

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

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

GitHub CLI

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

--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 create-release-tag -a gemini-cli

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

GitHub CLI

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

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

At a glance

Create and push a signed, annotated NeMo Relay stable tag, then prepare an unpublished GitHub Release draft for review.

Cutting a stable release
Calls git and gh
Release-candidate tags

What it does

Create Release Tag is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Create and push a signed, annotated NeMo Relay stable tag, then prepare an unpublished GitHub Release draft for review. Use when cutting a stable release; not for beta or release-candidate tags.

Its SKILL.md is about 830 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 GitHub and NVIDIA AI Platform. 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

Cutting a stable release
Release-candidate tags

Example prompts

“/create-release-tag”

What it can do on your machine

Read from SKILL.md and the folder at commit 651453f. 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
Shell commands in SKILL.md call:
- git
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
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

Create Release Tag loads about 827 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 276 words of instructions outside code blocks.

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

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 651453f, republished under its Apache-2.0 licence (© NVIDIA). 276 words, ~827 tokens.

Download SKILL.mdSave it as .claude/skills/create-release-tag/SKILL.md (or your agent's skills folder).

name: create-release-tag
description: Create and push a signed, annotated NeMo Relay stable tag, then prepare an unpublished GitHub Release draft for review. Use when cutting a stable release; not for beta or release-candidate tags.
license: Apache-2.0

Create a Release Tag

Require an explicit stable version in exact <major>.<minor>.<patch> form. Do not infer it from metadata or a branch name, and do not edit package metadata while tagging. The matching release/<major>.<minor> branch must exist on upstream; Relay stable tags are raw SemVer, for example 0.9.0, without v.

Before the destructive tag push, require explicit approval. Preserve user changes: do not stash, discard, or switch away from a dirty checkout. Fetch the release branch and tags, require HEAD to equal the upstream release branch, and require the workspace version to equal the requested version. Verify both local and remote tags are absent, create a signed annotated tag, verify it with git tag -v, and push only refs/tags/<tag>. Stop on any failed check; never force-update, replace, or delete tags.

After a successful push, create a GitHub Release only when the user explicitly authorizes the draft. Use the prior published stable release returned by GitHub, read the release-notes content at the new tag, and use draft-release-notes evidence only to verify claims. Prepare TITLE and NOTES_FILE, then create the draft with the command below. Present its URL for review; publishing is a separate action.

Create and Verify the Tag

Use upstream for NVIDIA/NeMo-Relay. Before requesting push approval, use the following checks with the user-provided VERSION:

bash

VERSION=<major.minor.patch>
RELEASE_BRANCH="release/$(printf '%s' "$VERSION" | cut -d. -f1,2)"
git ls-remote --exit-code --heads upstream "refs/heads/$RELEASE_BRANCH"
git fetch upstream "$RELEASE_BRANCH" --tags
test -z "$(git status --porcelain)"
git switch "$RELEASE_BRANCH"
git pull --ff-only --signoff upstream "$RELEASE_BRANCH"
test -z "$(git status --porcelain)"
test "$(git rev-parse HEAD)" = "$(git rev-parse "upstream/$RELEASE_BRANCH")"
test "$(sed -nE 's/^version = "([^"]+)"$/\1/p' Cargo.toml | head -1)" = "$VERSION"
! git rev-parse --verify --quiet "refs/tags/$VERSION"
if git ls-remote --exit-code --tags upstream "refs/tags/$VERSION" >/dev/null; then
  echo "Error: tag already exists on upstream" >&2
  exit 1
else
  tag_lookup_status=$?
  case "$tag_lookup_status" in
    2) ;;
    *) echo "Error: remote tag lookup failed" >&2; exit "$tag_lookup_status" ;;
  esac
fi

After explicit approval, create and push only the verified tag:

bash

git tag -s -a -m "NVIDIA NeMo Relay ${VERSION}" "$VERSION" HEAD
git tag -v "$VERSION"
git push upstream "refs/tags/$VERSION"

For an authorized GitHub Release draft, read the tagged docs/about-nemo-relay/release-notes/index.mdx, find the previous published stable release with gh api repos/NVIDIA/NeMo-Relay/releases/latest, and use the tagged notes as the source for a concise body. Verify no release already exists, then run:

bash

gh release create "$VERSION" --repo NVIDIA/NeMo-Relay --title "$TITLE" --notes-file "$NOTES_FILE" --draft --verify-tag

Do not create a team announcement or publish the draft unless separately requested.

Files

Just SKILL.md in .agents/skills/create-release-tag of NVIDIA/NeMo-Relay.

Open the folder on GitHubat commit 651453f

Compare with similar skills

Create Release Tag 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.

Create Release Tag compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Create Release Tag this skillNVIDIA/NeMo-Relay	190	—	~827	Automated safety check: Pass	Apache-2.0	today
Nemoclaw Maintainer Release NotesNVIDIA/NemoClaw	23k	—	~2.1k	Automated safety check: Pass	Apache-2.0	today
Respond To IssueNVIDIA/Megatron-LM	18k	—	~913	Automated safety check: Pass	Custom licence	today
Doca Public Knowledge MapNVIDIA/skills	3.5k	—	~3.3k	Automated safety check: Pass	Apache-2.0	today
Nemoclaw Maintainer Normalize Title TagsNVIDIA/NemoClaw	23k	—	~693	Automated safety check: Pass	Apache-2.0	today
Nemoclaw Maintainer Analyze CI PerformanceNVIDIA/NemoClaw	23k	—	~644	Automated safety check: Pass	Apache-2.0	today

Similar skills

Nemoclaw Maintainer Release Notes
NVIDIA/NemoClaw
Official
Draft a post-tag NemoClaw Announcement from the verified release range and shipped PRs.
23k GitHub stars~2.1k tokensUpdated today
DevelopmentAuto-check passed
Respond To Issue
NVIDIA/Megatron-LM
Official
Research and draft a response to a GitHub issue or question from an external contributor.
18k GitHub stars~913 tokensUpdated today
DevelopmentAuto-check passed
Doca Public Knowledge Map
NVIDIA/skills
Official
A skill your agent uses when the user needs to locate authoritative information about NVIDIA DOCA without access to the source tree — finding the right docs.nvidia.com page for a…
3.5k GitHub stars~3.3k tokensUpdated today
DevelopmentAuto-check passed
Nemoclaw Maintainer Normalize Title Tags
NVIDIA/NemoClaw
Official
Remove bracketed NemoClaw tags from GitHub issue and PR titles.
23k GitHub stars~693 tokensUpdated today
Marketing & SEOAuto-check passed
Nemoclaw Maintainer Analyze CI Performance
NVIDIA/NemoClaw
Official
Analyze retained NemoClaw CI timings for slow CLI tests, runner queues, or base-image publication.
23k GitHub stars~644 tokensUpdated today
Testing & QAAuto-check passed
Embeddings via 9Router
decolua/9router
Generates vector embeddings through the 9Router /v1/embeddings endpoint, using models from providers such as OpenAI, Gemini, Mistral and Voyage for RAG and semantic search.
30k GitHub stars~604 tokensUpdated 6 days ago
AI & LLM EngineeringAuto-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.
190 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…
190 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.
190 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.
190 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.
190 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…
190 GitHub stars~1.7k tokensUpdated today
Auto-check passed

Works with

Questions about Create Release Tag

What does Create Release Tag do?

Create and push a signed, annotated NeMo Relay stable tag, then prepare an unpublished GitHub Release draft for review. Create Release Tag is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Create and push a signed, annotated NeMo Relay stable tag, then prepare an unpublished GitHub Release draft for review.

When should I use Create Release Tag?

Create Release Tag fits situations like: cutting a stable release; release-candidate tags.

How do I install Create Release Tag in Claude Code?

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

How do I install Create Release Tag in Codex?

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

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

What does Create Release Tag need to run?

Going by SKILL.md and its folder, Create Release Tag needs the command-line tools its instructions call (git and gh).

Does Create Release Tag access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Create Release Tag 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 Create Release Tag use?

Create Release Tag 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 Create Release Tag use?

About 827 tokens (SKILL.md is roughly 3.3k 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 Create Release Tag?

Skills that share tags, products or a category with Create Release Tag: Nemoclaw Maintainer Release Notes (NVIDIA/NemoClaw, 23k stars), Respond To Issue (NVIDIA/Megatron-LM, 18k stars), Doca Public Knowledge Map (NVIDIA/skills, 3.5k stars) and Nemoclaw Maintainer Normalize Title Tags (NVIDIA/NemoClaw, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Release Tag?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/NeMo-Relay, which has 190 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 7, 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 Create Release Tag

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Create a Release Tag

Create and Verify the Tag

Files

Compare with similar skills

Similar skills

More from NVIDIA/NeMo-Relay

Related

Questions about Create Release Tag