openclaw-migration
PassAudited by ClawScan on May 1, 2026.
Overview
This is a plain migration checklist with no executable code or credentials, but it does describe renaming, editing, and possibly deleting project files.
Before installing or using this skill, treat it as a repository migration checklist: apply changes in version control, inspect diffs, run tests and linting, and explicitly approve any removal of the old project directory or changes to agent metadata files.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If followed, the agent may rename, copy, edit, or remove project files, which could break the project if done incorrectly.
The skill directs potentially broad repository mutations, including moving or removing directories. This is expected for a migration guide, but it can materially change the workspace.
either rename `clawdbot/` → `openclaw/` or copy its contents ... remove or archive the old `clawdbot/` directory once the new structure is stable
Use this in a version-controlled workspace, review the planned diff, run tests, and confirm before deleting or archiving the old directory.
Incorrect edits to these files could change how future agents interpret the project or behave in the repository.
The playbook includes moving or updating persistent agent metadata, persona, memory, and skill files. This is coherent with the migration, but those files can influence future agent behavior.
decide where `AGENTS.md`, `SOUL.md`, `MEMORY.md`, `skills.json`, `skills/` should live relative to the new app root
Review changes to agent, persona, memory, and skill metadata carefully, and keep backups or version-control history for rollback.