OpenClaw Git Backup

Create, update, validate, or troubleshoot automated git backup workflows for OpenClaw repositories. Use when a user wants a scheduled commit-and-push backup...

This skill appears coherent and reasonably safe for its purpose, but review and test before deploying: 1) Confirm the target remote and branch (the script will fall back to 'main' if detached — verify this to avoid pushing to the wrong branch). 2) Prefer scoped deploy keys or the host credential manager over storing long-lived personal tokens; if you must use an HTTPS token, follow the guidance to store it in a repo-local credential file and restrict token scope, and ensure file permissions are correct. 3) Add BACKUP_EXCLUDES to prevent scheduler self-noise or sensitive runtime files being committed. 4) Run the bundled script manually and force-run the cron job once as recommended to validate commits and pushes. 5) Be aware the script runs with the cron user's filesystem permissions — do not use it to back up repositories that contain secrets you do not want accessible to that user. If you want stronger guarantees, consider using an SSH deploy key or a CI-backed backup with separated credentials.

Type: OpenClaw Skill Name: openclaw-git-backup Version: 0.1.0 The skill provides a legitimate utility for automating git backups within OpenClaw repositories. The core logic in `scripts/nightly_git_backup.sh` performs standard git operations (add, commit, push) with configurable excludes and detailed commit messages, while the documentation in `SKILL.md` and `references/` correctly guides the agent on setup and credential management, including explicit warnings against insecure practices like embedding tokens in URLs.