Release Version
GOODBOY008/r-shell
Release a new r-shell version and create a published GitHub release with contributor credits.
Generate a GitHub release-checklist issue for a full (non-RC) release of the Smelter server and/or the TypeScript SDK.
Install Create Release Checklist
$ npx skills add software-mansion/smelter --skill create-release-checklist -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install software-mansion/smelter create-release-checklist --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/software-mansion/smelter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/create-release-checklist .claude/skills/create-release-checklist && 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 "create-release-checklist" agent skill from https://github.com/software-mansion/smelter/tree/master/.claude/skills/create-release-checklist into .claude/skills/create-release-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release-checklist", 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/software-mansion/smelter/tree/master/.claude/skills/create-release-checklistType 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 software-mansion/smelter --skill create-release-checklist -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install software-mansion/smelter create-release-checklist --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/software-mansion/smelter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/create-release-checklist .agents/skills/create-release-checklist && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-release-checklist" agent skill from https://github.com/software-mansion/smelter/tree/master/.claude/skills/create-release-checklist into .agents/skills/create-release-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release-checklist", 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 software-mansion/smelter --skill create-release-checklist -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install software-mansion/smelter create-release-checklist --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/software-mansion/smelter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/create-release-checklist .cursor/skills/create-release-checklist && 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 "create-release-checklist" agent skill from https://github.com/software-mansion/smelter/tree/master/.claude/skills/create-release-checklist into .cursor/skills/create-release-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release-checklist", 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/software-mansion/smelter.git --path .claude/skills/create-release-checklist--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 software-mansion/smelter --skill create-release-checklist -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install software-mansion/smelter create-release-checklist --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/software-mansion/smelter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/create-release-checklist .gemini/skills/create-release-checklist && 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 "create-release-checklist" agent skill from https://github.com/software-mansion/smelter/tree/master/.claude/skills/create-release-checklist into .gemini/skills/create-release-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release-checklist", 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 software-mansion/smelter create-release-checklistInstalls 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 software-mansion/smelter --skill create-release-checklist -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/software-mansion/smelter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/create-release-checklist .github/skills/create-release-checklist && 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 "create-release-checklist" agent skill from https://github.com/software-mansion/smelter/tree/master/.claude/skills/create-release-checklist into .github/skills/create-release-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release-checklist", 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 software-mansion/smelter --skill create-release-checklist -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install software-mansion/smelter create-release-checklist --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/software-mansion/smelter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/create-release-checklist .opencode/skills/create-release-checklist && 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 "create-release-checklist" agent skill from https://github.com/software-mansion/smelter/tree/master/.claude/skills/create-release-checklist into .opencode/skills/create-release-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release-checklist", 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
create-release-checklist- GitHub stars
- 732
- Token cost
- ~1.9k tokens
- SKILL.md length
- 590 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Generate a GitHub release-checklist issue for a full (non-RC) release of the Smelter server and/or the TypeScript SDK.
- Works in 3 steps: Current versions and last released tags… → The changelog: read the ## unreleased… → The server↔SDK coupling:…
- Tasks that involve Feature launches and release readiness
- SKILL.md covers What to gather first, Extracting options from the…, Issue structure (reproduce… and Creating the issue
- Calls git and gh
What it does
Create Release Checklist is an agent skill from software-mansion/smelter. Generate a GitHub release-checklist issue for a full (non-RC) release of the Smelter server and/or the TypeScript SDK. Reads the changelog, extracts the actual new/changed options to verify, and opens the issue with gh.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Feature launches and release readiness and Changelog and release notes. It works with GitHub, TypeScript, Rust and React. The repository describes itself as: Toolkit for real-time, low latency, programmable video and audio mixing.
When your agent uses it
- Tasks that involve Feature launches and release readiness
- Tasks that involve Changelog and release notes
Example prompts
- “/create-release-checklist”
Requirements
- Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Current versions and last released tags (so you can propose the next versions)
- The changelog: read the ## unreleased section of CHANGELOG.md. This is the source of truth for what needs to be verified — do not invent…
- The server↔SDK coupling: ts/smelter-node/src/manager/locallySpawnedInstance.ts defines VERSION and REPO. The SDK downloads the server…
What it can do on your machine
Read from SKILL.md and the folder at commit f3b8293. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadGrepGlob
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and 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
Create Release Checklist loads about 1.9k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 590 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Grep, Glob
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 590 words (~1,891 tokens).
“Create a GitHub issue that tracks a full, non-RC release of the Smelter server and the TypeScript SDK, following the structure and ordering of the process documented in RELEASE.md.”
- name
- create-release-checklist
- allowed-tools
- Bash, Read, Grep, Glob
- disable-model-invocation
- false
Files
Just SKILL.md in .claude/skills/create-release-checklist of software-mansion/smelter.
Open the folder on GitHubat commit f3b8293
Compare with similar skills
Create Release Checklist 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 |
|---|---|---|---|---|---|---|
| Create Release Checklist this skillsoftware-mansion/smelter | 732 | — | ~1.9k | Automated safety check: Notes | Custom licence | |
| Release VersionGOODBOY008/r-shell | 151 | — | ~4k | Automated safety check: Pass | MIT | |
| Release New Versionkcsujeet/ilamy-calendar | 351 | — | ~5.8k | Automated safety check: Pass | MIT | |
| Megaphone ReleaseKuberwastaken/megaphone | 169 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Upgrade Dear Imgui StackLatias94/dear-imgui-rs | 107 | — | ~977 | Automated safety check: Pass | Apache-2.0 | |
| Release MaintainerUndertone0809/rudder | 292 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Release New Version
kcsujeet/ilamy-calendar
Cut a new release of @ilamy/calendar — analyze commits since the last tag, suggest a semver bump, draft a CHANGELOG entry in the project's existing style, run the CI gate, commit, tag, push to…
Megaphone Release
Kuberwastaken/megaphone
Prepare, validate, publish, and verify Megaphone releases. An agent skill from Kuberwastaken/megaphone.
Upgrade Dear Imgui Stack
Latias94/dear-imgui-rs
A skill your agent uses when a user asks to upgrade Dear ImGui, cimgui, ImPlot, ImPlot3D, ImNodes, ImGuizmo, Dear ImGui Test Engine, or related bindings in this repository.
Release Maintainer
Undertone0809/rudder
A skill your agent uses when inspecting, preparing, executing, recovering, or verifying Rudder releases across npm, GitHub Releases, Desktop assets, tags, dist-tags, changelogs, Discord…
Generate Release Notes
teambit/bit
Generate comprehensive release notes for Bit from git commits and pull requests.
More from software-mansion/smelter
API Change
software-mansion/smelter
Run the full API change workflow after modifying types in smelter-api.
Related
Works with
Categories
Questions about Create Release Checklist
What does Create Release Checklist do?
Generate a GitHub release-checklist issue for a full (non-RC) release of the Smelter server and/or the TypeScript SDK. Create Release Checklist is an agent skill from software-mansion/smelter. Generate a GitHub release-checklist issue for a full (non-RC) release of the Smelter server and/or the TypeScript SDK.
When should I use Create Release Checklist?
Create Release Checklist fits situations like: tasks that involve Feature launches and release readiness; tasks that involve Changelog and release notes.
How do I install Create Release Checklist in Claude Code?
Run `npx skills add software-mansion/smelter --skill create-release-checklist -a claude-code`. Or copy the skill folder (.claude/skills/create-release-checklist in software-mansion/smelter) into .claude/skills/create-release-checklist in your project. Claude Code loads it when a task matches its description.
How do I install Create Release Checklist in Codex?
Run `npx skills add software-mansion/smelter --skill create-release-checklist -a codex`. Or copy the skill folder (.claude/skills/create-release-checklist in software-mansion/smelter) into .agents/skills/create-release-checklist in your project. Codex loads it when a task matches its description.
Can I use Create Release Checklist 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 software-mansion/smelter --skill create-release-checklist -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-release-checklist, .gemini/skills/create-release-checklist, .github/skills/create-release-checklist and .opencode/skills/create-release-checklist in your project.
What does Create Release Checklist need to run?
Going by SKILL.md and its folder, Create Release Checklist needs the command-line tools its instructions call (git and gh). Its frontmatter pre-approves these tools: Bash, Read, Grep, Glob.
Does Create Release Checklist access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Create Release Checklist safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Create Release Checklist use?
Create Release Checklist has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Create Release Checklist use?
About 1.9k tokens (SKILL.md is roughly 7.6k 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 Release Checklist?
Skills that share tags, products or a category with Create Release Checklist: Release Version (GOODBOY008/r-shell, 151 stars), Release New Version (kcsujeet/ilamy-calendar, 351 stars), Megaphone Release (Kuberwastaken/megaphone, 169 stars) and Upgrade Dear Imgui Stack (Latias94/dear-imgui-rs, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Create Release Checklist?
software-mansion (a GitHub organization) maintains it in software-mansion/smelter, which has 732 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.
Source: software-mansion/smelter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.