git-crypt-backup

What This Skill Does

The git-crypt-backup skill provides an automated, secure mechanism for backing up your Clawdbot workspace and configuration to GitHub. By utilizing git-crypt, it ensures that sensitive data—such as your identity, internal memories, API credentials, and agent sessions—remains encrypted at rest on remote servers. This skill allows you to maintain a version-controlled, encrypted history of your agent’s progress while keeping proprietary data safe from unauthorized access.

Installation

To install this skill, run: clawhub install openclaw/skills/skills/louzhixian/git-crypt-backup. After installation, you must initialize the local repositories, define your .gitattributes to specify which files require encryption, and generate export keys. These keys act as the master password for your data and must be stored in a secure, offline location or encrypted vault. Without these keys, data pushed to your private GitHub repository will be unreadable to everyone, including you.

Use Cases

This skill is designed for power users who want to synchronize their agent's 'brain' across multiple devices. It is perfect for developers moving between a local workstation and a cloud server, or for those who require a disaster recovery plan for their Clawdbot installation. It is also an essential tool for maintaining a long-term audit trail of agent sessions and memory updates without sacrificing privacy.

Example Prompts

1. "Perform a manual backup of my current workspace and configuration using the git-crypt-backup script."
2. "How do I rotate my git-crypt keys for the clawdbot-workspace repository?"
3. "Can you help me check if the latest session logs have been encrypted and pushed to the repository?"

Tips & Limitations

• Security First: Never lose your master keys. If you lose the keys stored in ~/clawdbot-keys, your remote backup will become permanently inaccessible.
• Automation: You are encouraged to set up a daily cron job to run the backup script, ensuring your memory and session files are never more than 24 hours out of sync.
• Performance: While git-crypt handles encryption seamlessly, extremely large memory directories may impact git commit performance; consider using .gitignore for transient cache files.