workspace-backup-github

Backup AI Agent workspace to GitHub - One-click backup for OpenClaw, Claude Code, Cursor, and other AI Agent workspaces to a private GitHub repository. Suppo...

This skill appears to do what it says (push workspace files to a private GitHub repo) but you should be cautious before using it: - The skill asks for a GitHub personal access token (PAT) with broad 'repo' scope and embeds that token in the git remote URL (https://x-access-token:[email protected]/...). That token will be stored locally in the repo's .git/config and used each time the cron job runs — not in tracked files, but still present on disk and therefore at risk if the machine is compromised. Consider creating a narrowly scoped token or a separate machine account you can revoke easily. - The SKILL.md claims 'sensitive data are NOT backed up' but there is no secret-scanning or redaction step in the script. Inspect your workspace for credentials, environment files, or keys before backing up. Add explicit exclusions or run a secret-scan (e.g., git-secrets, truffleHog) before the first commit. - The script hard-codes WORKSPACE_DIR=/root/.openclaw/workspace. Verify this path is correct for your environment and that you understand which account will run the script (cron job). Running as root or with incorrect permissions may expose more data than intended. - Prefer safer authentication options if possible: use an SSH deploy key, a GitHub App with limited permissions, or a token with the minimum required scopes. Avoid pasting long-lived tokens into third-party services; rotate/revoke tokens immediately if you suspect misuse. - Test manually first: run the provided script locally with a throwaway repo or account, confirm it doesn't commit secrets, and verify where the token is stored. Only enable scheduled cron after confirming behavior. If you want, I can: (1) help produce a checklist to inspect your workspace for secrets before backup, (2) suggest a safer deployment pattern (deploy key or restricted token), or (3) produce a modified script that avoids embedding tokens in git remotes (e.g., using git credential helper or SSH keys).

Type: OpenClaw Skill Name: workspace-backup-github Version: 1.3.0 This skill facilitates backing up the AI workspace to GitHub but exhibits high-risk credential handling and data exposure. It prompts the user for a GitHub Personal Access Token (PAT) with full 'repo' permissions and stores it in plain text within the '.git/config' file by embedding it in the remote URL (scripts/backup.sh). Additionally, while the documentation claims to exclude sensitive info, the backup process includes the 'skills/' and 'memory/' directories, which are highly likely to contain secrets or personal data, increasing the risk of accidental data exfiltration.