New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Update Project Version

by NVIDIA in NVIDIA/NeMo-Relay

Perform a NeMo Relay project release-version change across project-owned manifests, dependencies, lockfiles, and generated attribution surfaces while keeping just set-version coverage complete.

OfficialApache-2.0Auto-check passedDevelopment

Install Update Project Version

skills CLI
$ npx skills add NVIDIA/NeMo-Relay --skill update-project-version -a claude-code

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

GitHub CLI
$ gh skill install NVIDIA/NeMo-Relay update-project-version --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/update-project-version .claude/skills/update-project-version && 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
update-project-version
GitHub stars
190
Token cost
~776 tokens
SKILL.md length
364 words
Files
2 (incl. references)
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

Perform a NeMo Relay project release-version change across project-owned manifests, dependencies, lockfiles, and generated attribution surfaces while keeping just set-version coverage complete.

  • Works in 6 steps: Read the current version from Cargo.toml… → Compare project-owned package/workspace… → Run just set-version . → …
  • Dependency-only updates
  • SKILL.md covers Invariants, Workflow, Verification and References
  • Calls just

What it does

Update Project Version is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Perform a NeMo Relay project release-version change across project-owned manifests, dependencies, lockfiles, and generated attribution surfaces while keeping just set-version coverage complete. Do not use for dependency-only updates or adding a package when no project version bump is requested.

Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/version-automation.md`).

It sits in Development, covering Dependency management. It works with 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

  • Dependency-only updates
  • Adding a package when no project version bump is requested

Example prompts

  • “/update-project-version”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Read the current version from Cargo.toml and choose the exact target.
  2. Compare project-owned package/workspace members and plugin manifests with
  3. Run just set-version .
  4. Review the diff, then search tracked Cargo, Python, npm, lockfile, and plugin
  5. If a project-owned release surface remains on the old version, update the
  6. Refresh lockfiles or attribution files only when their versioned inputs

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:

    • just

    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

Update Project Version loads about 776 tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 80 tokens; SKILL.md has 364 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~776
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.6k

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). 364 words, ~776 tokens.

Download SKILL.mdSave it as .claude/skills/update-project-version/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
update-project-version
description
Perform a NeMo Relay project release-version change across project-owned manifests, dependencies, lockfiles, and generated attribution surfaces while keeping just set-version coverage complete. Do not use for dependency-only updates or adding a package when no project version bump is requested.
license
Apache-2.0

Update Project Version

Use this skill for project release-version changes, including prerelease and build-metadata variants.

Invariants

  • Cargo.toml [workspace.package].version is the Rust source of truth.
  • just set-version <version> is the single repository entrypoint for updating normal project-version surfaces. Do not hand-edit its existing targets.
  • Every new package or plugin that participates in the unified NeMo Relay release, plus its project-version dependencies and lockfile entries, must be covered by the version automation. If a value does not derive automatically, update the automation in the same change that introduces it.
  • Python surfaces use PEP 440 translations where required; Cargo, npm, and plugin manifests use the repository SemVer form.

Workflow

Use this sequence:

  1. Read the current version from Cargo.toml and choose the exact target.
  2. Compare project-owned package/workspace members and plugin manifests with the helpers called by set_project_version, paying particular attention to recent or in-scope additions. A new manifest, publishable package, internal dependency pinned to the project version, or lockfile package entry is a signal that just set-version may need to change.
  3. Run just set-version <version>.
  4. Review the diff, then search tracked Cargo, Python, npm, lockfile, and plugin manifests for the exact old version. Classify matches rather than replacing them blindly: third-party pins and examples can legitimately match.
  5. If a project-owned release surface remains on the old version, update the appropriate helper and rerun just set-version <version>. Read references/version-automation.md only when the version topology or helper implementation changes.
  6. Refresh lockfiles or attribution files only when their versioned inputs changed. Do not run language suites for a metadata-only bump.
Show full SKILL.md (105 more words)Show less

Verification

Before handoff, verify:

  • Confirm every project-owned manifest version and internal dependency resolves to the target SemVer or its expected PEP 440 translation, and that unrelated versions did not change.
  • Rerun just set-version <version> when automation changed; it should be idempotent and report no missing expected fields.
  • Use focused checks for edited helper code and targeted packaging or generated output checks only for surfaces affected by the bump.

Temporary versions produced by packaging recipes are not the canonical project version unless the release workflow explicitly requires that exact suffix.

References

  • Cargo.toml
  • justfile
  • references/version-automation.md — only for adding, removing, or debugging a versioned surface or version helper

© 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

SKILL.md and 1 other file (references) in .agents/skills/update-project-version of NVIDIA/NeMo-Relay.

  • SKILL.md
  • references/version-automation.md

Open the folder on GitHubat commit 651453f

Compare with similar skills

Update Project Version 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.

Update Project Version compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Update Project Version this skillNVIDIA/NeMo-Relay190—~776Automated safety check: PassApache-2.0
Pnpm Engineteambit/bit18k—~1.9kAutomated safety check: PassCustom licence
Dependency UpdaterAsvarox/allkaraoke2614 repos~3.5kAutomated safety check: PassMIT
Uv Package ManagerYikai-Liao/symusic18915 repos~4kAutomated safety check: NotesMIT
Managing Cargo Dependencieshashintel/hash1.7k—~1.2kAutomated safety check: PassAGPL-3.0
Next Python Stdlib Upgrade PickerRustPython/RustPython22k—~257Automated safety check: PassMIT

Similar skills

  • Pnpm Engine

    teambit/bit

    Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Dependency Updater

    Asvarox/allkaraoke

    Smart dependency management for any language. An agent skill from Asvarox/allkaraoke.

    261 GitHub starsUsed in 4 repos~3.5k tokens
    DevelopmentAuto-check passed

  • Uv Package Manager

    Yikai-Liao/symusic

    Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows.

    189 GitHub starsUsed in 15 repos~4k tokens
    DevelopmentAuto-check: notes

  • Managing Cargo Dependencies

    hashintel/hash

    Cargo.toml dependency management patterns for HASH workspace.

    1.7k GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Next Python Stdlib Upgrade Picker

    RustPython/RustPython

    Picks the next CPython standard library module ready for a RustPython upgrade, skipping modules that already have an open upgrade pull request.

    22k GitHub stars~257 tokensUpdated today
    DevelopmentAuto-check passed

  • Bazel

    Moosync/Moosync

    Hermetic Bazel build, test, and packaging commands for the Moosync project.

    259 GitHub stars~722 tokensUpdated 5 days ago
    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

Categories

Questions about Update Project Version

What does Update Project Version do?

Perform a NeMo Relay project release-version change across project-owned manifests, dependencies, lockfiles, and generated attribution surfaces while keeping just set-version coverage complete. Update Project Version is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Perform a NeMo Relay project release-version change across project-owned manifests, dependencies, lockfiles, and generated attribution surfaces while keeping just set-version coverage complete.

When should I use Update Project Version?

Update Project Version fits situations like: dependency-only updates; adding a package when no project version bump is requested.

How do I install Update Project Version in Claude Code?

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

How do I install Update Project Version in Codex?

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

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

What does Update Project Version need to run?

Going by SKILL.md and its folder, Update Project Version needs the command-line tools its instructions call (just). Our summary lists: Python 3.

Does Update Project Version 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 Update Project Version 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 Update Project Version use?

Update Project Version 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 Update Project Version use?

About 776 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 863 tokens, read only when the agent opens those files.

What are the alternatives to Update Project Version?

Skills that share tags, products or a category with Update Project Version: Pnpm Engine (teambit/bit, 18k stars), Dependency Updater (Asvarox/allkaraoke, 261 stars), Uv Package Manager (Yikai-Liao/symusic, 189 stars) and Managing Cargo Dependencies (hashintel/hash, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Update Project Version?

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.