Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
clawd-migrate
v0.2.1Migrate moltbot or clawdbot assets to openclaw by discovering, backing up, migrating, verifying files, and reinstalling openclaw automatically.
⭐ 0· 600·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and SKILL.md describe migrating moltbot/clawdbot assets to an openclaw layout; the included Python and Node wrapper code implements discovery, backup, copy, verification, and an optional post-setup. Required env/credentials are none and required binaries are Python/Node/npm which match the described functionality. Minor metadata inconsistencies: registry metadata said "instruction-only" but the package contains implementation files; package.json version (0.2.0) differs from registry version 0.2.1; homepage/repository URL empty — these are bookkeeping issues but not functional red flags.
Instruction Scope
The runtime instructions and code scan the chosen root for files including .config/moltbook and .config/moltbot and will copy credential files (credentials.json / clawdbook data) into the target .config/clawdbook and into backups. That behaviour is expected for a migration tool, but it means secrets stored in those config files will be read and duplicated on disk. Documentation contains mixed wording about whether reinstalling openclaw runs automatically or is user-prompted; the migration code (run_migration) does not itself run openclaw install/onboard, so the docs overstate automatic behavior in places — the TUI or explicit flag is the likely trigger for install-onboard.
Install Mechanism
No install spec is embedded in the skill registry entry, and the package is designed for npm distribution (bin wrapper + scripts/copy-py.js). There are no external download URLs or extract steps in the bundle. The tool can run `npm install -g openclaw` (via subprocess) which fetches code from the npm registry — expected given the stated purpose. No obscure or high-risk install hosts are used in the provided files.
Credentials
The skill declares no required environment variables or credentials, which aligns with the code. However, the code intentionally reads and copies local configuration/credential files (e.g., .config/moltbook/credentials.json) and places them into backups and the openclaw target layout. This is proportionate to a migration tool, but users should understand that secret API keys/credentials present in those paths will be duplicated on disk. The Node wrapper sets PYTHONPATH to the packaged lib for execution — normal for this packaging approach.
Persistence & Privilege
The skill does not request permanent inclusion (always:false) and does not modify other skills or global agent config. It writes files to disk (backups and migrated copies) and invokes subprocesses (npm/openclaw) — expected for a migration utility. Use of shell=True for subprocesses is present to match user PATH, which is intentional for locating npm/openclaw on different platforms but means the commands run in the user's shell environment.
Assessment
This package appears to do what it says: discover your bot files, create a timestamped backup, copy memory/config/credential files into an openclaw layout, and verify copies. Before running it: 1) Review and trust the destination (it will duplicate any credentials found under .config/moltbook or .config/moltbot into backups and .config/clawdbook). 2) Run it in a safe/test environment first (use a temporary directory) to inspect the backup manifest and confirm what will be copied. 3) If you do not want the tool to install software from the network, avoid the post-migration install/onboard step (use the CLI/TUI options that skip setup) — note the docs are inconsistent about automatic install; the migration code does not itself call the installer, but the interactive flow or flags may. 4) Because the repository metadata (homepage/repo URL empty) and versions are slightly inconsistent, prefer to inspect the package source you plan to run (the files here are included) and, if using npm, prefer installing from a known author/repo. If you need further certainty, run the tool inside an isolated/containerized environment and inspect the created backups/_manifest.txt before deleting or moving any originals.Like a lobster shell, security has layers — review code before you run it.
latestvk97cm6sea460n2dnzgj6ggw2px812186
License
MIT-0
Free to use, modify, and redistribute. No attribution required.