Agent skill

Check SDK Updates

by tony1223 in tony1223/better-agent-terminal

Check whether Claude Code, Claude Agent SDK, and Codex SDK have new versions on npm.

MITAuto-check passedDevelopment

Install Check SDK Updates

skills CLI

$ npx skills add tony1223/better-agent-terminal --skill check-sdk-updates -a claude-code

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

GitHub CLI

$ gh skill install tony1223/better-agent-terminal check-sdk-updates --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/tony1223/better-agent-terminal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/check-sdk-updates .claude/skills/check-sdk-updates && 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/

Paste into Claude Code

Install the "check-sdk-updates" agent skill from https://github.com/tony1223/better-agent-terminal/tree/main/.claude/skills/check-sdk-updates into .claude/skills/check-sdk-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-sdk-updates", 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

$skill-installer install https://github.com/tony1223/better-agent-terminal/tree/main/.claude/skills/check-sdk-updates

Type 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.

skills CLI

$ npx skills add tony1223/better-agent-terminal --skill check-sdk-updates -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install tony1223/better-agent-terminal check-sdk-updates --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tony1223/better-agent-terminal.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/check-sdk-updates .agents/skills/check-sdk-updates && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "check-sdk-updates" agent skill from https://github.com/tony1223/better-agent-terminal/tree/main/.claude/skills/check-sdk-updates into .agents/skills/check-sdk-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-sdk-updates", 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.

skills CLI

$ npx skills add tony1223/better-agent-terminal --skill check-sdk-updates -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install tony1223/better-agent-terminal check-sdk-updates --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tony1223/better-agent-terminal.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/check-sdk-updates .cursor/skills/check-sdk-updates && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "check-sdk-updates" agent skill from https://github.com/tony1223/better-agent-terminal/tree/main/.claude/skills/check-sdk-updates into .cursor/skills/check-sdk-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-sdk-updates", 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

$ gemini skills install https://github.com/tony1223/better-agent-terminal.git --path .claude/skills/check-sdk-updates

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add tony1223/better-agent-terminal --skill check-sdk-updates -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install tony1223/better-agent-terminal check-sdk-updates --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tony1223/better-agent-terminal.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/check-sdk-updates .gemini/skills/check-sdk-updates && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "check-sdk-updates" agent skill from https://github.com/tony1223/better-agent-terminal/tree/main/.claude/skills/check-sdk-updates into .gemini/skills/check-sdk-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-sdk-updates", 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.

GitHub CLI

$ gh skill install tony1223/better-agent-terminal check-sdk-updates

Installs 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).

skills CLI

$ npx skills add tony1223/better-agent-terminal --skill check-sdk-updates -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/tony1223/better-agent-terminal.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/check-sdk-updates .github/skills/check-sdk-updates && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "check-sdk-updates" agent skill from https://github.com/tony1223/better-agent-terminal/tree/main/.claude/skills/check-sdk-updates into .github/skills/check-sdk-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-sdk-updates", 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.

skills CLI

$ npx skills add tony1223/better-agent-terminal --skill check-sdk-updates -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install tony1223/better-agent-terminal check-sdk-updates --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tony1223/better-agent-terminal.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/check-sdk-updates .opencode/skills/check-sdk-updates && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "check-sdk-updates" agent skill from https://github.com/tony1223/better-agent-terminal/tree/main/.claude/skills/check-sdk-updates into .opencode/skills/check-sdk-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-sdk-updates", 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-sdk-updates
GitHub stars: 518
Token cost: ~886 tokens
SKILL.md length: 369 words
Files: 1
Skills in repo: 1
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Check whether Claude Code, Claude Agent SDK, and Codex SDK have new versions on npm.

