clawroam_skill

This skill provides seamless, encrypted cross-machine vault synchronization for knowledge, memory, and settings to keep your AI assistant in sync.
  • Python

2.6k

GitHub Stars

7

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill clawroam

  • _meta.json271 B
  • CLAUDE.md3.6 KB
  • clawroam.sh10.7 KB
  • migrate.sh8.7 KB
  • README.md7.2 KB
  • SKILL.md7.9 KB
  • track-packages.sh9.0 KB

Overview

This skill provides a portable identity vault for OpenClaw called ClawRoam. It continuously and invisibly syncs your agent's knowledge, packages, and memory across machines using end-to-end encryption. You can bring your own storage provider (Google Drive, Dropbox, S3, Git, FTP, WebDAV, local) or use the optional ClawRoam Cloud managed service. The design emphasizes automatic versioning, offline-first behavior, and explicit control over sensitive per-instance data.

How this skill works

ClawRoam watches and snapshots a structured vault, auto-committing changes and pushing them to the configured provider within seconds. Each installation generates an Ed25519 keypair; the private key never leaves the machine and commits are signed, while the public key is registered with the provider. Changes are versioned like Git so you can view history, diff pending changes, rollback, and selectively pull profiles from other machines.

When to use it

  • Keep agent memory, installed-skill manifests, and project context consistent across multiple machines.
  • Migrate an agent to a new machine or restore a previous profile state quickly and safely.
  • Maintain encrypted backups of long-term memory and package requirements with full history.
  • Share a vault using a secure storage provider without exposing machine-specific identities.
  • Use a simple managed option (ClawRoam Cloud) when you prefer not to manage storage.

Best practices

  • Enable auto-sync during initial setup for seamless background syncing, then check sync status occasionally.
  • Never auto-sync per-instance identity or personality files without explicit user consent.
  • Keep private keys on-device with strict filesystem permissions; only share public keys with providers.
  • Review package diffs before allowing automated installs; always confirm package changes.
  • Use named profiles per machine and explicitly pull another profile to import its data.

Example use cases

  • A developer works on multiple laptops and keeps project context and requirements.yaml synchronized across them.
  • Restore a previous agent state after testing risky changes by rolling back to a prior commit.
  • Teams or users who prefer Bring-Your-Own-Storage connect to Google Drive, S3, or a Git remote for encrypted backups.
  • Quickly migrate an agent to a new device using the interactive migrate.sh pull wizard.
  • Use ClawRoam Cloud for a turnkey, pay-as-you-go vault when you don’t want to configure storage.

FAQ

No. The Ed25519 private key stays on the machine in a locked directory; only the public key is registered with the provider.

What data is never auto-synced?

Per-instance files like an agent's personality or local identity are never auto-synced without explicit opt-in.

How does billing work for ClawRoam Cloud?

First 50 MB are free; beyond that it charges $0.005/MB/month with no bandwidth fees and no per-instance fees.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
clawroam skill by openclaw/skills | VeilStrat