Git is where your skills live. SkillRepo is how your whole team stays on the current, approved set, in every agent.
Team is $8/seat per month, 14-day trial, no card. Working solo? Developer is $5/month — start on your own, then bring your team onto one library.
A different job from version control.
If your agent skills live in a git repo today, you already have them in one place. The friction shows up next: getting the current version into the path each agent actually reads, keeping it current without a manual pull, and — once more than one person is involved — knowing which version each repo is running and being able to pull a bad one back.
Those are distribution and governance jobs, and they’re the ones SkillRepo does.
The same jobs, done two ways.
| What you need | With git | With SkillRepo |
|---|---|---|
| Put a skill in one place | Commit or copy the files | skillrepo init writes them for you |
| Land it where each agent reads | Copy or script it per tool, per machine | Written to each dev environment’s native path |
| Stay current | Remember to pull | Refreshes at the start of a session, or on skillrepo update |
| Run the same approved version across your repos | Submodules, tags, and discipline | Approved-version pins, scoped per repo |
| Pull a bad version back | Revert, then everyone re-pulls | Recall, with a fallback to the last approved version |
| See where a repo has drifted | Diff the files by hand | Drift visible across your repos |
| Judge a third-party skill before you run it | Read it yourself | A two-layer A–F safety grade as a signal |
| Know who really wrote it | A self-reported commit author | Provenance and a verified GitHub identity |
| Keep your own skills private | A private repo | Private by default |
One library, every agent, always current.
With git, the skill files sit wherever you committed them. To get them where an agent looks — Claude Code reads .claude/skills/, most other tools read .agents/skills/ — you copy, symlink, or script it for each tool, and you repeat that on every machine. To stay current, someone has to remember to pull.
SkillRepo turns that into one step. skillrepo init writes the current files to the native path of each dev environment you use — seven are supported today: Claude Code, Cursor, Windsurf, VS Code + Copilot, Gemini CLI, Codex CLI, and Cline. In most of them the library refreshes at the start of a session; anywhere else, a single skillrepo update brings it current. One library, every agent, no manual pull.
The approved version, in plain sight.
Git keeps history, but it has no notion of which version a given repo is meant to run. You approximate that with branches, tags, submodules, and review discipline — by hand, and it drifts.
SkillRepo makes the approved version explicit:
- Approved-version pins — pin the version each repo runs, scoped per repo, so every repo gets the skills it needs at the versions you approved.
- Recall with fallback — when a version turns out to be wrong, recall it, and each repo falls back to the last approved version on its next sync.
- Drift you can see — spot which repos and agents have moved off the version you approved, instead of finding out later.
This is the Team layer, at $8/seat per month. It’s what turns “everyone has a copy” into “everyone runs the copy you approved,” across your organization’s repos.
Know what you’re pulling before you run it.
A folder in git tells you what changed. It doesn’t tell you whether a skill you pulled from someone else is safe, or who actually wrote it — and a lot of what’s out there isn’t safe: 36.8% of public skills contain a security flaw (Snyk, Feb 2026).
Every skill on SkillRepo carries a two-layer A–F safety grade. Treat it as a signal to help you decide, not a certification — review a skill before you run it. You also get provenance and a verified GitHub identity on what you pull, so a skill is attributed to a real author. And your own skills are private by default; you choose what to share.
Grades are signals, not a certification. They tell you where to look; they don’t replace reading a skill before you run it.
You don’t have to choose.
SkillRepo doesn’t replace git, and it doesn’t ask you to move your skills out of it. Your code and your source files stay in version control, where they belong.
SkillRepo writes the current skill files to disk and gitignores them, so they don’t clutter your repo or collide with your commits. Your source stays in version control; SkillRepo gets the current, approved skills into every agent your team runs.
Questions people ask.
- Can't I just keep my agent skills in a git repo?
- You can, and many people do. What that setup doesn't do is put the current version in the path each agent reads, keep it current without a manual pull, or tell you which version a repo is running. SkillRepo adds that layer on top of the files.
- Does SkillRepo replace git?
- No. Your code stays in git. SkillRepo writes the current skill files to disk and gitignores them, so they don't clutter your repo. The two work together.
- How does SkillRepo keep skills current?
- skillrepo init writes the current files to each supported dev environment's native path. In most environments the library refreshes at the start of a session; anywhere else, skillrepo update brings it current.
- Which dev environments are supported?
- Seven today: Claude Code, Cursor, Windsurf, VS Code + Copilot, Gemini CLI, Codex CLI, and Cline. Skills land in each one's native path.
- What do the safety grades mean?
- Every skill carries a two-layer A–F grade. It's a signal to help you decide, not a certification — review a skill before you run it.
- Are my own skills public?
- No. What you publish is private by default; you choose what to share.
- What does it cost?
- Developer is $5 per month — install and sync your library across every dev environment, with a 5-day trial and no card. Team is $8/seat per month and adds approved-version pins, recall, and drift across your organization's repos, with a 14-day trial and no card.
Get your whole team on one library, kept current.
Team is $8/seat per month: one library delivered to every member and repo, kept current, with approved-version pins, recall, and drift you can see. The trial runs 14 days and needs no card.
Just starting on your own? Developer is $5 per month — set up your environment and keep your own library current, then bring your team onto the same one. 5-day trial, no card.