Agent Migration
v1.0.1Safely rename or migrate an OpenClaw agent by updating config and naming, migrating session content, fixing session metadata, restarting, verifying, and aski...
⭐ 0· 78·0 current·0 all-time
by@kid0114
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the actual behavior: scripts and docs operate on ~/.openclaw, agent directories, sessions.json and workspace paths to copy and verify session data and update config. The declared high local-permission requirement in README/metadata is appropriate for the actions performed.
Instruction Scope
SKILL.md confines actions to migration tasks and references the included scripts for inspect/copy/verify. It reads/writes OpenClaw config, agent dirs, workspace and session metadata — which is expected. One minor note: verify script calls an external command (openclaw doctor) that is not declared in required binaries; the runtime will need that binary available. Guardrails (no hard-edit of locks, require confirmation before deletion) are present.
Install Mechanism
No install spec; this is instruction-only with included shell scripts. No downloads or external installers are used, so nothing arbitrary is fetched or executed from remote URLs.
Credentials
The skill requests no environment variables or credentials. It does require elevated local file permissions to modify ~/.openclaw and workspace paths, which is proportional to migration behavior and is documented in README/metadata.
Persistence & Privilege
always is false and the skill does not request persistent or system-wide privileges beyond modifying its own agent-related files. It does not modify other skills' configs or assert permanent presence.
Assessment
This package is coherent with its stated purpose but performs high‑impact local file operations. Before using: (1) review the three included scripts to ensure they match your expectations; (2) back up ~/.openclaw and any workspace directories; (3) run inspect/summary modes first (copy script supports a summary mode) to preview changes; (4) ensure you run commands as the correct user (avoid root unless you understand why); (5) confirm the presence of the openclaw CLI if you plan to use verify (openclaw doctor); (6) never delete the old agent until you have manually verified the new agent and have explicit backup/consent. If you want additional assurance, provide a sandboxed test agent and perform a dry run there first.Like a lobster shell, security has layers — review code before you run it.
agentvk97eg4z1xapp7fp7rhyy81mr7h83nk46latestvk97d3kmc8kx13mtw7rezk8eamx83x1eymigrationvk97eg4z1xapp7fp7rhyy81mr7h83nk46openclawvk97eg4z1xapp7fp7rhyy81mr7h83nk46sessionvk97eg4z1xapp7fp7rhyy81mr7h83nk46workspacevk97eg4z1xapp7fp7rhyy81mr7h83nk46
License
MIT-0
Free to use, modify, and redistribute. No attribution required.