One company registry for your team’s agent skills

Publish a SKILL.md bundle once. Teammates pull that exact revision with one command, pinned in vskill.lock.

Request Skills access Read the vskill docs

Assisted access. We confirm fit and setup before provisioning; an inquiry does not grant access.

From SKILL.md to every teammate

Draft: vskill push --draft uploads SKILL.md and assets for review. Plain push publishes where policy allows; vskill suggest proposes an update.
Review: Company policy decides who publishes.
Pull: vskill pull <slug>@<revision> writes .claude/skills/<slug>/ and pins vskill.lock.
Roll back: A rollback is a new, unverified revision. Teammates find its number with vskill status and pull it.

What a pull looks like

Synthetic example. Pulling needs an API key with read:skills.

Agents can also search and retrieve skills through vskill mcp. A pull puts files on disk once; nothing syncs automatically, and your agent still has to be set up to load them.

Full CLI and MCP reference

Already approved?

Continue Skills setup

Need evidence for a revision?

Assurance evaluates one revision when a release needs it. Results stay with that revision.

Explore Assurance

Questions before setup

What can I import?

A SKILL.md with assets, or a portable vskill JSON package. AGENTS.md, CLAUDE.md and prompts need converting to a SKILL.md first.

Who can see drafts?

Reviewers and collaborators with the right company role. Publishing publicly or exporting is always a separate step.

Do we need Challenges or Assurance?

No. Teammates can pull a pinned, published revision with no evaluation on record.

Looking for practical learning tracks?