Official agent skill

Create Beta Tag

Create and push a signed, annotated NeMo Relay beta tag from its release branch or validated main.

OfficialApache-2.0Auto-check passed

Install Create Beta Tag

skills CLI

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

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

GitHub CLI

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

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

GitHub CLI

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

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

GitHub CLI

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

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

GitHub CLI

$ gh skill install NVIDIA/NeMo-Relay create-beta-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-beta-tag .gemini/skills/create-beta-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-beta-tag" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/create-beta-tag into .gemini/skills/create-beta-tag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-beta-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-beta-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-beta-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-beta-tag .github/skills/create-beta-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-beta-tag" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/create-beta-tag into .github/skills/create-beta-tag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-beta-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-beta-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-beta-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-beta-tag .opencode/skills/create-beta-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-beta-tag" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/create-beta-tag into .opencode/skills/create-beta-tag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-beta-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-beta-tag
GitHub stars: 190
Token cost: ~728 tokens
SKILL.md length: 246 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 beta tag from its release branch or validated main.

Cutting a beta tag
Calls git

What it does

Create Beta 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 beta tag from its release branch or validated main. Use when cutting a beta tag; not for RC or stable tags.

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

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

Example prompts

“/create-beta-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
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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 Beta Tag loads about 728 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 246 words of instructions outside code blocks.

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

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). 246 words, ~728 tokens.

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

name: create-beta-tag
description: Create and push a signed, annotated NeMo Relay beta tag from its release branch or validated main. Use when cutting a beta tag; not for RC or stable tags.
license: Apache-2.0

Create a Beta Tag

Require an explicit stable base version in <major>.<minor>[.<patch>] form; treat two components as patch 0. Do not infer it from the branch or package metadata, and do not edit version files while creating the tag.

Prefer release/<major>.<minor>. If that remote branch does not exist, use main only when its workspace version equals the requested base version. Select the next unused positive beta number for that exact base version unless the user provides one. Relay tags are raw SemVer: 0.9.0-beta.1, never v0.9.0-beta.1.

Before the destructive tag push, require explicit approval. Preserve user changes: do not stash, discard, or switch away from a dirty checkout. Fetch the source branch and tags, require HEAD to equal upstream/<source-branch>, and require the workspace version to equal the stable base 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.

Select and Verify the Source

Use upstream for NVIDIA/NeMo-Relay. The version and optional beta number are user inputs. Validate a supplied number as a positive integer; otherwise derive the next number after fetching tags for the selected source branch.

bash

BASE_VERSION=<major.minor[.patch]>
[[ "$BASE_VERSION" =~ ^[0-9]+\.[0-9]+(\.[0-9]+)?$ ]] || { echo "Error: invalid base version" >&2; exit 1; }
if [[ "$BASE_VERSION" =~ ^[0-9]+\.[0-9]+$ ]]; then BASE_VERSION="$BASE_VERSION.0"; fi
RELEASE_BRANCH="release/$(printf '%s' "$BASE_VERSION" | cut -d. -f1,2)"
SOURCE_BRANCH="$RELEASE_BRANCH"
if git ls-remote --exit-code --heads upstream "refs/heads/$SOURCE_BRANCH" >/dev/null; then
  :
else
  lookup_status=$?
  case "$lookup_status" in
    2) SOURCE_BRANCH=main ;;
    *) echo "Error: release branch lookup failed" >&2; exit "$lookup_status" ;;
  esac
fi
git fetch upstream "$SOURCE_BRANCH" --tags

