Check whether the toolkit skills installed on this machine are up to date, and say exactly what changed in each newer version before anything is updated. Reads the toolkit's public update feed and compares it with the version each installed skill declares. Read-only: it never installs, changes or deletes anything. Needs network access to read the feed.
version
2.1.0
updated
2026-09-21
works in
every conformant agent
needs
node
cost
free · no API key
license
MIT
Say this you do not type commands, you ask
“are my toolkit skills up to date”
“check for updates”
“what changed in the toolkit”
“is there a new version of watch-video”
“update my skills”
“what is new in the toolkit”
“toolkit updates”
Once it is installed, that is the whole interface. Your agent picks the skill
up on its own and runs whatever it needs to. The commands further down are there for anyone who
would rather drive it themselves.
Install pick your agent
Examples copy and go
How it works step by step
It looks in the folders agents keep skills in, in your current project, and in the plugin folders of Claude Code and Codex. A symlinked install counts once.
It keeps only skills whose header says they come from this publisher. A skill with the same name from someone else is ignored.
It reads the version each copy declares, then reads the public update feed.
For every copy that is behind, it lists each release in between, oldest first. A breaking release is marked, and its Breaking lines come first.
It prints the update command that fits how that copy was installed. A Claude Code plugin gets the marketplace command, a Codex plugin gets the Codex one, and a linked copy only needs a git pull.
It never writes, installs or deletes anything.
Limits what it will not do
It only sees skills from this publisher, in the usual folders. Anything else needs --dir.
It reports and advises. It does not update by itself, on purpose.
If the feed is down, it says so and stops. It does not guess a version.
A copy whose header has no version shows as 0.0.0, so it always looks behind.
Claude Code keeps old versions in its plugin cache after an update. Codex replaces them. It treats the newest cached version as the installed one, and does not read the agent's own record of which version is enabled.
Changelog what changed, newest first
2.1.0
Added
The tool has its own icon, in a dark and a light version. Codex shows it on the plugin card and in the skill list, and the toolkit site shows it on the tool's page and in share previews.
2.0.0breaking
Breaking
Installed as a Claude Code plugin, the slash command is now /toolkit-updates:toolkit-updates, with the plugin name in front. This has been true since 1.1.0, and this release marks it as breaking. Use the new name, or ask in words, which works as before. A copy in a skills folder keeps the plain name /toolkit-updates.
Added
Codex now shows a display name, a short line and a starter prompt for the skill in its skill list. They come from a generated agents/openai.yaml inside the skill folder. Other agents ignore that file.
Changed
The description now leads with what the skill does, then its trigger phrases, then the detail. Codex shortens long skill lists from the end, so the phrases that route a request now survive far longer. With 40 skills installed, 95% of the phrases stay visible instead of 8%.
Fixed
A skill header with Windows line endings (CRLF) is read correctly, so the version is no longer misread on a Windows checkout.
1.1.0
Added
Finds copies installed as Codex plugins, and gives the Codex update command for them.
Finds Claude Code plugin copies in the newer layout, where the skill sits in a skills/ folder. The older layout still works.
Each line says where the copy lives, so a skill installed in two agents is easy to tell apart.
Can be installed as a Codex plugin, from the same source as everything else.
Changed
Claude Code keeps old versions in its plugin cache after an update. Only the newest one is checked now, so an old folder is no longer reported as behind.
The changelog address now points to the site, so it keeps working if the repository layout changes.
1.0.0
Added
Check every toolkit skill installed on the machine against the public update feed, and list what changed in each newer version.
Finds copies in the folders agents read, in a project, in Claude Code's plugin cache, and behind symlinks.
Marks a breaking change, and gives the exact update command for each copy.
Read-only. Exit code 10 means an update is available, and 2 means the feed could not be read.
Optional --available lists toolkit skills that are not installed yet, and --json gives structured output.
An agent that has this installed reads CHANGELOG.md in the skill folder.
The same history is at changelog.json,
and every tool's releases are at /updates.json.
Just ask
You do not need to run anything. Once the skill is installed, say what you want in your own words:
"are my toolkit skills up to date?""what changed in watch-video?""is there anything new in the toolkit?""update my skills"
The agent checks, tells you in plain words what is new, and puts anything that needs your action first. It does not update anything until you say yes.
Options
Option
Effect
--available
Also list toolkit skills that are not installed
--json
Structured output instead of text
--feed ADDRESS_OR_FILE
Read another feed. Also set by AGENT_TOOLKIT_FEED
--dir FOLDER
Also look in this folder of skills. Repeat it for more
Exit codes: 0 everything is current, 10 an update is available, 2 the feed could not be read, 1 bad usage. That makes it easy to use in a script or a scheduled job.
Requirements
Node 18 or newer. If you do not have it, the skill installs it for you. The agent runs this, or you can:
sh scripts/setup-deps.sh --check # is everything present?
sh scripts/setup-deps.sh # show the install command, ask, then run it
.\scripts\setup-deps.ps1 # Windows
It needs network access to read the feed.
In Codex, the network is off by default, so the check fails with a message that says so. Allow it in ~/.codex/config.toml and run it again. scripts/install.sh prints the exact lines. This skill writes nothing, so it does not need the credential folder.