Personality Backup
PendingStatic analysis audit pending.
Overview
No static analysis result has been recorded yet. Pattern checks will appear here once the artifact has been analyzed.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A backup could contain all OpenClaw secrets and account credentials, not just personality files.
The script copies every non-hidden file from the configured secrets directory into the backup by default. That may include API keys, tokens, or other account credentials.
if [ "$CFG_BACKUP_SECRETS" = "true" ] && [ -d "$CFG_SECRETS_DIR" ]; then ... cp -r "$CFG_SECRETS_DIR"/* "$BACKUP_DIR/secrets/"
Use an explicit allowlist for secrets, disable secret backup unless necessary, and verify the archive recipient and encryption password before running.
Users may believe every backup is safely encrypted, but a misconfigured password file could lead to a failed, hanging, or weakly protected backup workflow.
If the password file is missing or the expected field is not found, the password remains empty and is still exported for the backup script instead of failing closed.
password = ""
if pw_file and os.path.isfile(pw_file):
with open(pw_file) as f:
...
pairs = {
"CFG_PASSWORD": password,Fail immediately when the password is missing or empty, and do not deliver any archive unless encryption has been verified.
Sensitive backups may continue running and emailing after setup, and existing scheduled jobs could be lost if the command is copied directly.
The documented setup creates a recurring cron job for automated backups, and the command form can replace the user's existing crontab rather than safely appending.
echo "0 3 * * * bash $(pwd)/scripts/backup.sh /path/to/backup-config.json" | crontab -
Require explicit user approval for scheduled backups, document how to remove the cron job, and use a safer append flow such as preserving `crontab -l` output.
Private or stale memory contents, including any bad instructions already stored there, could be restored into a new agent environment.
Backing up and restoring memory is central to the skill, but it means persistent agent memory and identity context are carried forward across installations.
"backup_memory": true, ... The backup includes a generated `RESTORE.md` with step-by-step instructions for restoring onto a fresh OpenClaw installation.
Inspect memory and personality files before restore, and keep encrypted archives tightly controlled.
Dependency and credential requirements may not be visible during installation or preflight checks.
The registry metadata does not declare dependencies or credentials even though SKILL.md lists p7zip/Python and the scripts can use SMTP credentials.
Required binaries (all must exist): none Env var declarations: none Primary credential: none
Declare required binaries such as 7z, python3, and rsync, and declare optional SMTP credential environment variables.