openclaw-github-sync

What This Skill Does

The openclaw-github-sync skill provides a secure, version-controlled bridge between an OpenClaw agent's internal workspace and an external Git repository. By maintaining a mirror of non-sensitive context—such as markdown notes, selected memory segments, and custom skill configurations—this tool allows human operators to audit, refine, and update the agent's knowledge base remotely. The skill is designed with a 'security-first' architecture, utilizing an allowlist-based export manifest to ensure that sensitive environmental variables, API keys, and internal secrets remain strictly within the agent's local environment. It facilitates a professional DevOps workflow where the agent's progress can be tracked via Git history, enabling easier collaboration and long-term maintenance of the agent’s persona and utility.

Installation

To install this skill, run the command: clawhub install openclaw/skills/skills/bradvin/openclaw-github-sync. Post-installation, you must configure the environment by copying references/.env.example to references/.env and populating the SYNC_REMOTE variable with your private repository's SSH URL. Ensure that git, rsync, and python3 are installed and available in your environment path. Finally, define your exported files in references/export-manifest.txt to explicitly dictate which files are authorized for synchronization.

Use Cases

This skill is ideal for users who manage complex autonomous agents and require a secondary backup of the agent's reasoning process and task history. It is frequently used for teams deploying agents in production environments where auditing 'thought logs' or 'memory dumps' is a regulatory or organizational requirement. It is also highly effective for developers iterating on custom skill logic who want to push updates from a local IDE directly to the agent's workspace without manual file transfers.

Example Prompts

1. "Sync my current memory and updated skills to the remote repository and generate a summary of the changes."
2. "Please push the latest version of my configuration files to the backup Git repo, but make sure the export manifest is followed strictly."
3. "Check for manual updates in the remote sync repository and carefully apply them to my workspace, keeping the trust boundaries in mind."

Tips & Limitations

• Manual Pulls Only: Never automate the pull process. Always review incoming changes to prevent malicious code injection or unauthorized persona alterations.
• Sanitize Before Syncing: Use the memory/public/ directory for any content intended for the repo; avoid placing raw workspace files that might accidentally contain secrets.
• Version Control Strategy: Utilize the provided grouping mechanism to create logical commits, which makes tracking agent evolution much easier during manual review sessions. Remember that this tool is not a primary backup; maintain standard system backups alongside your Git-based sync.