openclaw-teleport

Migrate, backup, or restore an OpenClaw agent workspace to/from a single .soul file. Use when the user wants to move an agent to a new machine, back up their...

Security Scan

The skill's purpose (pack/unpack agent workspaces) is plausible, but the instructions rely on external CLIs/packages (npm/npx, gh, possibly gpg, system cron and service control) while declaring no dependencies or environment needs and will move plaintext credentials — these mismatches and the runtime download via npm warrant caution.

Purpose & Capability

The name/description match the instructions (pack/unpack workspace, include credentials, cron jobs, repos). However the SKILL.md expects tools like npm/npx, the @kagura-agent/openclaw-teleport npm package, the GitHub CLI (gh), and optionally gpg, but the registry metadata lists no required binaries or env vars — that's an inconsistency. A migration tool legitimately needs to read/write agent files and credentials, but it should declare prerequisites and explain privilege needs.

Instruction Scope

Instructions direct the agent/operator to create and restore archives containing identity files, memory, openclaw.json (channel credentials), cron jobs, clone GitHub repos, and start the gateway. Those actions are within migration scope, but they involve reading/writing sensitive credentials and modifying system state (cron, starting services). The SKILL.md does not constrain or describe elevated privileges, nor does it require confirmation/validation steps before restoring credentials/configs.

Install Mechanism

There is no install spec in the registry entry, but the instructions tell the user to run 'npm install -g @kagura-agent/openclaw-teleport' or 'npx @kagura-agent/openclaw-teleport'. Pulling and executing a third-party npm package at runtime is a moderate-risk action and should be explicit in the registry metadata. The package origin (npm) is common, but users should be warned to verify the package source and review code before running npx globally or as root.

Credentials

The skill declares no required env vars, yet it will read and write agent credentials (openclaw.json) and may require service tokens (e.g., GitHub tokens for 'gh', gateway credentials). Packing produces .soul files with plaintext credentials. The skill does not declare or justify access to these secrets in registry fields, so the credential access is under-documented and potentially surprising to users.

Persistence & Privilege

always:false (good), but unpacking performs persistent system changes: writes configs/credentials to openclaw.json, restores cron jobs, clones repos, and starts the gateway. Those are appropriate for a migration tool but are high-impact operations. The skill will likely require filesystem and possibly elevated privileges; the SKILL.md doesn't describe safeguards (dry-run, confirmations, sandboxing).

Scan Findings in Context

[no_regex_findings] expected: The static scanner found nothing because this is an instruction-only skill (only SKILL.md present). Lack of findings is expected but not informative about runtime behavior — the SKILL.md itself is the primary security surface.

What to consider before installing

This tool can move an entire agent workspace, including plaintext API tokens and bot secrets. Before using it: (1) verify the npm package (@kagura-agent/openclaw-teleport) source and inspect its code or repository; (2) prefer using 'npm install' in a controlled environment (or run npx inside a disposable VM/container) rather than running as root on your main machine; (3) ensure you have local backups and perform a dry-run or inspect the .soul with 'inspect' before unpacking; (4) transfer .soul files only over encrypted channels and consider encrypting them with 'gpg -c' as suggested; (5) confirm which CLIs will be used (gh, git, gpg) and that you understand their credential needs; and (6) if you need higher assurance, ask the skill author/source for a repository URL, a checksum for the npm package, or an install script you can audit. If you can't verify the npm package or don't trust running installers, avoid using npx and instead request the package source for manual review.

One-command agent migration: pack identity, memory, config, credentials, cron jobs, and workspace into a single .soul archive, then unpack on a new machine for full restoration.

Install

npm install -g @kagura-agent/openclaw-teleport

Or use npx without installing:

npx @kagura-agent/openclaw-teleport pack

Commands

Pack (export)

# Pack the default (first) agent
openclaw-teleport pack

# Pack a specific agent by name
openclaw-teleport pack kagura

Produces a <name>_<date>.soul file (tar.gz) containing:

• Full workspace (identity files, memory, skills, workflows, databases — excluding git repo subdirectories)
• Agent config + channel credentials from openclaw.json
• Cron job definitions
• GitHub repo list (re-cloned on unpack)

Unpack (import/restore)

# Restore to default workspace (~/.openclaw/workspace)
openclaw-teleport unpack kagura_20260320.soul

# Restore to a custom workspace
openclaw-teleport unpack kagura_20260320.soul --workspace /path/to/workspace

Unpack automatically:

1. Installs OpenClaw if missing
2. Restores workspace files
3. Writes config + credentials to openclaw.json
4. Restores cron jobs
5. Clones GitHub repos via gh
6. Starts the gateway
7. Prints a welcome summary

Inspect

openclaw-teleport inspect kagura_20260320.soul

Shows manifest metadata without unpacking: agent name, pack date, file count, repos, channels, cron jobs.

Security

⚠️ .soul files contain plaintext credentials (API tokens, bot tokens, app secrets). Treat them like password files:

• Never commit to git or share publicly
• Transfer via encrypted channels (SSH, encrypted USB)
• Delete after unpacking
• Optionally encrypt with gpg -c agent.soul

When to Use

• Moving to a new machine — pack on old, unpack on new
• Backup — periodic pack to save current state
• Disaster recovery — unpack from a saved .soul file
• Cloning an agent setup — share a .soul file (minus secrets) as a template