agentleFS
claude-worldclaude-world/claude-agent/.claude/skills/migrate-openclaw/SKILL.md

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

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
  1. Distinctive:

    If not found, ask the user for the path:

    line 41
  2. Very specific:

    If they provide a path, use --openclaw-dir <path>

    line 43
  3. Distinctive:

    Run the migration script in dry-run mode to show what will be migrated:

    line 47
  4. Distinctive:

    Ask the user to confirm:

    line 59
  5. Distinctive:

    If the user wants to merge with existing data:

    line 71
  6. Distinctive:

    After migration, read the report:

    line 78
  7. Distinctive:

    Run a quick verification:

    line 90
  8. Very specific:

    Check memory files are populated: ls memory/

    line 91
  9. Very specific:

    Check skills were added: ls .claude/skills/

    line 92
  10. Very specific:

    Check CLAUDE.md was updated: grep "OpenClaw" CLAUDE.md

    line 93
  11. Distinctive:

    If the migration script fails:

    line 119
  12. Distinctive:

    Read the error output carefully

    line 120
  13. Distinctive:

    Always run dry-run first to preview

    line 128
  14. Very specific:

    Never overwrite existing data without --merge flag

    line 129
  15. Distinctive:

    Never copy credentials directly — note them for manual re-configuration

    line 130
  16. Distinctive:

    Keep the conversation friendly — this is someone switching their daily assistant

    line 131

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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/null

If 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 --verbose

Present 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 --verbose

If the user wants to merge with existing data:

node scripts/migrate-openclaw.cjs --merge --verbose

5. Read and Present Report

After migration, read the report:

cat workspace/migration-report.md

Present 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:

  1. Read the error output carefully
  2. 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
  3. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.