Skip to content
SkilVault
Sign inGet started
Features

Not just skills from the internet. Skills you can check.

Anyone can copy a skill file from a repo into their agent. SkilVault adds what that leaves out: a signature your machine verifies, a review before anything ships, and tools that keep a growing library usable.

The difference

Installing from a repo, or from SkilVault.

A skill is instructions your agent follows with your permissions. Where it came from matters more than how it is worded.

Copying a skill from the internet

  • Nothing proves the file is the one the author wrote.
  • A repo can change under you, and nothing tells your agent.
  • You read the whole file yourself, or trust it unread.
  • Every installed skill adds to what your agent loads up front.
  • Each CLI has its own folder, so you copy files around by hand.

Using SkilVault

  • Every version is signed, and your machine checks the signature.
  • Versions never change once published. Older ones are refused.
  • Automatic checks and an AI review come before a human signs.
  • Your agent sees a short entry per skill and loads the rest when it needs it.
  • One connection covers Claude Code, Codex, Grok and AGY.

Signed, and checked on your machine.

SkilVault signs every version offline. The signing key never sits on the server, so a hacked server cannot make your agent read something new.

  • Checked before use. The client verifies the signature before it reads, installs or updates a skill.
  • Refuses what does not match. Unsigned, unknown-key and older versions are all turned away.
  • Silent when fine, loud when not. You only hear about it when something is wrong.
terminal
$ skilvault read changelog-entry-on-completion
skilvault: refusing 'changelog-entry-on-completion' v1.0.1: it is not signed by a trusted key

Checked before a human signs it.

Skills are reviewed for quality and safety before publication.

  • Quality and safety. Each candidate is checked before it can join the catalog.
  • Reviewed before release. SkilVault checks the final files before approving a new version.
  • Signed publication. Approved versions are signed so your client can verify what it reads.
path of a new skill
  1. 1

    Skill prepared

    A new skill or an update is prepared for review.

  2. 2

    Reviewed

    Quality and safety checks before release.

  3. 3

    Signed and published

    Your client verifies the approved version before reading.

Versions that stay put.

A published version is never edited. A fix ships as a new, higher version, and an undo is an old version republished as a new one.

  • No silent swaps. The version you tested is the version you keep getting.
  • No going backwards. Once you have used a newer version, an older one is refused.
history of one skill
v1.0.0Published
v1.0.1Fix shipped as a new version
v1.0.2Earlier text republished as new
v1.0.0 after v1.0.2Refused by the client

A big library that stays out of the way.

Your agent gets a short entry for each skill you use. The full text is fetched, and verified, only when the agent actually needs it.

  • One connection, four CLIs. Claude Code, Codex, Grok and AGY each get their own folder, kept in sync for you.
  • Finding is local. Searching ranks the whole catalog on your machine. Only a query with no match goes to the server.

Free automatically loads your five chosen skills. Paid plans automatically load relevant skills across the library. Every plan can browse and explicitly read any published skill; Free can read 10 new skills a day beyond its five active ones.

works with
Claude CodeCodexGrokAntigravity
And more

Tools that grow with how you work.

Skill chains Team plan

Link 2 to 12 skills into an ordered chain and draw it in an editor. Your agent runs it as one skill, and each step is verified like any other read.

Skills that learn

Your notes stay in local files, apart from the signed pack, and secret-looking notes are refused. It is guidance for the agent, not enforcement.

Shared feedback

Off by default. Turn it on and only scrubbed rules are sent. When enough different accounts report the same thing, a draft update is prepared, and it still needs SkilVault's signature.

Ask for a skill

A search that finds nothing can become a request. It goes through the same checks and arrives as a draft, never straight into the catalog.

Two-step sign-in

Every account uses an authenticator app or a passkey, with recovery codes. Sensitive actions ask again. API keys are stored only as a hash.

Clear usage limits

Each plan states its keys, its skills and its hourly downloads. A limit gives you a 429 with a Retry-After, not a surprise.

Try it with the free plan.

Choose your skills, connect your machine once, and see the signature check for yourself.

Get startedBrowse the catalogSee pricing