The Problem

You've got a SKILL.md you wrote for one project. Someone else wrote a better one for the same thing. There's no way to find theirs, no way to share yours, and everyone's reinventing the same browser-testing or commit-formatting skill in their own .claude/skills/ directory. Classic fragmentation problem.

skills.sh is a package manager for agent skills. npx skills find to discover what's out there, npx skills add to install one. That's the whole workflow.

How It Works

# Find skills for a task
npx skills find "browser testing"

# Install a skill
npx skills add browserbase/skills/browser

# List what you've got
npx skills list

Skills get installed into your .claude/skills/ directory (or equivalent for other agents). The registry is community-driven. Vercel Labs has a bunch. Browserbase ships three. People publish their own.

Why It Matters

The skill ecosystem was heading toward a world where everyone copies SKILL.md files from GitHub repos manually. skills.sh turns that into npx skills add and now you've got versioning, discovery, and a shared registry. Same thing npm did for JavaScript packages in 2012. Obvious in retrospect, but someone had to build it.

Not everything on there is gold. Quality varies. But the pattern is right and the directory is growing fast. Worth checking before you write a skill from scratch. Someone's probably already built it.