Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Compare NeMo Relay release refs and draft the current documentation release-notes page from verified repository evidence.
Install Draft Release Notes
$ npx skills add NVIDIA/NeMo-Relay --skill draft-release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/NeMo-Relay draft-release-notes --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/draft-release-notes .claude/skills/draft-release-notes && 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 "draft-release-notes" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/draft-release-notes into .claude/skills/draft-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-release-notes", 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/draft-release-notesType 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 draft-release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/NeMo-Relay draft-release-notes --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/draft-release-notes .agents/skills/draft-release-notes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "draft-release-notes" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/draft-release-notes into .agents/skills/draft-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-release-notes", 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 draft-release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/NeMo-Relay draft-release-notes --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/draft-release-notes .cursor/skills/draft-release-notes && 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 "draft-release-notes" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/draft-release-notes into .cursor/skills/draft-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-release-notes", 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/draft-release-notes--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 draft-release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/NeMo-Relay draft-release-notes --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/draft-release-notes .gemini/skills/draft-release-notes && 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 "draft-release-notes" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/draft-release-notes into .gemini/skills/draft-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-release-notes", 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 draft-release-notesInstalls 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 draft-release-notes -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/draft-release-notes .github/skills/draft-release-notes && 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 "draft-release-notes" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/draft-release-notes into .github/skills/draft-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-release-notes", 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 draft-release-notes -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 draft-release-notes --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/draft-release-notes .opencode/skills/draft-release-notes && 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 "draft-release-notes" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/draft-release-notes into .opencode/skills/draft-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-release-notes", 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
draft-release-notes- GitHub stars
- 190
- Token cost
- ~575 tokens
- SKILL.md length
- 252 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Compare NeMo Relay release refs and draft the current documentation release-notes page from verified repository evidence.
- Works in 6 steps: Confirm the target release version from… → Run the helper. It reports an absent… → Verify each candidate claim in the… → …
- GitHub Release bodies
- SKILL.md covers Gather Evidence, Workflow and Validate
- Runs Python scripts from its folder; calls python3, git and just
What it does
Draft Release Notes is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Compare NeMo Relay release refs and draft the current documentation release-notes page from verified repository evidence. Do not use for GitHub Release bodies or ordinary feature documentation.
Its SKILL.md is about 580 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/collect_release_evidence.py`).
It sits in Development, covering Changelog and release notes. It works with GitHub. 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
- GitHub Release bodies
- Ordinary feature documentation
Example prompts
- “/draft-release-notes”
Requirements
- Python 3
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Confirm the target release version from the release branch and package
- Run the helper. It reports an absent prior release-notes directory without
- Verify each candidate claim in the changed public docs, API types, command
- Update docs/about-nemo-relay/release-notes/index.mdx unless the release
- Preserve the page's current structure: release summary and highlights,
- Preserve MDX front matter and the JSX SPDX comment. State the full history
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/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3gitjust
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
Draft Release Notes loads about 575 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 252 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). 252 words, ~575 tokens.
Download SKILL.mdSave it as
.claude/skills/draft-release-notes/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- draft-release-notes
- description
- Compare NeMo Relay release refs and draft the current documentation release-notes page from verified repository evidence. Do not use for GitHub Release bodies or ordinary feature documentation.
Draft Release Notes
Draft the current documentation release-notes page from verified repository evidence. Keep complete, PR-by-PR release history in GitHub Releases.
Gather Evidence
Run the read-only helper with explicit release refs and the target minor version:
python3 .agents/skills/draft-release-notes/scripts/collect_release_evidence.py \
--previous release/<previous-major>.<previous-minor> \
--current HEAD \
--version <major>.<minor>The report verifies both refs, compares their release-notes trees, identifies version text currently present in those pages, and groups commits into review candidates. Treat the groups as an evidence index, not publication-ready copy.
Workflow
- Confirm the target release version from the release branch and package metadata. Preserve unrelated working-tree changes.
- Run the helper. It reports an absent prior release-notes directory without failing, which is expected for early release branches.
- Verify each candidate claim in the changed public docs, API types, command help, or source before including it. Prioritize breaking changes, migrations, user-visible features, and ongoing support limitations.
- Update
docs/about-nemo-relay/release-notes/index.mdxunless the release changes its route or navigation entry. - Preserve the page's current structure: release summary and highlights, compatibility or migration notes, known issues, previous-release link, and related topics. Use tables or callouts only when they improve the existing page.
- Preserve MDX front matter and the JSX SPDX comment. State the full history is available in GitHub Releases; do not create a changelog or GitHub Release body from this skill.
Validate
Run the helper for the target release and, when useful, an early branch without release notes. Review public claims, then run:
git diff --check
just docsCheck product names, commands, package names, support claims, and links against the current repository before handing off the draft.
© 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/draft-release-notes of NVIDIA/NeMo-Relay.
- SKILL.md
- scripts/collect_release_evidence.py
Open the folder on GitHubat commit 651453f
Compare with similar skills
Draft Release Notes 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 |
|---|---|---|---|---|---|---|
| Draft Release Notes this skillNVIDIA/NeMo-Relay | 190 | — | ~575 | Automated safety check: Pass | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Mole CLI Release Flowtw93/Mole | 69k | — | ~2.5k | Automated safety check: Pass | GPL-3.0 | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 69k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
Cut Release
jfernandez/bpftop
Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.
More from NVIDIA/NeMo-Relay
All 30 skills in this repo- 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…
- Official
Nemo Relay Plugin Build
NVIDIA/NeMo-Relay
A skill your agent uses when building or packaging reusable NeMo Relay runtime behavior as an embedded configuration component or a manifest-backed rustdynamic native or worker gRPC plugin, with…
Related
Works with
Categories
Questions about Draft Release Notes
What does Draft Release Notes do?
Compare NeMo Relay release refs and draft the current documentation release-notes page from verified repository evidence. Draft Release Notes is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Compare NeMo Relay release refs and draft the current documentation release-notes page from verified repository evidence.
When should I use Draft Release Notes?
Draft Release Notes fits situations like: GitHub Release bodies; ordinary feature documentation.
How do I install Draft Release Notes in Claude Code?
Run `npx skills add NVIDIA/NeMo-Relay --skill draft-release-notes -a claude-code`. Or copy the skill folder (.agents/skills/draft-release-notes in NVIDIA/NeMo-Relay) into .claude/skills/draft-release-notes in your project. Claude Code loads it when a task matches its description.
How do I install Draft Release Notes in Codex?
Run `npx skills add NVIDIA/NeMo-Relay --skill draft-release-notes -a codex`. Or copy the skill folder (.agents/skills/draft-release-notes in NVIDIA/NeMo-Relay) into .agents/skills/draft-release-notes in your project. Codex loads it when a task matches its description.
Can I use Draft Release Notes 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 draft-release-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/draft-release-notes, .gemini/skills/draft-release-notes, .github/skills/draft-release-notes and .opencode/skills/draft-release-notes in your project.
What does Draft Release Notes need to run?
Going by SKILL.md and its folder, Draft Release Notes needs Python for the scripts in its folder and the command-line tools its instructions call (python3, git and just). Our summary lists: Python 3.
Does Draft Release Notes 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 Draft Release Notes 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 Draft Release Notes use?
Draft Release Notes 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 Draft Release Notes use?
About 575 tokens (SKILL.md is roughly 2.3k 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 Draft Release Notes?
Skills that share tags, products or a category with Draft Release Notes: Cutting A Release (TriliumNext/Trilium, 38k stars), Mole CLI Release Flow (tw93/Mole, 69k stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Mole Release Notes Publisher (tw93/Mole, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Draft Release Notes?
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.