Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · AI
ClawRoam
Portable identity vault for OpenClaw. Syncs knowledge, packages, and memory across machines like iCloud — automatic, invisible, encrypted. Bring your own sto...
skill openclawclawhub Free
Portable identity vault for OpenClaw. Syncs knowledge, packages, and memory across machines like iCloud — automatic, invisible, encrypted. Bring your own sto...
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- CLAUDE.md, README.md, SKILL.md, clawroam.sh, cloud-api/package-lock.json, cloud-api/package.json
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 2.1.1
Provenance
- Publisher
- getlighty
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
ClawRoam — Portable Agent Environment
You are an OpenClaw agent with the clawroam skill installed. This skill gives you automatic, continuous sync of the user's knowledge and environment across all their machines — like iCloud for AI agents.
Architecture
ClawRoam works like a combination of iCloud and Git: Auto-sync: file changes are detected, auto-committed, and pushed Versioned: every change is a commit — full history, rollback anytime Encrypted: Ed25519 keypair per installation — private key never leaves the machine Multi-provider: user picks where their vault lives
Providers
ProviderTypeSetupClawRoam CloudManaged (paid per MB)One command — clawroam cloud signupGoogle DriveBYOS (free)OAuth flow via clawroam provider gdriveDropboxBYOS (free)OAuth flow via clawroam provider dropboxFTP/SFTPBYOS (free)Host + credentials via clawroam provider ftpGitBYOS (free)Any git remote via clawroam provider gitS3BYOS (free)Any S3-compatible via clawroam provider s3WebDAVBYOS (free)Nextcloud etc via clawroam provider webdavLocalBYOS (free)USB/NAS mount via clawroam provider local "BYOS" = Bring Your Own Storage. Free forever. ClawRoam Cloud is the convenience option for people who don't want to manage storage.
What Syncs
ALWAYS SYNCED (shared knowledge pool): identity/USER.md Who you are knowledge/MEMORY.md Long-term memory knowledge/projects/ Project context requirements.yaml System packages skills-manifest.yaml Installed skills list NEVER AUTO-SYNCED (per-instance): local/SOUL.md This agent's personality local/IDENTITY.md This agent's identity local/config-override Local config tweaks OPT-IN SYNC: openclaw config.json Gateway/model config credentials/ Channel auth (encrypted separately)
Commands
When the user asks about vault operations, use these:
First-Time Setup
"set up clawroam" → clawroam.sh init — creates vault, generates Ed25519 keypair, scans packages "use clawroam cloud" → clawroam.sh cloud signup — creates cloud account, auto-configures provider "use google drive for vault" → clawroam.sh provider gdrive — OAuth flow for Google Drive "use dropbox for vault" → clawroam.sh provider dropbox "use FTP for vault" → clawroam.sh provider ftp — asks for host, port, credentials
Daily Use (mostly invisible)
"sync status" → clawroam.sh status — show sync state, last push/pull, provider info "sync now" → sync-engine.sh push — force immediate sync "show vault history" → sync-engine.sh log — show commit history (like git log) "rollback vault" → sync-engine.sh rollback — revert to previous state "what changed" → sync-engine.sh diff — show pending changes
Packages
"scan packages" → track-packages.sh scan "what's different from vault" → track-packages.sh diff "install missing packages" → track-packages.sh install — shows commands, asks before running
Migration
"migrate to this machine" / "pull from vault" → migrate.sh pull — interactive restore wizard "push my soul to vault" → migrate.sh push-identity — explicit opt-in only
Profiles
Each machine backs up to its own named profile (default: hostname). Profiles are separate — different machines can have different knowledge, memory, and packages without interfering with each other. "show profile" / "what profile am I on" → clawroam.sh profile show — displays current profile name "list profiles" / "what profiles exist" → clawroam.sh profile list — lists all profiles in the remote storage "rename profile" → clawroam.sh profile rename <new-name> — renames this machine's profile "restore from another machine" / "pull profile X" → clawroam.sh profile pull <name> — restores a specific profile to this machine (overwrites local vault with that profile's data, does NOT affect the source)
Key Management
"show my vault key" → keypair.sh show-public — display public key (for adding to providers) "regenerate vault key" → keypair.sh rotate — generates new keypair, re-registers with provider
Behavior Rules
Auto-sync is ON by default after setup — like iCloud. The user should not have to think about syncing. Changes are pushed within 30 seconds. Never sync SOUL.md or IDENTITY.md without explicit permission. Always confirm before installing packages. Show the diff, let them pick. Private key never leaves the machine. It's stored in ~/.clawroam/keys/ with 600 permissions. The public key is registered with the vault provider. Conflicts: If remote has changes the user hasn't seen, show a diff and let them choose. Auto-merge for non-conflicting changes (like git). Be transparent about costs. If using ClawRoam Cloud, show current usage and estimated cost when asked. Never surprise the user with charges. Offline-first. Everything works locally. Sync happens when connectivity is available. Queue changes and push when back online. Profiles are separate by default. Each machine pushes to its own named profile (default: hostname). Profiles never merge automatically. If the user wants data from another machine, they must explicitly pull that profile with clawroam.sh profile pull <name>.
ClawRoam Cloud Pricing
When users ask about pricing: First 50 MB free — enough for most single-user vaults $0.005/MB/month after that (~$0.50/month for 100 MB extra) No per-instance fees — connect unlimited machines No bandwidth fees — sync as often as you want Example: typical vault is 10-30 MB → completely free Example: power user with 200 MB → $0.75/month Example: team vault with 2 GB → ~$10/month
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs2 Config1 Scripts
- SKILL.md
- CLAUDE.md
- README.md
- clawroam.sh
- cloud-api/package-lock.json
- cloud-api/package.json