toolkit-updates
Skill1 starsChanged 33 days agoMITView on GitHub
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. Triggers: 'are my toolkit skills up to date', 'check for updates', 'what changed in the toolkit', 'is there a new version of video-watch', 'update my skills', 'what is new in the toolkit', 'toolkit updates'. 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.
In this repository20 other files it gives its agents.
- audio-narrateSkill
- audio-transcribeSkill
- cloudflare-opsSkill
- dokploy-opsSkill
- elevenlabs-studioSkill
- hetzner-opsSkill
- higgsfield-studio-brandkitSkill
- higgsfield-studio-marketplace-cardsSkill
- higgsfield-studio-product-photoshootSkill
- higgsfield-studioSkill
- higgsfield-studio-soul-idSkill
- higgsfield-studio-video-explainerSkill
- higgsfield-studio-websitesSkill
- higgsfield-studio-youtube-thumbnailSkill
- image-promptSkill
- namecheap-opsSkill
- plane-fleetSkill
- toolkit-credentialsSkill
- video-promptSkill
- video-watchSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Start with the answer: everything is current, or which skills have a newer version.
- Distinctive: line 37
Put any breaking change first and say what the user has to do.
- Distinctive: line 38
If the same skill is installed in more than one place, say so.
- Distinctive: line 39
If a skill is newer than the feed says, it is most likely a development copy.
- Very specific: line 45
If the feed cannot be read, the script says why and exits with 2.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
toolkit-updates
Tells the user which toolkit skills on this machine have a newer version, and what exactly changed in each one. It only reads. Updating is a separate step that the user approves.
Who you are doing this for
The user may not be technical. Say what changed in plain words, in the order it matters, and do not paste raw output. They should be able to decide "yes, update" or "not now" from your summary alone.
Run it
node scripts/check.mjsIt looks in the folders agents keep skills in, finds the toolkit skills by name and publisher, reads the version each one declares, and compares it with the public update feed. Add --available to also list toolkit skills that are not installed. Add --json if you would rather read structured output. If a skill lives somewhere unusual, add --dir <folder>.
The exit code says the result without reading the text: 0 all current, 10 an update is available, 2 the feed could not be read.
What to tell the user
- Start with the answer: everything is current, or which skills have a newer version.
- For each skill with an update, give the installed and the new version, then what changed, in the user's terms. Say what they can now do, not what files moved.
- Put any breaking change first and say what the user has to do. A breaking change means the update alone is not enough.
- If the same skill is installed in more than one place, say so. Each copy is updated separately.
- If a skill is newer than the feed says, it is most likely a development copy. Say that and leave it alone.
Updating
Never update without being asked. Show what will change first. When the user says yes, run the command the output gives under "To update" for that copy. It depends on how the copy was installed, so do not guess one. After updating, run the check again and confirm the version moved.
If the feed cannot be read, the script says why and exits with 2. Do not invent versions. Each installed skill has a CHANGELOG.md whose Latest: line is an address the user can open to check by hand.
Limits
- It only sees skills from this publisher. A skill with the same name from someone else is ignored on purpose.
- It only looks in the usual folders. Anything else needs
--dir. - It reports and advises. It does not install or update by itself.
Updates
This skill is versioned. Its version is metadata.version in the header of this file. CHANGELOG.md in this folder lists what changed in each version, newest first.
To check for a newer version, open the address on the Latest: line of CHANGELOG.md and compare its top version with the installed one. If the newer one is ahead, read every entry between the two and tell the user what changed before anything is updated. A Breaking section means the user has to do something. To update, reinstall the skill from its source repository, the same way it was installed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.