One library your whole team can't drift from.
Teams from $8/seat/month. No seat minimum. 14-day trial, no card.
Right now, every engineer is running their own setup.
Three people on your team used roughly the same agent 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 copy whatever they're handed.
The skills are fine. There's just no shared place they live.
Drift isn't a one-time mistake. It's the default.
Every agent works from a slightly different copy of “how we do things,” so the output diverges. Your codebase starts to read like it was written by five different teams — because, through five different agents, it was.
Curate one library every agent pulls from.
A team library on SkillRepo is the one approved set of agent skills for your whole team. You decide what goes in it; every engineer's agent pulls from the same place. Add skills from the public catalog, publish your own private ones, or mix both in a single library — vetted best-practice skills alongside the internal ones that encode how your team actually works.
Curating is a deliberate act, not a free-for-all. Adding, removing, and approving skills runs through the people you've given that permission — so the library reflects a decision about what your team standardizes on, not whoever happened to push last.
A library your team can't drift from.
Curation only matters if it sticks. On most dev environments, a session-start hook keeps every machine on the published version automatically — each new session picks up the current skills and overwrites local copies. Nothing to run, no version to remember; the library just stays current.
If someone has hand-edited a synced skill, skillrepo list flags it as drift before the next refresh — visible, not silent — and refreshing restores the published version. The library stays the single source of truth, and the source of truth stays singular.
Graded, so you're not curating blind.
Curating a library means vouching for what's in it. 36.8% of public skills contain a security flaw (Snyk, Feb 2026) — you don't want to approve those by accident.
Every skill on SkillRepo gets a two-layer analysis on publish — static checks plus an AI pass across safety, quality, clarity, and completeness — and ships with an A–F grade and the findings behind it. You curate with the score in view instead of guessing.
Grades are signals, not a certification. They tell you where to look; they don't replace reading a skill before you run it.
An audit log, because someone will ask.
When someone asks what your agents were allowed to run — a security review, a customer's vendor questionnaire, an incident — “we think it was current” isn't an answer. SkillRepo records the changes that shape the library to an account audit log: skills added and removed, publishes and visibility changes, member and role changes, GitHub integration syncs, and API key creation and revocation — each with who did it and when.
It's the paper trail for what your team standardized on and when it changed — so curation and compliance are the same motion, not two separate projects.
What every seat gets.
A seat isn't access to a list of links. It's the same curated library, delivered as real files into the tools your developers already use.
Into every dev environment
The library syncs as native skill files into Claude Code, Cursor, Windsurf, VS Code + Copilot, Gemini CLI, Codex CLI, and Cline — landing where each tool already looks for them. No per-editor wiring.
Current without the reminders
On most dev environments a session-start hook refreshes the library automatically every session — nothing to run, nothing to remember. The handful without a hook stay current with an occasional skillrepo update.
One source, every agent
Curate once and every engineer's agent runs the same vetted skills — whichever tool they prefer. The library is the standard; the editor is just where it shows up.
Questions teams ask.
- How do you prevent skill drift across a team?
- Every developer's agent pulls from one curated library. On most dev environments a session-start hook keeps it current automatically — each session syncs the published version and overwrites local copies, with nothing to run; the handful without a hook stay current with an occasional skillrepo update. skillrepo list flags any skill edited locally, so the whole team stays on the same version instead of drifting into private forks.
- Is the grade a certification?
- No. Grades are signals — a two-layer analysis (static checks plus an AI pass) scored A–F with the findings attached. They tell you where to look. Always review a skill yourself before your team runs it.
- Which dev environments are supported?
- Claude Code, Cursor, Windsurf, VS Code + Copilot, Gemini CLI, Codex CLI, and Cline. The library syncs as native skill files into each one — no per-editor setup.
Give every agent the same approved library.
Curate once, and your whole team's agents run the same vetted, graded, audited skills — no drift, across every dev environment.
Teams from $8/seat/month. No seat minimum. 14-day trial, no card.