← ClaudeAtlas

swarm-vaultlisted

The vault contract — how any agent reads, writes, and queries the SwarmVault. Use at the start of work in any vault-connected project, before exploring the repo, when deciding where to record memory/plans/decisions/sessions, when handing off between sessions or agents, or whenever unsure how the vault works.
AnmarHani/SwarmVault · ★ 4 · AI & Automation · score 77
Install: claude install-skill AnmarHani/SwarmVault
# swarm-vault — the vault contract The vault is the shared brain of every agent on this machine. Query it before exploring; write to it so parallel and future agents inherit what you learned. It is plain markdown — Obsidian is an optional viewer, never a dependency. The CLI is `swarmvault.py` — your platform's SwarmVault section (CLAUDE.md / AGENTS.md) records its full path; default install is `~/.swarmvault/scripts/swarmvault.py`. ## Reading (query first, explore second) ```bash swarmvault.py query --search "auth flow" # BM25, names + descriptions swarmvault.py query --project X --type memory # structured filters swarmvault.py show <note-name> # one body, once found swarmvault.py context . # the compact project brief ``` Descriptions are the payload — most questions are answered without opening a note. Open bodies (`show`) only for what you actually need. Reach for Glob/Grep on the repo only for what the vault cannot answer. If quality genuinely needs more context, take more — the budget curbs habit, not necessity. ## Writing (own files only) | What | Where | Lane | |---|---|---| | Memory (facts, footguns, decisions learned) | platform memory dir, or `<project>/.swarm/memory/` on Codex — sync mirrors both | machine | | Session journal (end of session) | `40 Sessions/<P>/YYYY-MM-DD <slug>.md` | machine | | Specs, plans, question queue | `30 Plans/<P>/` | human (specs) / machine (queue) | | Tickets + claims |