openclaw-checkpoint
Backup and restore OpenClaw workspace state and agents across machines using git. Enables disaster recovery by syncing SOUL.md, MEMORY.md, memory files, cron jobs, agents (~/.openclaw/agents/), and configuration to a remote repository. Use when user wants to checkpoint their OpenClaw state, restore on a new machine, migrate between computers, or protect against data loss. Provides commands checkpoint (help overview), checkpoint-setup (interactive onboarding), checkpoint-backup, checkpoint-restore (with interactive checkpoint selection or --latest for most recent), checkpoint-schedule (auto-backup), checkpoint-stop, checkpoint-status, checkpoint-init, and checkpoint-reset. Supports multi-agent backup with flags --workspace-only, --agents-only, and --agent <name>. Automatically backs up cron jobs to memory/cron-jobs-backup.json on each checkpoint-backup.
[](https://agentverus.ai/skill/2cd9a4c8-9312-4827-8a0a-f5344ef72a65)Community Comments
Public comments are the active feedback surface on skill reports right now. Use them to share implementation notes, edge cases, and operator context.
Sign in to comment on this skill
No comments yet. Be the first to share your thoughts.
Keep this report moving through the activation path: rescan from the submit flow, capture real-world interactions, and wire the trust endpoint into your automation.
https://agentverus.ai/api/v1/skill/2cd9a4c8-9312-4827-8a0a-f5344ef72a65/trustUse your saved key to act on this report immediately instead of returning to onboarding.
Use these current-skill command blocks to keep this exact report moving through your workflow.
curl -X POST https://agentverus.ai/api/v1/interactions \
-H "Authorization: Bearer at_your_api_key" \
-H "Content-Type: application/json" \
-d '{"agentPlatform":"openclaw","skillId":"2cd9a4c8-9312-4827-8a0a-f5344ef72a65","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/2cd9a4c8-9312-4827-8a0a-f5344ef72a65/trustCategory Scores
Findings (17)
The skill does not include explicit safety boundaries defining what it should NOT do.
→ Add a 'Safety Boundaries' section listing what the skill must NOT do (e.g., no file deletion, no network access beyond needed APIs).
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
Piping a downloaded script directly to a shell interpreter. This executes remote code without verification — a classic supply chain attack vector.
→ Review the code block starting at line 47. Ensure this pattern is necessary and does not pose a security risk.
Found persistent session reuse pattern: "background daemon"
→ Call out when browser or auth state persists across commands. Reused authenticated sessions should require explicit user consent and clear cleanup guidance.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
Found credential access pattern: "cat > ~/.openclaw/workspace/.env"
→ Remove references to credentials and secrets. Skills should never access sensitive authentication data.
The skill relies on external documentation, specs, or README content as part of its workflow, which introduces an additional remote dependency and trust boundary.
→ Review which external services or providers the skill depends on, what data crosses that boundary, and whether the dependency is necessary for the intended workflow.
Found system modification pattern: "crontab -e"
→ Skills should not modify system configuration or install packages globally. Bundle required dependencies.
Found system modification pattern: "~/.zshrc"
→ Skills should not modify system configuration or install packages globally. Bundle required dependencies.
Found federated auth flow pattern: "OAuth" Related auth/profile context: - overlapping signals from the repeated finding family — Federated auth flow detected
→ Treat OAuth, 2FA, and token-refresh guidance as authentication-sensitive workflows. Explain scope, storage, and refresh behavior clearly so agents do not handle more credential material than necessary.
The skill references a raw content hosting service which is classified as medium risk.
→ Use official package registries instead of raw content URLs. Raw URLs can be changed without notice.
The skill references a well-known installer script in its setup instructions.
→ Consider documenting the exact version or hash of the installer for supply chain verification.
The skill contains a curl-pipe-to-shell pattern in its setup/prerequisites section.
→ Consider pinning the installer to a specific version or hash for supply chain verification.