Right now, your skills are invisible.
Free for publishers. Claim your GitHub namespace, keep your work.
Right now, people find your skills by accident.
They find them with a Google search for the exact name, a link somebody tweeted, a year-old blog post — or they don't find them at all. The skills are good. The distribution is a scavenger hunt.
Software has maintainers. Skills just have authors.
And the copy outlives the original.
Someone copied one of your skills in January. A developer you've never met is running that copy now and assumes it's current. Every fix you've shipped since is stuck where you published it. Your best work gets flattened into “some file from the internet.”
A permanent identity, tied to your GitHub.
Publish to SkillRepo and every skill gets a permanent home under your GitHub namespace — a URL that's yours, attribution that travels with the work, and a version history people can trust.
If we've already ingested your skills from a public repo, they're attributed to the GitHub username we found. Sign in with GitHub to claim them — the namespace, and the credit, are yours.
Your skills get found.
Every published skill gets a public page in the catalog — browsable and searchable by anyone looking for what you've built. No login wall, no scavenger hunt.
And it shows up with its grade. Every skill is scored A–F by a two-layer analysis — static checks plus an AI pass — so quality is visible at a glance and strong work stands out instead of getting lost.
Grades are signals, not a certification — but they give good work a reason to surface.
Distributed to every agent, automatically.
When a team adds your skill to their library, it syncs straight into their setup — as native skill files across all seven supported dev environments: Claude Code, Cursor, Windsurf, VS Code + Copilot, Gemini CLI, Codex CLI, and Cline. You publish once; it lands wherever they work.
Ship an update and it carries forward: the people running your skill pick up the new version on their next sync, instead of being stranded on the copy they grabbed months ago. The maintainer's fix finally reaches everyone running the skill.
A portfolio page, with real numbers.
Your publisher page is the portfolio — every skill you've shipped, one link to share. And it comes with the numbers behind it: library reach (how many accounts hold your skills), download counts, and a per-skill breakdown.
So you can see which of your work is actually getting used — and decide what to build, fix, or promote next based on what's landing, not guesswork.
Free to publish.
Publishing is free. Claim your GitHub namespace, publish your skills, and get the page, the distribution, and the analytics at no cost. You keep your work; we make it reachable.
Questions publishers ask.
- How do people discover my skills?
- Every skill gets a public page in the catalog under your GitHub namespace — browsable and searchable by anyone, with its A–F grade shown so quality stands out. When a team adds it, it distributes automatically to their agents.
- Do I keep ownership and attribution?
- Yes. Skills publish under your GitHub identity and stay attributed to you. If we ingested your work from a public repo, sign in to claim it — your namespace is yours.
- What analytics do I get?
- Library reach (how many accounts hold your skills), download counts, and a per-skill breakdown — so you can see which of your skills are getting used.
Publish once. Get found, attributed, distributed.
Give your skills a permanent home, real discoverability, automatic distribution to every agent, and the analytics to see what's landing — free.
Free for publishers. Claim your GitHub namespace, keep your work.