openclaw-migration

Migrate OpenClaw memories, SOUL.md, user profiles, and workspace assets into Argo Agent.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/nadicodeai/argo-agent --skill openclaw-migration-nadicodeai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/nadicodeai/argo-agent/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/nadicodeai/argo-agent --skill openclaw-migration-nadicodeai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrate OpenClaw footprints (memory, persona, and workspace assets) into Argo Agent so you can continue workflows with minimal manual cleanup.

Core Features & Use Cases

  • Import SOUL.md, MEMORY.md, USER.md, and OpenClaw skills into Argo-compatible equivalents.
  • Merge OpenClaw workspace assets and command configurations, with conflict reporting and dry-run previews.
  • Archive unmapped artifacts for manual review and produce a migration report.

Quick Start

Install the migration skill and run the migration to start importing your OpenClaw footprint into Argo and generate a report.

Frequently Asked Questions about openclaw-migration

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

FAQPage Schema
How do I migrate OpenClaw memories and personas into Argo Agent?

To migrate OpenClaw memories and personas into Argo Agent, the skill imports SOUL.md, MEMORY.md, and USER.md files into Argo-compatible equivalents using a guided dry-run that handles conflict resolution and generates a detailed migration report.

What is the best way to import OpenClaw workspace assets and commands into Argo?

The best way to import OpenClaw workspace assets is to use a migration script that merges configurations, reports conflicts during a dry-run preview, and archives unmapped artifacts for manual review.

Do I need PyYAML to run the OpenClaw to Argo migration?

Yes, you need PyYAML installed because the migration script depends on it to parse OpenClaw data structures and safely update Argo configuration files during the import process.

Can I preview OpenClaw footprint migration before applying changes to Argo?

Yes, you can preview the migration through a guided dry-run that highlights configuration conflicts, merges workspace assets, and archives unmapped artifacts before any permanent changes are made to your Argo setup.

What happens to unmapped OpenClaw skills during the Argo migration?

Unmapped OpenClaw skills and artifacts are archived for manual review, and the migration process generates a detailed report so you can address any unresolved configurations after the import.