Works in 5 steps: Read the dependencies block of… → Run the following command (single Bash… → For each package, compare the declared… → …
The user asks to check for SDK/CLI updates
SKILL.md covers Steps and Notes
Calls npm and gh

What it does

Check SDK Updates is an agent skill from tony1223/better-agent-terminal. Check whether Claude Code, Claude Agent SDK, and Codex SDK have new versions on npm. Use when the user asks to check for SDK/CLI updates, e.g. "check sdk updates", "check claude code update", "有沒有更新", "檢查 SDK 版本".

Its SKILL.md is about 890 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. It works with npm and Claude Agent SDK. The repository describes itself as: Multi-workspace terminal aggregator with Claude Code AI integration. The licence is MIT.

When your agent uses it

The user asks to check for SDK/CLI updates

Example prompts

“check sdk updates”
“check claude code update”
“檢查 SDK 版本”
“/check-sdk-updates”

Requirements

Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Read the dependencies block of package.json and extract the current declared range for each of
Run the following command (single Bash call) to fetch latest versions in parallel
For each package, compare the declared version (strip leading ^/~) with the latest. Report a compact table
For each outdated package, analyze the gap between current and latest so the user can decide how to implement the update. For each one
After the per-package analysis, suggest the exact npm install command to bump them, e.g.

What it can do on your machine

Read from SKILL.md and the folder at commit b741989. 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
Shell commands in SKILL.md call:
- npm
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm 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

Check SDK Updates loads about 886 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 369 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~58
When it runs · the whole SKILL.md, loaded when a task matches: ~886

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 tony1223/better-agent-terminal at commit b741989, republished under its MIT licence (© tony1223). 369 words, ~886 tokens.

Download SKILL.mdSave it as .claude/skills/check-sdk-updates/SKILL.md (or your agent's skills folder).

name: check-sdk-updates
description: Check whether Claude Code, Claude Agent SDK, and Codex SDK have new versions on npm. Use when the user asks to check for SDK/CLI updates, e.g. "check sdk updates", "check claude code update", "有沒有更新", "檢查 SDK 版本".

Check SDK Updates

Compare the versions of @anthropic-ai/claude-code, @anthropic-ai/claude-agent-sdk, and @openai/codex-sdk declared in package.json against the latest published version on npm.

Steps

Read the dependencies block of package.json and extract the current declared range for each of:
- @anthropic-ai/claude-code
- @anthropic-ai/claude-agent-sdk
- @openai/codex-sdk
Run the following command (single Bash call) to fetch latest versions in parallel:
bash
```
npm view @anthropic-ai/claude-code version & \
npm view @anthropic-ai/claude-agent-sdk version & \
npm view @openai/codex-sdk version & \
wait
```
Map the three lines of output back to the three packages in the order requested.

For each package, compare the declared version (strip leading ^/~) with the latest. Report a compact table:

Package                              Current    Latest     Status
@anthropic-ai/claude-code            2.1.119    2.1.120    ⬆ update
@anthropic-ai/claude-agent-sdk       0.2.119    0.2.119    ✓ up to date
@openai/codex-sdk                    0.125.0    0.126.0    ⬆ update

For each outdated package, analyze the gap between current and latest so the user can decide how to implement the update. For each one:

a. Get the list of versions in between with:
bash
```
npm view <pkg> versions --json
```
Filter to versions strictly greater than current and ≤ latest. Note the count and span (patch / minor / major bumps).

b. Try to fetch release notes / changelog. Try in this order, stop at the first that works:
- npm view <pkg> repository.url → if it points to a GitHub repo, use gh release list -R <owner/repo> --limit 30 and gh release view <tag> -R <owner/repo> for the relevant tags.
- Look for a CHANGELOG.md inside node_modules/<pkg>/ (already-installed copy reflects the current version, but its history section may still cover newer versions if upstream backfills).
- Fall back to: npm view <pkg>@<latest> --json and read the description / homepage fields, then WebFetch the homepage's changelog/releases page.
c. Summarise per package in 2–4 bullets:
- Number of versions skipped (e.g. "5 patch releases, 1 minor")
- Any breaking changes or notable API/CLI changes
- Any items that touch the parts of our codebase that consume this SDK (e.g. electron/claude-agent-manager.ts, electron/codex-agent-manager.ts, electron/openai-agent-manager.ts)
- Risk assessment: low / medium / high, with one-line justification
After the per-package analysis, suggest the exact npm install command to bump them, e.g.:
```
npm install @anthropic-ai/claude-code@latest @openai/codex-sdk@latest
```
Group low-risk bumps together; call out any high-risk bump as needing a separate, careful update. Do NOT run the install — only suggest it. Wait for the user's confirmation before installing.

Show full SKILL.md (40 more words)Show less

Notes

Use npm view (not npm outdated) so the check works without touching the lockfile or node_modules.
If npm view fails (offline / registry error), report which package failed and stop.
Keep the output short — table + suggested install line is enough.

Files

Just SKILL.md in .claude/skills/check-sdk-updates of tony1223/better-agent-terminal.

Open the folder on GitHubat commit b741989

Compare with similar skills

Check SDK Updates 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.

Check SDK Updates compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Check SDK Updates this skilltony1223/better-agent-terminal	518	—	~886	Automated safety check: Pass	MIT	5 days ago
Agent SDK Version Bumppreset-io/agor	1.4k	—	~1.4k	Automated safety check: Pass	Custom licence	today
Helmor Bump Vendorsdohooo/helmor	1.3k	—	~2.1k	Automated safety check: Pass	Apache-2.0	1 mo ago
Nx Run Tasksnomcopter/react-mosaic	4.8k	8 repos	~613	Automated safety check: Pass	Custom licence	11 days ago
Migrate Internal Package into GhostTryGhost/Ghost	56k	—	~3.8k	Automated safety check: Pass	MIT	today
Open Code Review CLIalibaba/open-code-review	46k	—	~3.1k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Agent SDK Version Bump
preset-io/agor
Upgrades a pinned agent SDK in the agor project, such as the Claude, Codex or Gemini CLI one, and plans the release that carries it to packaged installs.
1.4k GitHub stars~1.4k tokensUpdated today
Agent WorkflowsAuto-check passed
Helmor Bump Vendors
dohooo/helmor
Bump or upgrade the pinned versions of Helmor's bundled agent CLIs, SDKs, and supporting binaries — Claude Code + claude-agent-sdk (lockstep), Codex, Cursor SDK, OpenCode, Kimi, Pi, and gh / glab /…
1.3k GitHub stars~2.1k tokensUpdated 1 mo ago
Agent WorkflowsAuto-check passed
Nx Run Tasks
nomcopter/react-mosaic
Helps with running tasks in an Nx workspace. An agent skill from nomcopter/react-mosaic.
4.8k GitHub starsUsed in 8 repos~613 tokens
DevelopmentAuto-check passed
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
56k GitHub stars~3.8k tokensUpdated today
DevelopmentAuto-check passed
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
46k GitHub stars~3.1k tokensUpdated today
DevelopmentAuto-check passed
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.
38k GitHub stars~3.2k tokensUpdated today
DevelopmentAuto-check passed

Works with

Questions about Check SDK Updates

What does Check SDK Updates do?

Check whether Claude Code, Claude Agent SDK, and Codex SDK have new versions on npm. Check SDK Updates is an agent skill from tony1223/better-agent-terminal. Check whether Claude Code, Claude Agent SDK, and Codex SDK have new versions on npm.

When should I use Check SDK Updates?

Check SDK Updates fits situations like: the user asks to check for SDK/CLI updates.

How do I install Check SDK Updates in Claude Code?

Run `npx skills add tony1223/better-agent-terminal --skill check-sdk-updates -a claude-code`. Or copy the skill folder (.claude/skills/check-sdk-updates in tony1223/better-agent-terminal) into .claude/skills/check-sdk-updates in your project. Claude Code loads it when a task matches its description.

How do I install Check SDK Updates in Codex?

Run `npx skills add tony1223/better-agent-terminal --skill check-sdk-updates -a codex`. Or copy the skill folder (.claude/skills/check-sdk-updates in tony1223/better-agent-terminal) into .agents/skills/check-sdk-updates in your project. Codex loads it when a task matches its description.

Can I use Check SDK Updates 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 tony1223/better-agent-terminal --skill check-sdk-updates -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-sdk-updates, .gemini/skills/check-sdk-updates, .github/skills/check-sdk-updates and .opencode/skills/check-sdk-updates in your project.

What does Check SDK Updates need to run?

Going by SKILL.md and its folder, Check SDK Updates needs the command-line tools its instructions call (npm and gh). Our summary lists: Node.js.

Does Check SDK Updates access the network?

SKILL.md contains no URLs. Its commands use npm and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Check SDK Updates 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 Check SDK Updates use?

Check SDK Updates is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Check SDK Updates use?

About 886 tokens (SKILL.md is roughly 3.5k 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 SDK Updates?

Skills that share tags, products or a category with Check SDK Updates: Agent SDK Version Bump (preset-io/agor, 1.4k stars), Helmor Bump Vendors (dohooo/helmor, 1.3k stars), Nx Run Tasks (nomcopter/react-mosaic, 4.8k stars) and Migrate Internal Package into Ghost (TryGhost/Ghost, 56k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Check SDK Updates?

tony1223 (a GitHub user) maintains it in tony1223/better-agent-terminal, which has 518 GitHub stars. The repository was last updated on October 5, 2026.

Source: tony1223/better-agent-terminal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Check SDK Updates

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Check SDK Updates

Steps

Notes

Files

Compare with similar skills

Similar skills

Agent SDK Version Bump

Helmor Bump Vendors

Nx Run Tasks

Migrate Internal Package into Ghost

Open Code Review CLI

Cutting A Release

Related

Questions about Check SDK Updates