Claim your skills
If skills are already listed on SkillRepo under your GitHub handle, you can move them into your account. This is a one-time ownership move that never touches your GitHub repositories.
On this page
What attribution is
Skillbot finds public SKILL.md files in public GitHub repositories, mirrors them onto SkillRepo, and lists each one under the GitHub handle it came from. When a skill is listed under your handle, we say it is attributed to you.
These skills are already live on SkillRepo. They have public pages, and anyone can already install them. Nothing about them is waiting on you — attribution simply records where the skill originally came from.
Attribution is not the same as ownership. A skill attributed to your handle is on SkillRepo under your name, but it is not yet in your account. Moving it into your account is the step described below.
What moving them into your account means
Moving your attributed skills into your account is a one-time ownership step. The skills are already on SkillRepo; moving them transfers ownership to your account so you can publish updates and manage them like any skill you authored here.
Their public links do not change. Anyone who already installed or bookmarked one of these skills is unaffected. The same page, at the same address, now belongs to you.
Nothing is fetched from GitHub. These skills were mirrored onto SkillRepo already. Moving them relocates the existing SkillRepo records into your account — it never imports anything new and never touches your GitHub repositories.
You gain control. Once a skill is in your account you can edit it, publish new versions, change its visibility, or remove it — the same things you can do with any skill you author on SkillRepo.
How to do it
Three steps. The whole flow lives inside SkillRepo — you never leave for GitHub beyond the one-time sign-in.
- 1
Sign in with GitHub
Sign in to SkillRepo with the GitHub account your skills are attributed to. If you already signed in another way, connect GitHub from the Settings page under GitHub Identity.
- 2
Review the skills attributed to you
On your getting-started screen, or from the GitHub Identity card in Settings, choose Review your skills to see everything currently listed under your handle.
- 3
Move them to your account
Choose Move all … to my account. Ownership transfers to you, and the skills show up in your My Skills page. Their public links stay exactly as they were.
How we know it is you
Ownership is verified through your GitHub sign-in. Signing in with GitHub proves you control that account, and only that proof lets you add the skills attributed to it.
It is a real sign-in, not a name match. We do not guess ownership by comparing usernames. You have to sign in with the GitHub account itself.
Mixed-case handles work. It does not matter how your handle is capitalized on the skill pages — verification is tied to the account you sign in with, so it lines up regardless of case.
If a skill shares a name with one you own
Sometimes an attributed skill has the same name as one already in your account. Nothing is overwritten. You keep both copies, and you can tidy things up later from your My Skills page — rename one, remove one, or leave them as they are.
If you would rather not have your skills here
You do not have to claim anything, and you can ask us to take your skills down instead. Email hello@skillrepo.dev with the skills you want removed and we will take them off SkillRepo. Our Terms of Service describe how content removal works.
Frequently asked questions
I do not have a GitHub account.
Skills are attributed to a GitHub handle, so claiming works by signing in with the GitHub account those skills came from. Sign in with that account and the skills attributed to it become available to add. If the skills are not yours, there is nothing to claim.
My GitHub username changed or was recycled.
Handles can move between people over time, so if the sign-in does not line up with the skills you expect, email hello@skillrepo.dev and we will sort out which account the skills belong to.
My skills are under an organization name.
Claiming today covers personal GitHub accounts. Claiming skills attributed to an organization is planned for a later version. If you need organization skills handled sooner, email hello@skillrepo.dev.
Someone else's name is on my skills, or I think this is wrong.
Only the verified GitHub owner can add a skill to their account, because claiming requires signing in with the GitHub account itself. If something still looks wrong — the wrong handle is attributed, or you want the skill taken down — use the takedown path in the section above.
Next steps
Once your skills are in your account, the Publishing Guide covers editing them, cutting new versions, and controlling who can see them.