Skip to content
Built on agentskills.io · 30+ tools

SkillRepo is the open registry for agent skills.

A permanent home for publishers. A curated library your team installs from. Built on the open agentskills.io format.

The publisher's problem

Right now, your skills are invisible.

People find them by accident, or not at all — a Google search for the exact name, a link somebody tweeted, a year-old blog post.

The skills are good. The distribution is a scavenger hunt.

Software has maintainers. Skills just have authors.

Someone copied one of your skills in January. A junior dev you've never met is running that copy now and assumes it's current. Every fix and improvement you've shipped since is stuck where you published it. Your best work gets flattened into “some file from the internet.”

The team's problem

Right now, every engineer is running their own setup.

Three people on your team used roughly the same skill last quarter; two of them don't know about each other's version. Your senior engineer has a setup that actually works — nobody else can see what's in it. New hires ask whoever happens to be around and pick different answers.

What a registry actually does

From scattered files to shared infrastructure.

Packages got npm. Containers got Docker Hub. Python libraries got PyPI.

Skills get SkillRepo.

01

A format emerged. Distribution didn’t.

The standard showed up — agentskills.io, adopted by 30+ tools. The registry didn’t. A format without distribution is packages without npm. Vendor CLIs handle the install. A registry handles what to install, from whom, graded how, and what your team curates — reachable from every agent.

02

Every skill has an author.

If we’ve already ingested your work from a public repo, it’s attributed to the GitHub username we found. Sign up with GitHub — or connect your GitHub account — to claim those skills.

03

Know what you’re installing.

36.8% of public skills contain a security flaw (Snyk, Feb 2026). Two-layer analysis on every publish: static checks plus an AI pass across safety, quality, clarity, completeness. Each skill ships with an A–F grade and the findings behind it. Grades are signals, not a certification. Always review a skill yourself before use.

The two doors

Two ways this changes your week.

If you publish

Your skills, discoverable.

  • A permanent URL and namespace tied to your GitHub identity — claimed once, yours.
  • Grading and install counts show which of your skills land.
  • Your publisher page is the portfolio — every skill, every install, one link to share.
  • More to come.
If you manage a team

Five engineers. Five agents. Five slightly different versions of the same skill.

You don't realize it until the output diverges — your codebase starts looking like it was written by five different teams because every agent was working from a different copy of “how we do things.”

A team library on SkillRepo flips it. You curate one shared set of skills; every engineer's agent pulls from the same place. Your code starts looking like your team wrote it.

Teams from $8/seat/month. No seat minimum. 14-day trial, no card.

Command Palette

Search for a command to run...