openclaw-migration

Migrate OpenClaw memories, persona, skills, and settings into Anakot Agent.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill openclaw-migration-chensihakniroth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/Chensihakniroth/ANAKOT-AGENT/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill openclaw-migration-chensihakniroth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyYAML, and includes scripts (resource) components.

What problem does it solve? Moving from OpenClaw to Anakot Agent normally means manually copying persona files, memory entries, command allowlists, and user skills, with no clear record of what transferred and what was left behind. This Skill automates that migration and produces a structured report of every migrated, archived, skipped, or conflicting item. ## Core Features & Use Cases - Guided interactive migration: Runs a dry-run preview first, then uses structured clarify prompts to resolve SOUL.md conflicts, imported skill conflicts, migration mode, and workspace instruction destinations before executing. - Comprehensive data import: Converts OpenClaw MEMORY.md and USER.md into Anakot memory entries, imports SOUL.md, merges command allowlists, copies user skills into ~/.anakot/skills/openclaw-imports/, and mirrors compatible assets such as TTS files. - Safe secret handling and reporting: Migrates only an allowlisted set of secrets (such as TELEGRAM_BOT_TOKEN) when explicitly requested, redacts credentials in reports, and writes report.json and summary.md detailing exactly what could not be migrated and why. - Use Case: A user with an existing ~/.openclaw setup wants to switch agents. The Skill previews the migration, asks how to handle a conflicting SOUL.md and duplicate skills, executes the chosen preset, and reports archived leftovers for manual review. ## Quick Start Ask the agent to migrate your OpenClaw setup into Anakot, starting with a dry-run preview of what can be imported.

Frequently Asked Questions about openclaw-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from OpenClaw to Anakot Agent?▼

Run a dry run first with the openclaw_to_anakot.py script or the anakot claw migrate CLI command, review the summary, resolve conflicts through the interactive prompts, then execute with the user-data or full preset. A report lists everything migrated, archived, or skipped.

What data does the OpenClaw migration import?▼

It imports SOUL.md, converts MEMORY.md and USER.md into Anakot memory entries, merges command allowlist patterns, copies user skills into ~/.anakot/skills/openclaw-imports/, mirrors TTS assets, and transfers compatible messaging settings. Unmapped docs are archived for manual review.

Does the migration transfer API keys and secrets?▼

Secrets are not migrated by default. Only when you explicitly choose the full compatible migration with --migrate-secrets does it import a small allowlisted set such as TELEGRAM_BOT_TOKEN, and all report output redacts credential values.

What happens when imported skills conflict with existing Anakot skills?▼

The dry run flags skill conflicts and you choose a policy: skip to keep existing skills, overwrite with a backup, or rename the imported folders. The chosen mode is recorded in the report as skill_conflict_mode.

Why are some OpenClaw items skipped during migration?▼

Items are skipped when they have no clean Anakot destination, such as unsupported auth blobs, or when a target already exists and overwrite is disabled. Every skipped item appears in the report with its reason, and non-secret docs may be archived instead.