Pnpm Engine
teambit/bit
Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.
Run the full API change workflow after modifying types in smelter-api.
Install API Change
$ npx skills add software-mansion/smelter --skill api-change -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install software-mansion/smelter api-change --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/api-change .claude/skills/api-change && 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 "api-change" agent skill from https://github.com/software-mansion/smelter/tree/master/.claude/skills/api-change into .claude/skills/api-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-change", 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/api-changeType 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 api-change -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install software-mansion/smelter api-change --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/api-change .agents/skills/api-change && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "api-change" agent skill from https://github.com/software-mansion/smelter/tree/master/.claude/skills/api-change into .agents/skills/api-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-change", 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 api-change -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install software-mansion/smelter api-change --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/api-change .cursor/skills/api-change && 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 "api-change" agent skill from https://github.com/software-mansion/smelter/tree/master/.claude/skills/api-change into .cursor/skills/api-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-change", 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/api-change--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 api-change -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install software-mansion/smelter api-change --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/api-change .gemini/skills/api-change && 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 "api-change" agent skill from https://github.com/software-mansion/smelter/tree/master/.claude/skills/api-change into .gemini/skills/api-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-change", 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 api-changeInstalls 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 api-change -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/api-change .github/skills/api-change && 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 "api-change" agent skill from https://github.com/software-mansion/smelter/tree/master/.claude/skills/api-change into .github/skills/api-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-change", 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 api-change -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 api-change --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/api-change .opencode/skills/api-change && 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 "api-change" agent skill from https://github.com/software-mansion/smelter/tree/master/.claude/skills/api-change into .opencode/skills/api-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-change", 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
api-change- GitHub stars
- 732
- Token cost
- ~450 tokens
- SKILL.md length
- 199 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Run the full API change workflow after modifying types in smelter-api.
- Works in 6 steps: Register new routes in OpenAPI spec → Generate JSON schemas from Rust types → Generate TypeScript types from schemas → …
- Tasks that involve Type safety
- Calls pnpm and cargo
What it does
API Change is an agent skill from software-mansion/smelter. Run the full API change workflow after modifying types in smelter-api. Generates schemas, TypeScript types, and verifies everything is in sync.
Its SKILL.md is about 450 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 Type safety. It works with Rust, React and pnpm. The repository describes itself as: Toolkit for real-time, low latency, programmable video and audio mixing.
When your agent uses it
- Tasks that involve Type safety
Example prompts
- “/api-change”
Requirements
- Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Register new routes in OpenAPI spec
- Generate JSON schemas from Rust types
- Generate TypeScript types from schemas
- Build the TypeScript SDK to verify compatibility
- Show a summary of all generated/changed files so the user can review what was affected.
- Try to update SDK
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:
pnpmcargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, 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
API Change loads about 450 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 199 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 199 words (~450 tokens).
“Run the API change workflow. All steps must pass before the change is considered complete.”
- name
- api-change
- allowed-tools
- Bash, Read, Grep, Glob
- disable-model-invocation
- false
Files
Just SKILL.md in .claude/skills/api-change of software-mansion/smelter.
Open the folder on GitHubat commit f3b8293
Compare with similar skills
API Change 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 |
|---|---|---|---|---|---|---|
| API Change this skillsoftware-mansion/smelter | 732 | — | ~450 | Automated safety check: Notes | Custom licence | |
| Pnpm Engineteambit/bit | 18k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Sentry Fixdifferent-ai-studio/teamclu | 167 | — | ~2.2k | Automated safety check: Pass | MIT | |
| @pierre/diffs Code Renderingpierrecomputer/pierre | 6.2k | 2 repos | ~803 | Automated safety check: Pass | Apache-2.0 | |
| RTK Rust Design Patternsrtk-ai/rtk | 83k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Wagmi Feature Developmentwevm/wagmi | 6.8k | — | ~3.8k | Automated safety check: Pass | MIT |
Similar skills
Sentry Fix
different-ai-studio/teamclu
A skill your agent uses when the user wants to fix a Sentry issue, auto-repair a bug from Sentry, or create a fix PR for a Sentry error.
@pierre/diffs Code Rendering
pierrecomputer/pierre
Guides an agent through using @pierre/diffs to render syntax-highlighted files and diffs, and to build editing and review surfaces in React or plain JavaScript.
RTK Rust Design Patterns
rtk-ai/rtk
Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.
Wagmi Feature Development
wevm/wagmi
Walks through adding a Wagmi feature across its layers: a Viem-based core action, TanStack Query options, and React and Vue bindings.
Rust Path Types
openinterpreter/openinterpreter
Rules for choosing Rust types for filesystem paths in new Codex code, covering protocol types, internal use and model tool arguments.
More from software-mansion/smelter
Create Release Checklist
software-mansion/smelter
Generate a GitHub release-checklist issue for a full (non-RC) release of the Smelter server and/or the TypeScript SDK.
Related
Categories
Questions about API Change
What does API Change do?
Run the full API change workflow after modifying types in smelter-api. API Change is an agent skill from software-mansion/smelter. Run the full API change workflow after modifying types in smelter-api.
When should I use API Change?
API Change fits situations like: tasks that involve Type safety.
How do I install API Change in Claude Code?
Run `npx skills add software-mansion/smelter --skill api-change -a claude-code`. Or copy the skill folder (.claude/skills/api-change in software-mansion/smelter) into .claude/skills/api-change in your project. Claude Code loads it when a task matches its description.
How do I install API Change in Codex?
Run `npx skills add software-mansion/smelter --skill api-change -a codex`. Or copy the skill folder (.claude/skills/api-change in software-mansion/smelter) into .agents/skills/api-change in your project. Codex loads it when a task matches its description.
Can I use API Change 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 api-change -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-change, .gemini/skills/api-change, .github/skills/api-change and .opencode/skills/api-change in your project.
What does API Change need to run?
Going by SKILL.md and its folder, API Change needs the command-line tools its instructions call (pnpm and cargo). Its frontmatter pre-approves these tools: Bash, Read, Grep, Glob.
Does API Change 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 API Change 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 API Change use?
API Change 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 API Change use?
About 450 tokens (SKILL.md is roughly 1.8k 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 API Change?
Skills that share tags, products or a category with API Change: Pnpm Engine (teambit/bit, 18k stars), Sentry Fix (different-ai-studio/teamclu, 167 stars), @pierre/diffs Code Rendering (pierrecomputer/pierre, 6.2k stars) and RTK Rust Design Patterns (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains API Change?
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.