LAST_BETA="$(git tag --list "${BASE_VERSION}-beta.*" | sed -nE "s/^${BASE_VERSION//./\\.}-beta\.([1-9][0-9]*)$/\\1/p" | sort -n | tail -1)"
BETA_NUMBER="${BETA_NUMBER:-$(( ${LAST_BETA:-0} + 1 ))}"
[[ "$BETA_NUMBER" =~ ^[1-9][0-9]*$ ]]
TAG="${BASE_VERSION}-beta.${BETA_NUMBER}"

From a clean checkout of SOURCE_BRANCH, verify the branch is current, the workspace version matches BASE_VERSION, and the tag is absent locally and on upstream. When SOURCE_BRANCH is main, make the same version check against upstream/main before switching. After the user authorizes the push:

bash

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

Files

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

Open the folder on GitHubat commit 651453f

Compare with similar skills

Create Beta 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 Beta Tag compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Create Beta Tag this skillNVIDIA/NeMo-Relay	190	—	~728	Automated safety check: Pass	Apache-2.0	today
LLM Torch Profiler Analysissgl-project/sglang	37k	2 repos	~6.4k	Automated safety check: Pass	Apache-2.0	today
Skill InspectorNVIDIA/SkillSpector	20k	—	~1.8k	Automated safety check: Pass	Apache-2.0	today
Embeddings via 9Routerdecolua/9router	30k	—	~604	Automated safety check: Pass	MIT	6 days ago
NEAR AI Cloud Private Inferenceinternet-court/internet-court-skill	6.4k	2 repos	~1.3k	Automated safety check: Pass	Custom licence	1 mo ago
Nemoclaw Maintainer Normalize Title TagsNVIDIA/NemoClaw	23k	—	~693	Automated safety check: Pass	Apache-2.0	today

Similar skills

LLM Torch Profiler Analysis
sgl-project/sglang
Unified LLM torch-profiler triage skill for sglang, vllm, TensorRT-LLM, and TokenSpeed.
37k GitHub starsUsed in 2 repos~6.4k tokens
DevelopmentAuto-check passed
Skill Inspector
NVIDIA/SkillSpector
Official
Decides whether an agent skill is safe to install by combining a SkillSpector static scan with the agent's own source review, ending in APPROVE, CAUTION or REJECT.
20k GitHub stars~1.8k tokensUpdated today
SecurityAuto-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
NEAR AI Cloud Private Inference
internet-court/internet-court-skill
Shows how to call NEAR AI Cloud through an OpenAI-compatible API and verify that inference ran in a TEE, using attestation checks and signed chat responses.
6.4k GitHub starsUsed in 2 repos~1.3k tokens
AI & LLM EngineeringAuto-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
Megatron-LM Container and Dependency Setup
NVIDIA/Megatron-LM
Official
Walks an agent through working inside the Megatron-LM CI container and changing dependencies with uv, so lock files resolve the same locally and in CI.
18k GitHub stars~2.6k tokensUpdated today
DevelopmentAuto-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

NVIDIA AI Platform

Questions about Create Beta Tag

What does Create Beta Tag do?

Create and push a signed, annotated NeMo Relay beta tag from its release branch or validated main. Create Beta 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 beta tag from its release branch or validated main.

When should I use Create Beta Tag?

Create Beta Tag fits situations like: cutting a beta tag.

How do I install Create Beta Tag in Claude Code?

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

How do I install Create Beta Tag in Codex?

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

Can I use Create Beta 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-beta-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-beta-tag, .gemini/skills/create-beta-tag, .github/skills/create-beta-tag and .opencode/skills/create-beta-tag in your project.

What does Create Beta Tag need to run?

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

Does Create Beta Tag access the network?

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

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

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

About 728 tokens (SKILL.md is roughly 2.9k 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 Beta Tag?

Skills that share tags, products or a category with Create Beta Tag: LLM Torch Profiler Analysis (sgl-project/sglang, 37k stars), Skill Inspector (NVIDIA/SkillSpector, 20k stars), Embeddings via 9Router (decolua/9router, 30k stars) and NEAR AI Cloud Private Inference (internet-court/internet-court-skill, 6.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Beta 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 Beta 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 Beta Tag

Select and Verify the Source

Files

Compare with similar skills

Similar skills

More from NVIDIA/NeMo-Relay

Related

Questions about Create Beta Tag