Avenger initiative
π‘οΈ Encrypted GitHub backup & restore for any OpenClaw system. Branch-per-night strategy with smart retention.
npx -y skills add ProSkillsMD/avenger-initiativeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Encrypted GitHub backup and restore for any OpenClaw agent system. Creates branch-per-night backups with smart retention (7 daily, 8 weekly, 12 monthly branches). Backs up openclaw.json (AES-256 encrypted), agent memories, SOUL/IDENTITY files, cron jobs, and custom skills to a private GitHub vault. Each backup auto-generates a human-friendly README.md inside the vault with purpose, full contents table, branch structure, step-by-step restore instructions, and Avenger agent commands. Triggers on phrases like "avenger backup", "backup system", "push to vault", "sync vault", "avenger restore", "restore from vault", "setup avenger", "avenger status", "avenger init", "configure backup", "set up backup". Also auto-runs after any critical config change.
The file declares its own license as MIT. That is the authorβs claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
4.5 KB, as published. Nobody here has run it
π‘οΈ Avenger Initiative
Encrypted, branch-based GitHub backup and restore for any OpenClaw system.
When This Skill Triggers
- User says "setup avenger" / "configure backup" / "avenger init" β Run SETUP flow
- User says "avenger backup" / "backup system" / "push to vault" β Run BACKUP
- User says "restore from vault" / "avenger restore" β Run RESTORE flow
- User says "avenger status" / "vault status" β Show STATUS
- After any confirmed config change (gateway restart, config patch) β Run BACKUP silently
SETUP FLOW (Agent-Guided)
When setup is triggered, walk the user through it conversationally. Ask one question at a time.
Step 1 β Ask for the vault repo
"To set up Avenger Initiative, I need a private GitHub repo to use as your vault. Have you created one already? If so, share the URL (e.g.
https://github.com/yourname/my-vault). If not, I can help you create one."
Step 2 β Handle the encryption key
"Your
openclaw.json(which contains all API keys and bot tokens) will be encrypted with AES-256 before being pushed. Do you have an existing encryption key from a previous Avenger setup, or should I generate a new one?"
Step 3 β Run setup
bash ~/.openclaw/workspace/skills/avenger-initiative/scripts/setup.sh \
--repo <vault-url>
Step 4 β Show key and insist they save it
"β οΈ Your encryption key is below β save it NOW in 1Password, Bitwarden, or a secure note. Without this key, your backup cannot be decrypted."
Wait for user to confirm "saved" before proceeding.
Step 5 β Explain what will be backed up
- π
openclaw.jsonβ encrypted (all API keys, bot tokens, agent configs) - π§ All memory logs and workspace files (SOUL, IDENTITY, MEMORY, TOOLS)
- π₯ Per-agent files for all agents
- π§ All custom skills
- π Cron job definitions
Retention policy:
- Daily β 7 days
- Weekly β 8 weeks (created every Sunday)
- Monthly β 12 months (created 1st of each month)
Step 6 β Run first backup & install cron
bash ~/.openclaw/workspace/skills/avenger-initiative/scripts/backup.sh
BACKUP
bash ~/.openclaw/workspace/skills/avenger-initiative/scripts/backup.sh
Creates backup/daily/YYYY-MM-DD branch β merges to main β prunes per retention policy.
On Sundays: also creates backup/weekly/YYYY-WNN.
On 1st of month: also creates backup/monthly/YYYY-MM.
RESTORE
bash ~/.openclaw/workspace/skills/avenger-initiative/scripts/restore.sh
Supports --branch backup/daily/YYYY-MM-DD to restore from a specific snapshot.
Shows vault manifest, asks for confirmation, decrypts and restores all files.
After restore: openclaw gateway restart
STATUS
Check ~/.openclaw/workspace/memory/avenger-backup.log for last backup. Show timestamp, branch, and vault URL.
File Locations
~/.openclaw/
βββ credentials/
β βββ avenger.key β Encryption key (NEVER commit)
β βββ avenger-config.json β Vault repo URL
βββ workspace/skills/avenger-initiative/
βββ SKILL.md
βββ scripts/
β βββ backup.sh
β βββ restore.sh
β βββ setup.sh
βββ references/
βββ security.md
Security Model
- Vault repo should be private on GitHub
openclaw.jsonβ AES-256-CBC encrypted (PBKDF2, 100k iterations)- All other files β plaintext (no secrets)
- Key lives only on the machine and in the user's password manager
See references/security.md for threat model and key rotation.
More verified OpenClaw skills available at proskills.md