Vault sync setup
Skill graphlit/vault-sync/plugins/vault-sync/skills/vault-sync-setup
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-setupAssembled 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 to install Vault Sync, connect an existing Vault Git repository to a local folder, refresh it, configure a recurring pull schedule, or make a local Vault available to an AI agent through filesystem files.
SKILL.md
2.0 KB, as published. Nobody here has run it
Vault Sync Setup
Vault Sync mirrors an existing Vault Git repository to local files. It does not create Vaults, manage replicas, call app APIs, search, query, summarize, rank, index, or push changes.
Workflow
- Confirm the environment is macOS, Linux, or WSL2. For Windows users, recommend WSL2 and keep the Vault under the WSL filesystem.
- Check for
bashandgit.rgis optional but useful for later consumption. - Install
vault-syncif it is not already onPATH. Prefer the bundled script:
bash skills/vault-sync-setup/scripts/install-vault-sync.sh
If the bundled script is unavailable, install from GitHub:
mkdir -p ~/.local/bin
curl -fsSL https://raw.githubusercontent.com/graphlit/vault-sync/main/bin/vault-sync -o ~/.local/bin/vault-sync
chmod +x ~/.local/bin/vault-sync
- Ask for the Vault Git repository URL and preferred local folder if missing. Use
~/vaults/<repo-name>as the default. - Do not infer the local Vault path from the current working directory, app name, or repository owner. Do not invent hidden app folders such as
~/.zine/vault,~/.dossium/vault, or~/.graphlit/vault. - Initialize and verify:
vault-sync init <vault-repo-url> <path>
vault-sync pull <path>
vault-sync doctor <path>
- Ask before installing a recurring schedule. If approved:
vault-sync schedule install <path> --every 5m
Agent Behavior
- Treat the Vault as generated, read-only context.
- Do not edit Vault files unless the user explicitly asks to modify local copies.
- Do not use
vault-syncas a search or read API. After setup, use normal filesystem tools. - If Git authentication fails, let the user complete their normal Git or GitHub CLI authentication flow.