← Back to Skills Marketplace
Git-Crypt Backup
by
louzhixian
· GitHub ↗
· v1.0.0
3225
Downloads
2
Stars
12
Active Installs
1
Versions
Install in OpenClaw
/install git-crypt-backup
Description
Backup Clawdbot workspace and config to GitHub with git-crypt encryption. Use for daily automated backups or manual backup/restore operations.
README (SKILL.md)
Git-Crypt Backup
Automated backup of Clawdbot workspace (~/clawd) and config (~/.clawdbot) to GitHub with sensitive files encrypted via git-crypt.
Setup
1. Create GitHub repos (private recommended)
# Create two private repos on GitHub:
# - \x3Cusername>/clawdbot-workspace
# - \x3Cusername>/clawdbot-config
2. Initialize git-crypt
# Install git-crypt
brew install git-crypt # macOS
# apt install git-crypt # Linux
# Workspace repo
cd ~/clawd
git init
git-crypt init
git remote add origin [email protected]:\x3Cusername>/clawdbot-workspace.git
# Config repo
cd ~/.clawdbot
git init
git-crypt init
git remote add origin [email protected]:\x3Cusername>/clawdbot-config.git
3. Configure encryption
Workspace .gitattributes:
SOUL.md filter=git-crypt diff=git-crypt
USER.md filter=git-crypt diff=git-crypt
HEARTBEAT.md filter=git-crypt diff=git-crypt
MEMORY.md filter=git-crypt diff=git-crypt
memory/** filter=git-crypt diff=git-crypt
Config .gitattributes:
clawdbot.json filter=git-crypt diff=git-crypt
.env filter=git-crypt diff=git-crypt
credentials/** filter=git-crypt diff=git-crypt
telegram/** filter=git-crypt diff=git-crypt
identity/** filter=git-crypt diff=git-crypt
agents/**/sessions/** filter=git-crypt diff=git-crypt
nodes/** filter=git-crypt diff=git-crypt
Config .gitignore:
*.bak
*.bak.*
.DS_Store
logs/
media/
browser/
subagents/
memory/
update-check.json
*.lock
4. Export keys (important!)
mkdir -p ~/clawdbot-keys
cd ~/clawd && git-crypt export-key ~/clawdbot-keys/workspace.key
cd ~/.clawdbot && git-crypt export-key ~/clawdbot-keys/config.key
⚠️ Store these keys securely (1Password, iCloud Keychain, USB drive, etc.)
5. Initial commit & push
cd ~/clawd && git add -A && git commit -m "Initial backup" && git push -u origin main
cd ~/.clawdbot && git add -A && git commit -m "Initial backup" && git push -u origin main
Daily Backup
Run scripts/backup.sh:
~/clawd/skills/git-crypt-backup/scripts/backup.sh
Or set up a cron job for automatic daily backups.
Restore on New Machine
# 1. Clone repos
git clone [email protected]:\x3Cusername>/clawdbot-workspace.git ~/clawd
git clone [email protected]:\x3Cusername>/clawdbot-config.git ~/.clawdbot
# 2. Unlock with keys
cd ~/clawd && git-crypt unlock /path/to/workspace.key
cd ~/.clawdbot && git-crypt unlock /path/to/config.key
What Gets Encrypted
| Repo | Encrypted | Plain |
|---|---|---|
| workspace | SOUL/USER/HEARTBEAT/MEMORY.md, memory/** | AGENTS.md, IDENTITY.md, TOOLS.md, drafts/** |
| config | clawdbot.json, .env, credentials/, sessions/ | cron/jobs.json, settings/** |
Usage Guidance
This skill appears to do what it says: push the Clawdbot workspace and config to GitHub with git-crypt protecting selected files. Before installing or running it, consider the following:
- Pre-requisites: ensure git and git-crypt are installed, and that you have GitHub push access (SSH keys or other creds). The skill does not list these required binaries/credentials — set them up first.
- Review .gitattributes and .gitignore carefully: a misconfigured .gitattributes or an initial commit made before setting up encryption can leak secrets. Verify the repository locally (git status, git-crypt unlock/test) before pushing.
- Protect git-crypt keys: the instructions export keys to ~/clawdbot-keys; store these keys in a secure vault (hardware token, password manager) and do not leave them on disk in plaintext if you want confidentiality.
- First-run safety: on initial setup, inspect the working tree for accidental plaintext secrets and consider removing or encrypting them before the first push.
- Automation considerations: if you schedule the script (cron), ensure the scheduled environment has the same SSH keys and permissions, and that git-crypt keys are available in a secure manner.
If you want stronger assurance, ask the skill author to explicitly declare required binaries/credentials and to include checks in the script that verify git-crypt is initialized and that no unencrypted sensitive files are staged before pushing.
Capability Analysis
Type: OpenClaw Skill
Name: git-crypt-backup
Version: 1.0.0
The skill is designed for backing up Clawdbot workspace and configuration to GitHub using git-crypt encryption. All file system and network operations (git commands, package installation) are directly aligned with this stated purpose. Sensitive files are explicitly configured for encryption via `.gitattributes`, and the `SKILL.md` provides clear instructions for setup, daily backup, and restore, without any evidence of prompt injection attempts, unauthorized data exfiltration, or malicious execution. The `scripts/backup.sh` simply performs standard git add/commit/push operations on the specified local repositories.
Capability Assessment
Purpose & Capability
The name/description match the included SKILL.md and script: both perform git-based backups of ~/clawd and ~/.clawdbot and use git-crypt. Minor mismatch: the registry metadata lists no required binaries or credentials, but the instructions assume common tools (git, git-crypt, an SSH-capable git remote, and a package manager for installing git-crypt). This is an omission in the declared requirements but not evidence of malicious intent.
Instruction Scope
Runtime instructions operate only on the declared targets (workspace and config directories), the repo setup, and exporting git-crypt keys. They do not instruct reading or exfiltrating other system files or environment variables, nor do they phone home to unknown endpoints — pushes go to the user’s GitHub repo as configured.
Install Mechanism
This is an instruction-only skill with a small, local bash script. There is no install spec that downloads remote archives or executes arbitrary installers. The only install guidance is to use system package managers (brew/apt) to install git-crypt, which is a low-risk, expected instruction.
Credentials
No environment variables/credentials are declared, which is reasonable for a local backup script, but the instructions implicitly require Git access (SSH keys or other Git credentials) and a writable GitHub repo. The skill also instructs exporting git-crypt keys to ~/clawdbot-keys — storing these keys insecurely would expose backups. These implicit dependencies should be understood by the user before use.
Persistence & Privilege
The skill does not request elevated persistence (always:false) and does not modify other skills or global agent settings. The included script only runs when invoked or scheduled by the user (cron), so its privilege is limited to the invoking user's file permissions.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install git-crypt-backup - After installation, invoke the skill by name or use
/git-crypt-backup - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: automated backup for Clawdbot workspace and config with git-crypt encryption
Metadata
Frequently Asked Questions
What is Git-Crypt Backup?
Backup Clawdbot workspace and config to GitHub with git-crypt encryption. Use for daily automated backups or manual backup/restore operations. It is an AI Agent Skill for Claude Code / OpenClaw, with 3225 downloads so far.
How do I install Git-Crypt Backup?
Run "/install git-crypt-backup" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Git-Crypt Backup free?
Yes, Git-Crypt Backup is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Git-Crypt Backup support?
Git-Crypt Backup is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Git-Crypt Backup?
It is built and maintained by louzhixian (@louzhixian); the current version is v1.0.0.
More Skills