The skill atlas
Public agent skills, organised the way your company works and rated one by one.
139,726 skills from GitHub, grouped by department, team and the work each team does. Find one for the job in front of you, see how it scored and why, and read its safety verdict before you install it.
- 139,726 Skills indexed Public agent skills from GitHub, each with a rated page.
- 276 Categories Kinds of work, grouped into teams and departments.
- 27,503 Launch-quality skills Graded A to C with a clean safety verdict, and not excluded by a quality filter.
- 4,310 Duplicates merged Copies in other repositories, merged into one page per skill.
Organised like a company
Department, then team, then the work that team does. You find a skill where your team would look, not in one long list of tags.
Independently rated and safety-scanned
A grade from A to F by our published scoring engine, and a safety scan that can cap it. Each page shows the evidence: what the scan found and, where they exist, a judge model's review and head-to-head results from real tasks.
Duplicates merged
Skills get copied from repository to repository. We merge the copies and keep the one from the most-starred repository.
Your agent can use it
Connect the MCP server and Claude Code, Cursor or any other MCP client can search the launch-quality skills by the problem it needs solved, and read our rating before it installs anything.
The largest departments
The app
Every skill on the machine, filed by the work it does.
Drag the map around. Departments with nothing in them are called out in red.
Why it works
A skill carries the part nobody has time to explain.
The gotchas. The checks. The three things that go wrong every time and the one order that avoids them. Your best engineer knows all of it and is never going to write the document.
Writing a skill is something they do while working, and the result runs inside everyone else's agent. Nobody becomes as good as the person who wrote it. They get most of the way there without having to interrupt them.
The interruption you do not make
Most of what stops you is not your own job. It is the bit of infrastructure, or data, or contract language that belongs to another team. You could do it yourself if you knew the five things they know, so you ask them instead, and they stop what they are doing.
A skill from that department is those five things. You do not become a platform engineer. You stop needing one in the room to get unblocked.
Closed beta
We are letting teams in a few at a time.
Leave your email and we will keep you posted on how it is going, and add you as soon as we can.
Email info@xyspace.dev to join.
One email when there is something worth telling you. No sequence, no drip, and we will not pass your address on.