vault-sync

Sync an OpenClaw workspace to a private Git repository with deterministic commits.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/bolander72/bstack --skill vault-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-sync
Source: https://github.com/bolander72/bstack/tree/main/skills/vault-sync
Command: npx skills add https://github.com/bolander72/bstack --skill vault-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically back up your OpenClaw workspace by syncing it to a private Git repository to provide a versioned history of memory, notes, configs, and skills.

Core Features & Use Cases

  • Automatic commit and push of workspace changes to a private Git repository
  • Guidance for setting up a cron-based recurring backup
  • Safe conflict handling and incremental backups for ongoing agent activity

Quick Start

Initialize a Git repo in your workspace and configure a private remote to start backing up your workspace automatically.

Frequently Asked Questions about vault-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I back up my OpenClaw workspace to a Git repository?

Sync an OpenClaw workspace to a private Git repository by initializing a local repo, configuring a remote, and setting up authentication. The Skill applies deterministic commits and pushes workspace memories, notes, and configurations to create versioned backups.

Can I schedule automatic workspace backups to GitHub using cron?

Yes, you can schedule automatic workspace backups to GitHub using a cron-based schedule. The Skill guides you through configuring recurring pushes to automatically sync your workspace memories and configurations to your private Git remote.

What do I need to set up before syncing my workspace to Git?

Before syncing your workspace to Git, you need a private Git repository, a configured remote, and proper authentication credentials. You also need to configure a .gitignore file to manage which workspace files are excluded from versioned backups.

How does versioned backup handle conflicts during ongoing agent activity?

Versioned backups handle conflicts during ongoing agent activity through safe conflict handling and incremental backups. This ensures that continuous workspace changes are synced to Git without overwriting uncommitted local modifications or breaking ongoing processes.

Is it safe to use Git versioning for backing up workspace memories and configs?

Yes, using Git versioning for workspace backups is safe when configured with a private repository and proper authentication. A .gitignore file ensures sensitive or unnecessary files are excluded, while incremental commits provide a secure, restorable history.