migrate-openclaw
Skill5 starsChanged 8 months agoMITView on GitHub
One-click migration from OpenClaw to Claude-Agent. Reads ~/.openclaw/ and imports memory, skills, agents, conversations, and configuration. Preserves your assistant's personality, knowledge, and customizations. Use when user says "migrate from openclaw", "import openclaw data", "switch from openclaw", or "I'm coming from openclaw".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- clawsouls/clawsouls-claude-code-plugintheir own version, first seen Apr 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- clawsouls/clawsouls-claude-code-plugin★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- apple-notesSkill
- apple-remindersSkill
- bear-notesSkill
- brainstormSkill
- cameraSkill
- content-creatorSkill
- context-healthSkill
- daily-briefingSkill
- deep-readSkill
- draft-messageSkill
- emailSkill
- exa-searchSkill
- gh-issuesSkill
- gif-searchSkill
- github-opsSkill
- google-workspaceSkill
- hue-lightsSkill
- image-genSkill
- imessageSkill
- memory-managerSkill
- notionSkill
- obsidianSkill
- password-managerSkill
- pdf-editorSkill
- peekabooSkill
- placesSkill
- podcast-makerSkill
- quick-researchSkill
- rss-monitorSkill
- security-auditSkill
- session-logsSkill
- setupSkill
- skill-creatorSkill
- slack-opsSkill
- smart-bedSkill
- sonosSkill
- speech-to-textSkill
- spotifySkill
- summarizeSkill
- task-trackerSkill
- text-to-speechSkill
- things-macSkill
- tmux-controlSkill
- trelloSkill
- trend-scoutSkill
- video-extractSkill
- weatherSkill
- whatsappSkill
- x-twitterSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 11 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 41
If not found, ask the user for the path:
- Very specific: line 43
If they provide a path, use --openclaw-dir <path>
- Distinctive: line 47
Run the migration script in dry-run mode to show what will be migrated:
- Distinctive: line 59
Ask the user to confirm:
- Distinctive: line 71
If the user wants to merge with existing data:
- Distinctive: line 78
After migration, read the report:
- Distinctive: line 90
Run a quick verification:
- Very specific: line 91
Check memory files are populated: ls memory/
- Very specific: line 92
Check skills were added: ls .claude/skills/
- Very specific: line 93
Check CLAUDE.md was updated: grep "OpenClaw" CLAUDE.md
- Distinctive: line 119
If the migration script fails:
- Distinctive: line 120
Read the error output carefully
- Distinctive: line 128
Always run dry-run first to preview
- Very specific: line 129
Never overwrite existing data without --merge flag
- Distinctive: line 130
Never copy credentials directly — note them for manual re-configuration
- Distinctive: line 131
Keep the conversation friendly — this is someone switching their daily assistant
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Migrate from OpenClaw
You are the OpenClaw migration skill for Claude-Agent. Help the user migrate their data from OpenClaw to Claude-Agent with a smooth, guided experience.
Prerequisites
The migration script is at scripts/migrate-openclaw.cjs (Node.js, zero dependencies).
Steps
1. Check OpenClaw Installation
First, check if OpenClaw is installed:
ls -la ~/.openclaw/ 2>/dev/nullIf not found, ask the user for the path:
- "Where is your OpenClaw installation? (default: ~/.openclaw/)"
- If they provide a path, use
--openclaw-dir <path>
2. Preview Migration (Dry Run)
Run the migration script in dry-run mode to show what will be migrated:
node scripts/migrate-openclaw.cjs --dry-run --verbosePresent the summary to the user:
- How many skills, agents, memory entries will be migrated
- What will be skipped
- Any manual actions required
3. Confirm with User
Ask the user to confirm:
- "Ready to migrate? This will import your OpenClaw data into Claude-Agent."
- "Your existing Claude-Agent data will be preserved (new data is added alongside it)."
- "Use --merge to overwrite existing data if you want to re-run the migration."
4. Run Migration
Execute the full migration:
node scripts/migrate-openclaw.cjs --verboseIf the user wants to merge with existing data:
node scripts/migrate-openclaw.cjs --merge --verbose5. Read and Present Report
After migration, read the report:
cat workspace/migration-report.mdPresent a friendly summary:
- What was successfully migrated
- What needs manual attention
- Next steps
6. Verify
Run a quick verification:
- Check memory files are populated:
ls memory/ - Check skills were added:
ls .claude/skills/ - Check CLAUDE.md was updated:
grep "OpenClaw" CLAUDE.md
7. Welcome Message
End with a warm welcome:
Welcome to Claude-Agent! Your OpenClaw data has been imported.
What was migrated:
- Your personality (SOUL.md → CLAUDE.md)
- Your knowledge base (MEMORY.md → memory/)
- Your skills (N skills adapted to Claude Code format)
- Your workflows (AGENTS.md → individual agents)
- Your recent conversations (summarized)
What you might want to do next:
- Say "good morning" for a briefing with your imported data
- Run /context-health to see everything loaded properly
- Try your migrated skills to see them in action
Your assistant is ready. How can I help?Fallback
If the migration script fails:
- Read the error output carefully
- Common issues:
- Permission denied →
chmod +x scripts/migrate-openclaw.cjs - OpenClaw path wrong → ask user for correct path
- JSON parse error → OpenClaw config may use unsupported JSON5 features
- Permission denied →
- Offer to migrate components individually (memory only, skills only, etc.)
Rules
- Always run dry-run first to preview
- Never overwrite existing data without --merge flag
- Never copy credentials directly — note them for manual re-configuration
- Keep the conversation friendly — this is someone switching their daily assistant
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

