Vault sync use
Sync Vault Git repositories to local Markdown for Claude Code, Codex, OpenClaw, Cursor, and other file-aware AI agents.
npx -y skills add graphlit/vault-sync --skill vault-sync-useAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when the user wants an AI agent to answer questions or perform research from an already-synced Vault folder using local Markdown files and normal filesystem tools.
SKILL.md
1.4 KB, as published. Nobody here has run it
Vault Sync Use
Use an already-synced Vault as local, read-only context. Vault Sync provides files; the agent does the reading and reasoning.
Workflow
- If
vault-syncis available and the user has not asked to avoid updates, refresh the Vault:
vault-sync pull <path>
- Read
<path>/README.mdfirst to learn the Vault source and conventions. - Ignore hidden control folders:
.git,.zine,.dossium,.graphlit,.claude, and.codex. - Search and read Markdown directly with normal filesystem tools:
rg -n "<terms>" <path>
ls <path>
sed -n '1,160p' <file>
- Cite local file paths in responses when useful.
Boundaries
- Do not call app APIs for Vault consumption.
- Do not use
vault-syncfor search, query, read, summarize, rank, or index. - Do not edit generated Vault files unless the user explicitly asks for local modifications.
- If QMD is installed, it can be an optional local search helper. Add the Vault folder with
qmd collection add <path> --name <name> --mask "**/*.md", add context withqmd context add qmd://<name> "Local Vault synced by Vault Sync", then runqmd embed. Use QMD to find likely files and local file reads for the full source. Do not require QMD.