New: 98,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

Nemoclaw Maintainer Cut Release Tag

by NVIDIA in NVIDIA/NemoClaw

Prepare and cut one signed NemoClaw semver release tag, then follow release workflows and draft the Announcement.

OfficialApache-2.0Auto-check passedTesting & QA

Install Nemoclaw Maintainer Cut Release Tag

skills CLI
$ npx skills add NVIDIA/NemoClaw --skill nemoclaw-maintainer-cut-release-tag -a claude-code

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

GitHub CLI
$ gh skill install NVIDIA/NemoClaw nemoclaw-maintainer-cut-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/NemoClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/nemoclaw-maintainer-cut-release-tag .claude/skills/nemoclaw-maintainer-cut-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/

Facts

Skill name
nemoclaw-maintainer-cut-release-tag
GitHub stars
23k
Token cost
~1.1k tokens
SKILL.md length
558 words
Files
5 (incl. references)
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

Prepare and cut one signed NemoClaw semver release tag, then follow release workflows and draft the Announcement.

  • Testing & QA work in your project
  • SKILL.md covers Hard Rules and Work to the requested outcome
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Nemoclaw Maintainer Cut Release Tag is an agent skill from NVIDIA/NemoClaw, published by the product's own GitHub organization. Prepare and cut one signed NemoClaw semver release tag, then follow release workflows and draft the Announcement.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/candidate-evidence.md`, `references/cut-and-follow-through.md` and `references/prepare-release.md`).

It sits in Testing & QA. The repository describes itself as: Run agents like Hermes, LangChain Deep Agents, and OpenClaw more securely inside NVIDIA OpenShell with managed inference. The licence is Apache-2.0.

When your agent uses it

  • Testing & QA work in your project

Example prompts

  • “/nemoclaw-maintainer-cut-release-tag”

What it can do on your machine

Read from SKILL.md and the folder at commit 4e3bf44. 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

Nemoclaw Maintainer Cut Release Tag loads about 1.1k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 37 tokens; SKILL.md has 558 words of instructions outside code blocks.

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

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/NemoClaw at commit 4e3bf44, republished under its Apache-2.0 licence (© NVIDIA). 558 words, ~1,125 tokens.

Download SKILL.mdSave it as .claude/skills/nemoclaw-maintainer-cut-release-tag/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
nemoclaw-maintainer-cut-release-tag
description
Prepare and cut one signed NemoClaw semver release tag, then follow release workflows and draft the Announcement.
user_invocable
true
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->

Cut Release Tag

Cut one signed annotated semver tag from a generated plan. Use the release scripts for tag writes. Use Run Maintainer E2E for maintainer-requested workflow dispatches. Do not improvise tag, push, version-bump, or other release-state GitHub writes.

Treat these as separate states:

  • Tag can be cut: the release entry and required image checks pass. The maintainer chooses to proceed with the displayed documentation coverage and general E2E state. The release brief records both decisions and contains no unresolved prompts.
  • Tag cut: the remote signed tag exists and peels to the planned candidate.
  • Post-tag follow-through: after reporting the tag as cut, continue the same task. Monitor latest, release labels, public documentation, and release images. Draft the Announcement and report lkg state.

Hard Rules

  • Use the requested version. Generate the plan with --version vX.Y.Z; never infer a bump.
  • Tag only the candidate captured in the plan.
  • By default, plan origin/main without an exception. For urgent QA qualification, a maintainer may select a historical ancestor with --candidate <full-sha> --exception <reason>.
  • Require the release entry for a current-main plan. A historical plan records its explicit release-entry exception in the signed release brief.
  • Treat documentation coverage as maintainer context, not a tag gate. Show the coverage point, later commits and PRs, review and check state, changed paths, and open managed docs PRs.
  • Record the maintainer's documentation decision in the signed release brief.
  • Require applicable GHCR base and managed-image publication evidence.
  • Treat E2E as maintainer context, not a tag gate. Show the newest full E2E result and let the maintainer run focused tests, run the full suite, or proceed with the displayed status.
  • Record every displayed or requested E2E result and the decision in the release brief, the signed Markdown release record. Record a plain-language exception reason when the status is exceptional or a requested run remains unresolved.
  • Pass the final release brief to release:cut with --message-file. The file becomes the signed tag annotation; do not maintain another exception record.
  • Ask the maintainer to paste the plan's full confirmation phrase before cutting.
  • Push only the planned semver tag. Never push or move latest or lkg here.
  • Report the tag as cut immediately after remote readback. This report is a progress checkpoint, not the final response.
  • Continue the same task through post-tag follow-through. Do not make a post-tag result a tag gate.
  • Ask before a workflow rerun. Never create a GitHub Discussion.
  • Never move, delete, or replace an existing remote semver tag unless the maintainer starts a protected-tag remediation.
  • Follow the release-train policy and the shared Git and GitHub Access Hard Stop.
Show full SKILL.md (131 more words)Show less

Work to the requested outcome

  • Prepare: follow Prepare the Release and its linked candidate evidence. Start independent read-only checks early and prepare authorized documentation during image waits. Keep the planned candidate immutable.
  • Cut: after the final brief is reviewable and the required confirmation is supplied, follow Cut and Follow Through. Its tag readback establishes tag success.
  • Follow through: continue the same task through automatic release workflows, the local Announcement draft, and lkg classification using the same reference.
  • Recover: use Recovery for failed evidence or post-tag work. Retain the specific rerun authorization and immutable-tag boundaries.

The release confirmation protects a signed public tag. Do not apply that confirmation requirement to preliminary reads or already-authorized preparation. Report tag success as a progress checkpoint; report final completion only after the follow-through conditions are classified.

© 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 4 other files (references) in .agents/skills/nemoclaw-maintainer-cut-release-tag of NVIDIA/NemoClaw.

  • SKILL.md
  • references/candidate-evidence.md
  • references/cut-and-follow-through.md
  • references/prepare-release.md
  • references/recovery.md

Open the folder on GitHubat commit 4e3bf44

Compare with similar skills

Nemoclaw Maintainer Cut 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.

Nemoclaw Maintainer Cut Release Tag compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nemoclaw Maintainer Cut Release Tag this skillNVIDIA/NemoClaw23k—~1.1kAutomated safety check: PassApache-2.0
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Diagnosing Bugsfossasia/eventyay-interpretation1.6k32 repos~2.1kAutomated safety check: PassApache-2.0
TDDpietheinstrengholt/rssmonster56430 repos~906Automated safety check: PassMIT
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
TDDsanity-io/sanity6.4k20 repos~1kAutomated safety check: PassMIT

Similar skills

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed

  • Diagnosing Bugs

    fossasia/eventyay-interpretation

    Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 32 repos~2.1k tokens
    Testing & QAAuto-check passed

  • TDD

    pietheinstrengholt/rssmonster

    Test-driven development. An agent skill from pietheinstrengholt/rssmonster.

    564 GitHub starsUsed in 30 repos~906 tokens
    Testing & QAAuto-check passed

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

  • TDD

    sanity-io/sanity

    Official

    Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 20 repos~1k tokens
    Testing & QAAuto-check passed

  • Context Driven Development

    Ibrahim-3d/orchestrator-supaconductor

    A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…

    381 GitHub starsUsed in 9 repos~2.9k tokens
    Testing & QAAuto-check passed

More from NVIDIA/NemoClaw

All 30 skills in this repo

  • Nemoclaw Maintainer Cross Issue Sweep

    NVIDIA/NemoClaw

    Official

    Find open issues that a NemoClaw PR may also fix or conflict with.

    23k GitHub stars~893 tokensUpdated today
    Auto-check passed

  • Nemoclaw Maintainer Day

    NVIDIA/NemoClaw

    Official

    Run a NemoClaw daytime maintainer pass over release-targeted work.

    23k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Nemoclaw Contributor Update Dependencies

    NVIDIA/NemoClaw

    Official

    Audit and implement a NemoClaw dependency version upgrade, including Hermes and base images.

    23k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Nemoclaw Maintainer Fix E2E Failures

    NVIDIA/NemoClaw

    Official

    Continuously maintain automatic NemoClaw main E2E results through coordinated repairs.

    23k GitHub stars~2.6k tokensUpdated today
    Auto-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
    Auto-check passed

Categories

Questions about Nemoclaw Maintainer Cut Release Tag

What does Nemoclaw Maintainer Cut Release Tag do?

Prepare and cut one signed NemoClaw semver release tag, then follow release workflows and draft the Announcement. Nemoclaw Maintainer Cut Release Tag is an agent skill from NVIDIA/NemoClaw, published by the product's own GitHub organization. Prepare and cut one signed NemoClaw semver release tag, then follow release workflows and draft the Announcement.

When should I use Nemoclaw Maintainer Cut Release Tag?

Nemoclaw Maintainer Cut Release Tag fits situations like: testing & QA work in your project.

How do I install Nemoclaw Maintainer Cut Release Tag in Claude Code?

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

How do I install Nemoclaw Maintainer Cut Release Tag in Codex?

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

Can I use Nemoclaw Maintainer Cut 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/NemoClaw --skill nemoclaw-maintainer-cut-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/nemoclaw-maintainer-cut-release-tag, .gemini/skills/nemoclaw-maintainer-cut-release-tag, .github/skills/nemoclaw-maintainer-cut-release-tag and .opencode/skills/nemoclaw-maintainer-cut-release-tag in your project.

What does Nemoclaw Maintainer Cut Release Tag need to run?

SKILL.md names no scripts, command-line tools or credentials: Nemoclaw Maintainer Cut Release Tag is instructions for the agent only.

Does Nemoclaw Maintainer Cut Release Tag 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 Nemoclaw Maintainer Cut 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 Nemoclaw Maintainer Cut Release Tag use?

Nemoclaw Maintainer Cut Release Tag is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nemoclaw Maintainer Cut Release Tag use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 9.3k tokens, read only when the agent opens those files.

What are the alternatives to Nemoclaw Maintainer Cut Release Tag?

Skills that share tags, products or a category with Nemoclaw Maintainer Cut Release Tag: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (pietheinstrengholt/rssmonster, 564 stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nemoclaw Maintainer Cut Release Tag?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/NemoClaw, which has 22,706 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 11, 2026.

Source: NVIDIA/NemoClaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.