Official agent skill

Create Rc Tag

by NVIDIA in NVIDIA/NeMo-Relay

Create and push a signed, annotated NeMo Relay release-candidate tag from its validated release branch.

OfficialApache-2.0Auto-check passed

Install Create Rc Tag

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

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

GitHub CLI
$ gh skill install NVIDIA/NeMo-Relay create-rc-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-rc-tag .claude/skills/create-rc-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/

Facts

Skill name
create-rc-tag
GitHub stars
192
Token cost
~635 tokens
SKILL.md length
228 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

Create and push a signed, annotated NeMo Relay release-candidate tag from its validated release branch.

  • Cutting an RC tag
  • Calls git
  • Not for code freezes

What it does

Create Rc 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 release-candidate tag from its validated release branch. Use when cutting an RC tag; not for code freezes or stable tags.

Its SKILL.md is about 640 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 an RC tag
  • Not for code freezes

Example prompts

  • “/create-rc-tag”

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

    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 Rc Tag loads about 635 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 228 words of instructions outside code blocks.

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

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). 228 words, ~635 tokens.

Download SKILL.mdSave it as .claude/skills/create-rc-tag/SKILL.md (or your agent's skills folder).
name
create-rc-tag
description
Create and push a signed, annotated NeMo Relay release-candidate tag from its validated release branch. Use when cutting an RC tag; not for code freezes or stable tags.
license
Apache-2.0

Create an RC 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. The matching release/<major>.<minor> branch must exist on upstream.

Select the next unused positive RC number for that exact base version unless the user supplies one. Relay uses raw-SemVer tags such as 0.9.0-rc.1, without a leading 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 stable base version. Verify that 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 RC number are user inputs. Validate a supplied number as a positive integer; otherwise derive the next number after fetching the release branch and tags.

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)"
git ls-remote --exit-code --heads upstream "refs/heads/$RELEASE_BRANCH"
git fetch upstream "$RELEASE_BRANCH" --tags

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

From a clean checkout of RELEASE_BRANCH, require HEAD to match upstream/$RELEASE_BRANCH, verify the workspace version matches BASE_VERSION, and check that TAG is absent locally and on upstream. 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"

© 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/create-rc-tag of NVIDIA/NeMo-Relay.

Open the folder on GitHubat commit 16d73b4

Compare with similar skills

Create Rc 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 Rc Tag compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Rc Tag this skillNVIDIA/NeMo-Relay192—~635Automated safety check: PassApache-2.0
Skill InspectorNVIDIA/SkillSpector20k1 repos~1.8kAutomated safety check: PassApache-2.0
LLM Torch Profiler Analysissgl-project/sglang37k2 repos~6.4kAutomated safety check: PassApache-2.0
Embeddings via 9Routerdecolua/9router30k—~604Automated safety check: PassMIT
NEAR AI Cloud Private Inferenceinternet-court/internet-court-skill6.4k2 repos~1.3kAutomated safety check: PassCustom licence
Nemoclaw Maintainer Normalize Title TagsNVIDIA/NemoClaw23k—~693Automated safety check: PassApache-2.0

Similar skills

  • 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 starsUsed in 1 repo~1.8k tokens
    SecurityAuto-check passed
  • 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
  • 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 7 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
  • Remove bracketed NemoClaw tags from GitHub issue and PR titles.

    23k GitHub stars~693 tokensUpdated today
    Marketing & SEOAuto-check passed
  • Audit and implement a NemoClaw dependency version upgrade, including Hermes and base images.

    23k GitHub stars~1.4k 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.

    192 GitHub stars~575 tokensUpdated today
    Auto-check passed
  • 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 Create Rc Tag

What does Create Rc Tag do?

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

When should I use Create Rc Tag?

Create Rc Tag fits situations like: cutting an RC tag; not for code freezes.

How do I install Create Rc Tag in Claude Code?

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

How do I install Create Rc Tag in Codex?

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

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

What does Create Rc Tag need to run?

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

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

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

About 635 tokens (SKILL.md is roughly 2.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 Create Rc Tag?

Skills that share tags, products or a category with Create Rc Tag: Skill Inspector (NVIDIA/SkillSpector, 20k stars), LLM Torch Profiler Analysis (sgl-project/sglang, 37k 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 Rc Tag?

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.