Pinned revisions
Pull a specific revision. Use vskill status to check for updates and local edits.
Know which skill revision every repository runs.
Publish a skill once to your company registry. Reviewers approve changes, and each repository pulls an exact revision recorded in vskill.lock.
Built for
Engineering teams sharing agent skills across repositories
What you get
A company skill registry with roles, review and pinned versions
Get started
Guided setup
We set up your registry with you and agree pricing up front.
Why it matters
Copied skills drift apart.
Paste a skill into five repositories and you have five skills. Nobody can say which revision an agent ran.
Without a registry
- A copy of every skill in every repository, edited in place
- No record of which revision a repository uses
- Changes copied between repositories without review
With Versalist Skills
- Published revisions available to pull into repositories
- A lockfile that records exactly which revision each repository pulled
- Company policy that decides who publishes and when review is required
How it works
Publish and share a skill.
Draft
Upload a new skill with its scripts and references, or propose a change to one your team already uses.
Review
Your company policy decides who publishes. Where review is required, a reviewer approves the revision first.
Pull
Teammates pull the exact revision with one command, pinned in vskill.lock next to your code.
Roll back
Owners and admins roll back with a recorded reason, publishing a new revision your team can pull.
Features
Manage shared skills.
Roles and review
Viewers, contributors, reviewers and admins, with approval rules and tool policy set for your company.
Managed updates
Updates stop if a managed file was edited locally.
Agent access over MCP
Agents can search your reviewed skills and fetch one directly through the MCP server built into vskill.
Integrations
Built for the skills format your agents already use.
- Agents
- Claude Code
- MCP-compatible agents
- Formats
- SKILL.md with scripts, references and assets
- Portable vskill package
- Interfaces
- Web app
- vskill CLI
- MCP server
- API
Resources
Explore the registry.
One published revision, pulled into three repositories and pinned in each.
Public skill directory
Browse published public skills you can inspect, copy or install into your workspace.
Browse public skillsCLI and MCP reference
The core vskill commands, every MCP tool and the registry API.
Read the referenceSkill learning tracks
Practical tracks for teams writing and reviewing their first skills.
Open the learning tracks
Security
Access follows your company roles.
Every skill and draft is scoped to your company, and every API key acts only as the teammate who created it.
Scoped API keys
Separate read and write scopes, on keys that belong to one user and can be revoked at any time.
Members only
The registry, CLI and API serve only signed-in members of your company.
Private drafts
Drafts are visible only to their owner, your reviewers and admins, and invited collaborators.
Content checks
Binaries and symlinks are rejected, and imported packages that contain secrets are blocked.
Pricing
Get started with Skills.
Priced when we set up your registry.
We set up your registry with you, including roles and review policy, and agree pricing before you start.
FAQ
Frequently asked questions
How do we get started?
Request access and we’ll confirm fit, then set up your company registry with you, including roles and review policy.
Do we need Continuous Evals or Challenges too?
No. Skills works on its own. Add Continuous Evals when you want to compare two revisions of a skill before it ships.
Which agents can use a pulled skill?
vskill pull writes the Claude Code skills layout. Other agents can search and fetch skills through the MCP server built into vskill.
Do pulled skills update automatically?
No. Teammates pull a new revision when they’re ready, so nothing changes underneath a running agent.
What can we import?
A SKILL.md with its scripts, references and assets, or a portable vskill JSON package.