Run one skill across two agents.
By the end of this page you'll have a local vault, a validated skill, and the same skill running from both Claude Code and Codex with zero forks.
Step 1 — Install the local vault
The installer builds the Node app under ~/.autovault/app, preserves vault storage in ~/.autovault, and writes the CLI shim to ~/.autovault/bin/autovault.
$ curl -fsSL https://autovault.sh | sh # macOS: also available via brew$ brew install autoworks-ai/tap/autovault
autovault.sh serves the audited script from the AutoVault source repository; you can read it before piping it.Step 2 — Add your first skill
Skills enter the vault through a source adapter. Whatever the source, the gate runs the same five checks before admission.
$ autovault add github:autoworks-ai/skills/extract-pdf
Step 3 — Scope it to your context
By default a freshly-added skill is unscoped — admitted to the vault, but not visible to any caller. Scope it explicitly to the agents and projects that should see it.
$ autovault scope extract-pdf \ --agent claude-code,codex \ --project autovault-website \ --device $(hostname)
Step 4 — Run it from your agent
The skill is now installed, validated, scoped, and rendered for each target agent. The same skill name works in all of them, while tool calls are transformed to each agent's vocabulary.
> use extract-pdf to summarize report.pdf ✓ tool resolved: chrome-devtools, read# extracting... "This 24-page report covers Q1 platform metrics, with three..."
Where to next
You've completed the install + add + scope + run loop. From here, most people branch into one of four places: