Documentation

Everything you need to know about using ClaudeVault.

Quick Start

Get up and running in under 2 minutes.

•Create a free account at claudevault.dev
•Generate an API key in your Vault under API Key
•Run: npx claudevault — the guided setup walks you through auth and your first install
•On install, pick a scope: project-local (<cwd>/.claude/) or global (~/.claude/)

Device Management

Each API key supports up to 3 devices.

CLI Commands

Everything you can do with the ClaudeVault CLI.

•npx claudevault — Guided first-run setup (or shows help if already authenticated)
•npx claudevault auth <key> — Authenticate and register this device
•npx claudevault list [--local] — List owned assets and install status across both scopes (--local = offline)
•npx claudevault install <slug> [--project|--global] [--skip-preset] — Install a skill, preset, or entire bundle
•npx claudevault update — Check both scopes and apply updates to installed assets
•npx claudevault view <slug> — Print a prompt or skill to stdout
•npx claudevault uninstall <slug> [--project|--global] [--restore-backup|--skip-restore] — Remove an installed asset
•npx claudevault deauth — Deactivate this device and remove your API key

Install Scopes

Choose where skills land: one project, or every project.

•Project scope (--project): installs to <cwd>/.claude/skills/claudevault/ — only available inside that project
•Global scope (--global): installs to ~/.claude/skills/claudevault/ — available in every Claude Code session
•With no flag, the CLI prompts you interactively (and defaults to project if it detects a project directory)
•For CI or scripts: set CLAUDEVAULT_SCOPE=project|global to skip the prompt
•Project installs auto-append .claude/skills/claudevault/ and .claude/claudevault.json to your .gitignore so paid content is never committed
•Presets are always project-scoped — they're a project's CLAUDE.md, not a global config. Any existing CLAUDE.md is backed up to CLAUDE.md.backup first