OpenClaw Daily Backup

This skill should be used when the user asks for daily backup, scheduled backup, restore, rollback, recovery, or routine protection of core OpenClaw workspac...

This skill largely does what it claims (local backup/restore of SOUL files), but the package includes actual backup data (backups/...) and many delivery docs. Before installing or running scripts: 1) Inspect the included backups (backups/ and openclaw.sanitized.json) for any sensitive data or secrets — do not assume redaction is perfect. 2) Review scripts/scripts/*.mjs for any network calls or unexpected behavior (e.g., remote upload, telemetry) before executing. 3) Run operations initially in a sandbox or non-production copy of your workspace and use --dry-run where supported. 4) Remove or archive the bundled backups if you don't need them, and set restrictive permissions on created backup directories. 5) If you plan to publish or share this skill, avoid committing real workspace backups into the repo and verify sanitization of any sample data.

Type: OpenClaw Skill Name: openclaw-daily-backup Version: 1.3.1 The skill bundle provides a comprehensive and well-documented backup and restore utility for OpenClaw workspace configuration files. The core logic in 'scripts/backup.mjs' and 'scripts/restore.mjs' uses standard Node.js built-in modules (fs, crypto, path) to manage file snapshots and verify integrity via SHA-256 hashes. Notably, the backup script implements a 'sanitizeObject' function that uses regex patterns to identify and redact sensitive information (e.g., tokens, API keys, secrets) from 'openclaw.json' before storage. There is no evidence of data exfiltration, obfuscation, or malicious instructions intended to subvert the agent.