Skip to content

Your own skills

Your skills, in every project, from one place

Upload the skills your team has written to SkillsVault, and use them in any project and any AI tool. When you change one, you change it once: every project gets the same version, with no copies to keep in step.

One source for your own skills: a version uploaded once is checked and reaches every project, in every AI tool.You, or your agentNothing to upload yetSKILLSVAULT · PRIVATEmy-skill1.2.0CurrentSeen by your organisation onlyWebsite · Claude Codemy-skill 1.2.0API · Codexmy-skill 1.2.0Mobile app · Cursormy-skill 1.2.0Data jobs · Gemini CLImy-skill 1.2.0

Four projects in four AI tools all use my-skill 1.2.0, from one place.

01/04

Upload once

Your skills go in one place

Every organisation on SkillsVault has a private publisher of its own. No application, and nothing to wait for.

  1. 01An owner or admin of your organisation creates an upload token under Organisation, then Private capabilities.
  2. 02With it, you upload each skill as a standard agent skill package (a folder with a SKILL.md), through the same publishing API every publisher uses. Your AI agent can do the upload for you.
  3. 03You group your skills into a capability, the same unit everything on SkillsVault is installed as.

Private

Only your organisation sees them

  1. 01Your capabilities are visible to the members of your organisation and nobody else. They never appear in the catalogue, in search, in the sitemap or to an AI agent browsing SkillsVault.
  2. 02They are never for sale. Your organisation is licensed for them automatically, free, with no end date, and nobody else can be.
  3. 03No person reviews them before you can use them: nobody but your organisation reads the listing.

Checked

Checked like everything else

  1. 01Every version you upload goes through the same automated checks as a capability on sale: that it is a valid package, that its bytes match their checksum, and that it carries nothing that looks like a live secret or an unsafe path.
  2. 02A version that fails is not published, and the one that works stays in use. You are told which check failed.
  3. 03Every version is signed, so the installer can prove the files in a project are the ones you uploaded.

Every project

Any project, any AI tool

Your skills install the same way as anything your organisation subscribes to, into Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and the other AI tools SkillsVault supports.

  1. 01In any project, one command installs everything your organisation holds: your own skills and the capabilities you subscribe to.
  2. 02Or connect your AI tool to the SkillsVault MCP server, and it loads your skills from SkillsVault when it needs them.
  3. 03A new project gets the same skills as the last one, from the same place.
npx -y https://skillsvault.dev/skillsvault-cli.tgz install
https://mcp.skillsvault.dev/mcp

Update once

Change it in one place, and every project follows

You choose how each capability is delivered, and that decides how an update reaches your projects.

  1. 01Hosted or hybrid: nothing is copied into the project except, for hybrid, a small pointer. Your AI tool loads the skill from SkillsVault each time it uses it, so every project uses the newest verified version from the moment it is published.
  2. 02Downloadable: the files are installed into the project. Running the install command again in a project brings it to the newest version.
  3. 03Either way there is one copy that matters, and it is the one in SkillsVault.

Start

Next to what you buy

Your own skills sit beside the capabilities your organisation subscribes to: the same install, the same checks, the same signed packages. How a license is held and checked is on How the license works, and what every version is checked for is on Trust.

Read the documentation

Keep your team's skills in one place

Create an account, and your organisation gets its own private space for the skills you write.