Alternatives
The other ways teams share AI skills, compared honestly.
Every team already has a way of passing skills around: a shared repository, a public directory, a registry, or a message in chat. These pages set Skills Board next to each option, say plainly when the other one is the better choice, and link every competitor claim to a public page you can check yourself.
Comparisons
A shared GitHub repository
The shared GitHub repo, and the alternative to it
The default setup for engineering teams. Where it holds up, where a shared library fits better, and how to run both.
skills.sh
Skills Board vs skills.sh
A public directory with a leaderboard and packs, next to a private team library. Where each one belongs.
Smithery
Skills Board vs Smithery
A public registry with managed connections, next to a team-curated library. Two different problems.
How these pages work
What Skills Board is, in one paragraph
Skills Board is a shared library for the AI skills a team recommends. A teammate saves a skill from its original repository and path, adds the tags the team searches by, and everyone else finds it later. Each person then picks how to use it: open the source, copy an install command, download a ZIP of the latest files, or connect a compatible agent to an authenticated MCP endpoint. The hosted product is free forever, the code is MIT licensed, and a saved skill is a team recommendation rather than a formal review.
Start the library and see which comparison still matters.
Creating a team library takes a minute and costs nothing. Save one skill, invite one teammate, and judge it from there.