← ClaudeAtlas

new-vaultlisted

Scaffold a new vault conforming to vault-os-v4. Invoked when user says "new vault", "create vault", "scaffold vault", or describes a project that needs a vault. Extracts context from chat, asks ≤3 questions, confirms, then writes all files.
thereisno-tomorrow/vault-os · ★ 3 · AI & Automation · score 74
Install: claude install-skill thereisno-tomorrow/vault-os
# new-vault Scaffold a complete vault conforming to **vault-os-v4** (`spec/vault-os-v4.md`). When invoked, execute phases 0–5 below. All file content is defined inline — no external files consulted at runtime. Everything needed is here. **v4 baseline (what changed from v2 — do not scaffold the v2 artifacts):** - **Slim compass** — three sections only (Focus / Questions / Flags) + an `*Updated:*` stamp. No Vault State, Key Files, or Hot Files tables. Continuity is computed by the orient hook, not curated here. - **Context-contract manifest** — `exports:` / `intake:` / `domains:`, not `export-surfaces:`. - **Native permissions** — protected files gated by `permissions.ask` in `.claude/settings.json`. No `protect.py`, no `protected-files.txt`. - **No `knowledge.md`** and **no `guide.md`** — both retired (D9). `/guide` renders CLAUDE.md's Commands table. - **Two v4 hooks** (`session-orient.sh` version 4.2.0, `session-capture.sh` version 4.2.0, both `--selftest`-able). - `validate-note.py` + `ops/validate-config.yaml` remain **Module A only**. --- ## Module Catalog The vault manifest (`ops/vault-manifest.md`) is always created — it is a baseline component, not a module. | ID | Name | Key additions | Requires | |---|---|---|---| | A | Knowledge Graph | `notes/` (flat), MOCs, `dedup-index.md`, `validate-note.py`, `ops/validate-config.yaml`, `/reduce` `/reflect` `/connect` `/think` | — | | B | Inbox Pipeline | `inbox/`, `archive/transcripts/`, `processing-backlog.md`, `reduce-s