Adf Master
Kilo-Org/kilo-marketplace
Azure Data Factory (ADF) CI/CD, deployment, and pipeline development.
Verify whether a tagged NeMo Relay release reached GitHub Actions, tagged Go module source, crates.io, PyPI, and npm.
Install Check Release Deployments
$ npx skills add NVIDIA/NeMo-Relay --skill check-release-deployments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/NeMo-Relay check-release-deployments --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/check-release-deployments .claude/skills/check-release-deployments && rm -rf skills-srcUse ~/.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/
Install the "check-release-deployments" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/check-release-deployments into .claude/skills/check-release-deployments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-release-deployments", 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 install https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/check-release-deploymentsType 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.
$ npx skills add NVIDIA/NeMo-Relay --skill check-release-deployments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/NeMo-Relay check-release-deployments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/check-release-deployments .agents/skills/check-release-deployments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "check-release-deployments" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/check-release-deployments into .agents/skills/check-release-deployments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-release-deployments", 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.
$ npx skills add NVIDIA/NeMo-Relay --skill check-release-deployments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/NeMo-Relay check-release-deployments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/check-release-deployments .cursor/skills/check-release-deployments && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "check-release-deployments" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/check-release-deployments into .cursor/skills/check-release-deployments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-release-deployments", 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 https://github.com/NVIDIA/NeMo-Relay.git --path .agents/skills/check-release-deployments--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NVIDIA/NeMo-Relay --skill check-release-deployments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/NeMo-Relay check-release-deployments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/check-release-deployments .gemini/skills/check-release-deployments && rm -rf skills-srcUse ~/.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/
Install the "check-release-deployments" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/check-release-deployments into .gemini/skills/check-release-deployments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-release-deployments", 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.
$ gh skill install NVIDIA/NeMo-Relay check-release-deploymentsInstalls 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).
$ npx skills add NVIDIA/NeMo-Relay --skill check-release-deployments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/check-release-deployments .github/skills/check-release-deployments && rm -rf skills-srcUse ~/.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/
Install the "check-release-deployments" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/check-release-deployments into .github/skills/check-release-deployments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-release-deployments", 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.
$ npx skills add NVIDIA/NeMo-Relay --skill check-release-deployments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA/NeMo-Relay check-release-deployments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/check-release-deployments .opencode/skills/check-release-deployments && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "check-release-deployments" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/check-release-deployments into .opencode/skills/check-release-deployments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-release-deployments", 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
check-release-deployments- GitHub stars
- 190
- Token cost
- ~415 tokens
- SKILL.md length
- 198 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Verify whether a tagged NeMo Relay release reached GitHub Actions, tagged Go module source, crates.io, PyPI, and npm.
- Publication status of a specific tag
- Runs Shell scripts from its folder; calls gh
- Not for publishing packages
What it does
Check Release Deployments is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Verify whether a tagged NeMo Relay release reached GitHub Actions, tagged Go module source, crates.io, PyPI, and npm. Use for publication status of a specific tag; not for publishing packages or creating tags.
Its SKILL.md is about 420 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/check_release_deployments.sh`).
It sits in DevOps & Cloud, covering Deployment and CI/CD. It works with GitHub Actions, NVIDIA AI Platform and npm. 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
- Publication status of a specific tag
- Not for publishing packages
Example prompts
- “/check-release-deployments”
Requirements
- A Bash shell
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
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use 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
Check Release Deployments loads about 415 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 198 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from NVIDIA/NeMo-Relay at commit 651453f, republished under its Apache-2.0 licence (© NVIDIA). 198 words, ~415 tokens.
Download SKILL.mdSave it as
.claude/skills/check-release-deployments/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- check-release-deployments
- description
- Verify whether a tagged NeMo Relay release reached GitHub Actions, tagged Go module source, crates.io, PyPI, and npm. Use for publication status of a specific tag; not for publishing packages or creating tags.
- license
- Apache-2.0
Check Release Deployments
Require the release tag as input. Do not infer it from the current checkout, Git history, or package metadata.
The checker requires Bash, curl, gh, jq, just, and uv. Authenticate
gh for NVIDIA/NeMo-Relay and verify it with gh auth status. The checker
does not run on Windows. From the repository root, run:
.agents/skills/check-release-deployments/scripts/check_release_deployments.sh <tag>It validates Relay's raw-SemVer tag format, converts the version to PEP 440 for
PyPI, and checks the published package sets documented in RELEASING.md. It
also verifies that the source-first Go module is present at the tag and reports
the release-related GitHub Actions jobs. Registry checks run only after their
publication jobs are verified successful. If the tag or release jobs cannot be
verified, package checks are skipped.
☑means the exact package version is deployed.○means that exact package version is not deployed.000means a lookup or response could not be verified.- Other numeric values are HTTP statuses returned by the registry.
The Go row checks the tagged go.mod source because Relay does not publish a
separate Go package-manager artifact.
This is a read-only workflow. Do not retry an absent or failed deployment by publishing packages unless the user separately asks to publish.
© 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 (scripts) in .agents/skills/check-release-deployments of NVIDIA/NeMo-Relay.
- SKILL.md
- scripts/check_release_deployments.sh
Open the folder on GitHubat commit 651453f
Compare with similar skills
Check Release Deployments 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Check Release Deployments this skillNVIDIA/NeMo-Relay | 190 | — | ~415 | Automated safety check: Pass | Apache-2.0 | |
| Adf MasterKilo-Org/kilo-marketplace | 189 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Cline CLI Release Publishercline/cline | 70k | — | ~3.4k | Automated safety check: Warn | Apache-2.0 | |
| Repo Hygiene Scan and FixQwenLM/qwen-code | 28k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 259 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| AI News RadarLearnPrompt/ai-news-radar | 1.8k | — | ~2.5k | Automated safety check: Notes | MIT |
Similar skills
Cline CLI Release Publisher
cline/cline
Walks through releasing the Cline CLI package to npm: release notes, version bump, matching git tag, and either the GitHub workflow or a local publish.
Repo Hygiene Scan and Fix
QwenLM/qwen-code
Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
AI News Radar
LearnPrompt/ai-news-radar
A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…
CI Pipeline Synthesizer
kajisho5/ffmpeg-skill
Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects.
More from NVIDIA/NeMo-Relay
All 30 skills in this repo- Official
Draft Release Notes
NVIDIA/NeMo-Relay
Compare NeMo Relay release refs and draft the current documentation release-notes page from verified repository evidence.
- Official
Nemo Relay Migrate From Flow
NVIDIA/NeMo-Relay
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…
- Official
Add Middleware
NVIDIA/NeMo-Relay
Add a new NeMo Relay guardrail or intercept type, registration surface, or pipeline stage.
- Official
Contribute Docs
NVIDIA/NeMo-Relay
Author or edit NeMo Relay documentation or examples when repository-specific MDX, public API, integration, or release-history conventions matter.
- Official
Maintain CI
NVIDIA/NeMo-Relay
Change or review NeMo Relay GitHub Actions workflows where permissions, pinned actions, caching, reusable workflows, or release gates require repository-specific handling.
- Official
Nemo Relay Install
NVIDIA/NeMo-Relay
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…
Related
Works with
Categories
Questions about Check Release Deployments
What does Check Release Deployments do?
Verify whether a tagged NeMo Relay release reached GitHub Actions, tagged Go module source, crates.io, PyPI, and npm. Check Release Deployments is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization.io, PyPI, and npm.
When should I use Check Release Deployments?
Check Release Deployments fits situations like: publication status of a specific tag; not for publishing packages.
How do I install Check Release Deployments in Claude Code?
Run `npx skills add NVIDIA/NeMo-Relay --skill check-release-deployments -a claude-code`. Or copy the skill folder (.agents/skills/check-release-deployments in NVIDIA/NeMo-Relay) into .claude/skills/check-release-deployments in your project. Claude Code loads it when a task matches its description.
How do I install Check Release Deployments in Codex?
Run `npx skills add NVIDIA/NeMo-Relay --skill check-release-deployments -a codex`. Or copy the skill folder (.agents/skills/check-release-deployments in NVIDIA/NeMo-Relay) into .agents/skills/check-release-deployments in your project. Codex loads it when a task matches its description.
Can I use Check Release Deployments 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 check-release-deployments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/check-release-deployments, .gemini/skills/check-release-deployments, .github/skills/check-release-deployments and .opencode/skills/check-release-deployments in your project.
What does Check Release Deployments need to run?
Going by SKILL.md and its folder, Check Release Deployments needs a shell for the scripts in its folder and the command-line tools its instructions call (gh). Our summary lists: A Bash shell.
Does Check Release Deployments access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Check Release Deployments 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Check Release Deployments use?
Check Release Deployments 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 Check Release Deployments use?
About 415 tokens (SKILL.md is roughly 1.7k 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 Check Release Deployments?
Skills that share tags, products or a category with Check Release Deployments: Adf Master (Kilo-Org/kilo-marketplace, 189 stars), Cline CLI Release Publisher (cline/cline, 70k stars), Repo Hygiene Scan and Fix (QwenLM/qwen-code, 28k stars) and Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 259 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Check Release Deployments?
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.