FAQ

A reviewed library of skills for Claude Code. You choose skills, connect your machine once, and Claude reads them on demand. See How it works.

No. The free plan needs no payment details and never expires. See Plans & billing.

The client installs into Claude Code's skills folder (~/.claude/skills) and is built for Claude Code. The API is open, so you can build your own tooling on it (API reference).

Every plan can search and browse the whole catalog. On Pro and Unlimited you can read any published skill, pinned or not. On the free plan you can only read the skills you have pinned.

Any time. Remove one to free its pin and add another; the change shows on all your machines immediately. See Choosing your skills.

Search covers the whole catalog so you can discover skills. On the free plan, results marked [not selected] are not in your library yet — pin them in the dashboard to use them. On Pro and Unlimited you can read any of them straight away with skilvault read <name>, whether or not you pin them.

Skills read through the API are always the latest version. Copies kept on this machine refresh the first time you use SkilVault from a CLI each day. See Skills in your CLI.

Skills you have installed locally are ordinary files and work offline. Reading on demand needs a connection to check your manifest; only the pack download itself is cached.

Not through the website today — the catalog is curated by administrators. Your own personal skills in ~/.claude/skills keep working alongside SkilVault, and SkilVault never modifies them.

As many as your plan allows keys for — one key per machine is the tidy way. The free plan has 1 key. See API keys.

It would technically work, but a shared key shares one library and one set of limits, and revoking it cuts everyone off. Give each person their own account, and each machine or CI job its own key.

No — only a fingerprint is stored. Revoke it and create a new one. See API keys.

The client and the install command send it in an Authorization header, never in an address; do the same in your own scripts. Keys are revocable and scoped to your account, responses are never cached, and the reference server strips any ?k= an older client still sends from its logs. See Security & privacy.

You keep paid access until the end of the period you paid for, then move to the free plan. Skills already installed on your machine keep working; skills beyond the free pin limit are removed from your library, oldest first, and reading is limited to pinned skills again. See Plans & billing.

Not yet — billing is monthly only.

You keep paid access for a 7-day grace period so you can fix your payment method; after that you move to the free plan.

No. Skills run on your machine. SkilVault records which skills your key fetched and what you searched for, not your work. See Security & privacy.

Each is reviewed before it is published, and can be pulled later, but skills are provided as-is. You can read any skill first with skilvault read <name>, and Claude's own permission prompts still apply.

Ask the operator of your SkilVault deployment. Deletion revokes your keys immediately.

On the Legal page: terms of service and privacy policy.