Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Version 2.0.2 of claw-sync introduces a major refactor and restructuring: - Migrated all source code and scripts into a dedicated claw-sync/ subdirectory. - Added example configuration and documentation files: README.md, SKILL.md, .gitignore, and config.example.env. - Introduced modular scripts for pull, push, cron setup, and status operations. - Updated command structure for improved usability and clarity. - Removed the old root-level .gitignore file.
What This Skill Does
Syncs OpenClaw memory files and custom skills to a remote Git repository. Each sync creates a versioned backup that can be restored by name or as the latest version. Sensitive files like API keys and .env are excluded automatically.
Unlike manual file copies or generic backup tools, it handles OpenClaw-specific files automatically while excluding secrets from the repository.
When to use it
- Backing up agent memory before a major project change
- Restoring a previous workspace state after accidental file loss
- Syncing custom skills across multiple machines
- Previewing what would be pushed before committing a sync
- Listing all backup versions to find a specific restore point
Example Workflow
Here's how your AI assistant might use this skill in practice.
User runs: /sync
- 1Reads memory and skill files from the OpenClaw workspace
- 2Excludes files containing secrets (openclaw.json, .env)
- 3Pushes eligible files to the configured GitHub repository
- 4Tags the push with a versioned timestamp for future restore
Files pushed to remote repo with a new versioned backup created
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.