A skills.sh alternative, or a companion
skills.sh is a public registry: you find a skill, then install it with npx skills add. Hubskillz answers the next question, the one about the version your whole team actually runs.
skills.sh is the best place to find a skill and install it in one command, across some twenty different agents. It does not decide which version your team runs, and an update rewrites the instructions with nobody reviewing them. The two fit together: the registry publishes, Hubskillz pins the approved version and tracks upstream.
Last updated: August 30, 2026
At a glance
| Criterion | skills.sh | Hubskillz |
|---|---|---|
| Role | Public registry: find and install | Internal directory: approve and maintain |
| Content | Publicly published skills | Your organization’s skills, public ones and your own |
| Install | npx skills add owner/repo, machine by machine | hubskillz sync --all, every machine and every project |
| Agents supported | Around twenty, from Claude Code to Cursor, Codex, Copilot and Windsurf | Claude Code through the CLI, claude.ai through a ZIP export |
| Upstream update | npx skills update, run by hand, with no review step | Detected, with the diff and the Snyk and Socket audits |
| Approval | No internal step | A maintainer reads the diff before machines move |
| Local drift | Invisible | Flagged as customized on the machine concerned |
| Without a terminal | Terminal required | Browser, plus a ZIP export for claude.ai |
| Team scope | Everyone picks their own | Required and recommended skills, per team |
What skills.sh does
The registry solves discovery. One command installs a skill someone else wrote, and the work starts within the minute. It is by far the fastest way to try a skill out.
Its reach goes well beyond Claude Code: the same command installs for Cursor, Codex, Copilot, Windsurf and fifteen or so other agents. Hubskillz covers Claude Code and claude.ai, and makes no claim to that breadth today.
Installing freezes the content as it stood that day. Nothing changes on the machine afterwards until npx skills update runs.
What is missing at team scale
Every install is local. Eight people installing the same skill across three weeks end up with eight slightly different folders, and nobody knows.
An upstream update rewrites the instructions an agent will follow on your code. With no reading step, that change reaches production through a command someone ran on a Tuesday evening.
The skills your team writes itself go through a separate Git repo, private or public, and a second install command. No review step sits between the commit and the machines.
Both together
This is the intended use. A skill installed from skills.sh is pinned in the directory at its installed version. When skills.sh publishes a new one, Hubskillz raises a draft carrying the diff and the Snyk and Socket audits, and no machine changes until a maintainer approves it.
Skills written in house travel the same path, which leaves one list to read and one command to run.
When skills.sh is enough
You work alone, or you are trying skills out before sharing them: the registry covers the whole need, and Hubskillz stays free on the day the team shows up.
Frequently asked questions
Is Hubskillz a public skill registry?
No. The directory is private to your organization. To discover public skills, skills.sh is the right place, and Hubskillz then keeps your copy under control.
What if upstream publishes a dangerous version?
It arrives as a draft, with the line by line diff and the Snyk and Socket results attached. Rejecting the draft leaves every machine on the previously approved version.
Next steps
Other comparisons
- A Git repo of skills, or HubskillzVersion the skills in a repo, copy them onto each machine by hand.
- Claude Code plugins, or HubskillzBundle the skills into a plugin, let everyone install it from a marketplace.
- skills.sh vs Claude Code pluginsThe two ways to distribute skills without copying anything, compared against each other.
- Hubskillz alternatives