Update Request | Should you upgrade Vercel skills CLI to v1.5.22? Three controlled comparisons

Direct answer

Vercel skills CLI v1.5.22 is worth testing now if your Skill repository has nested categories, one Skill is shared by several Agents, or you need MiniMax Code support. Against v1.5.21 in the same environment, v1.5.22 found two nested Skills instead of one, retained the shared lock entry after removing only Codex, and installed successfully to MiniMax Code instead of rejecting the Agent name.

The recommendation remains conditional. Those three paths passed locally and the upstream repository's 740 tests passed, but we did not independently reproduce live skills.sh/well-known updates, self-hosted GitHub host retention, or a real team's global Skill directories.

What changed in v1.5.22

Vercel released v1.5.22 on August 5, 2026. The changelog includes ten changes; four directly affect installation state:

• discovery now reaches Skills below multiple category levels;
• well-known sources and skills.sh packs can surface upstream additions during update;
• removing a shared Skill from one Agent no longer drops the lock entry while another Agent still uses it;
• minimax-code is now a supported target under .minimax/skills/.

The release also covers GitHub shorthand normalization, preservation of self-hosted GitHub hosts, complete non-interactive find output, and portable local paths. We did not label every changelog item as independently tested.

Fixed versions and fixture

The v1.5.22 tag was pinned to commit a4d243c3d4f86cdf9385dd1b6a0733f6937e70b5; v1.5.21 was pinned to 7cb7db64dc1201052dea305e508a2fc490f7e5e2. All fixtures and installs stayed under /tmp/token-beggars-skills-v1522.*; no global user Skill directory was modified.

skills/core-skills/amazon-bedrock/SKILL.md
skills/specialized-skills/database-skills/amazon-dynamodb/SKILL.md

Comparison 1: nested discovery

npx --yes skills@1.5.21 add ./fixture --list
npx --yes skills@1.5.22 add ./fixture --list

v1.5.21 reported one Skill and omitted amazon-dynamodb. v1.5.22 reported both Skills. Both commands exited normally, showing that the older failure mode could be a silent omission rather than an error.

Comparison 2: shared lock retention

We installed amazon-bedrock for Codex and Claude Code, then removed it only from Codex. In both versions, the shared directory and Claude Code link remained. The lock state differed: v1.5.21 left no Skill key in skills-lock.json; v1.5.22 retained amazon-bedrock. The new behavior keeps lock state aligned with files that are still in use.

Comparison 3: MiniMax Code

With --agent minimax-code, v1.5.21 returned Invalid agents: minimax-code and exit code 1. v1.5.22 installed to .minimax/skills/amazon-bedrock and exited 0. This verifies one local, single-Skill, non-interactive install path.

Upstream verification

On the official v1.5.22 checkout, the TypeScript check passed. A focused run covered nested discovery, well-known update, removal, update source, MiniMax Code, and non-interactive find: 100 tests across six files passed. The full run passed 740 tests across 55 files.

These results validate the release commit's regression suite; they do not replace live external-system testing. In particular, skills.sh and well-known update behavior was covered by upstream tests, not by an independent public registry experiment.

Upgrade checklist

1. Back up skills-lock.json.
2. Run npx skills@1.5.22 add <source> --list and compare names and counts.
3. Run one update in a temporary project and inspect the source URL and host.
4. Remove a shared Skill from only one Agent, then verify the remaining links and lock entry.
5. Review the lock diff before making v1.5.22 the team default.

If your workflow only installs flat local directories and never uses update or remove, the immediate benefit is smaller. Do not change a stable environment only because a newer version exists.

— Token Beggars Editorial

References

• Vercel skills CLI repository at v1.5.22