openclaw-migration

Migrate OpenClaw memories, SOUL.md, allowlists, skills, and assets into Hermes Agent.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge --skill openclaw-migration-chris-chai-minjae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge --skill openclaw-migration-chris-chai-minjae

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrates an OpenClaw footprint into Hermes Agent, importing memories, SOUL.md, command allowlists, user skills, and workspace assets to create a seamless Hermes environment.

Core Features & Use Cases

  • Import OpenClaw memories and SOUL.md into Hermes
  • Migrate workspace assets, command allowlists, and user skills into Hermes structure
  • Generate a detailed migration report highlighting conflicts, skips, and archived items

Quick Start

Run the migration script to begin transferring data from OpenClaw into Hermes.

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 settings into Hermes?

Run the migration script with a source OpenClaw directory and a Hermes target to import memories, SOUL.md, command allowlists, user skills, and workspace assets into the Hermes structure.

What data is included when moving an OpenClaw footprint to Hermes?

An OpenClaw footprint migration to Hermes includes memories, SOUL.md profiles, command allowlists, user skills, and workspace assets, with optional secrets migration and structured conflict reporting.

Do I need a source OpenClaw directory to migrate to Hermes Agent?

Yes, the migration requires a source OpenClaw directory and a Hermes target to transfer profiles, settings, and skills while generating a report of conflicts and archived items.

How are conflicts handled when importing OpenClaw workspace assets into Hermes?

Conflict handling during the OpenClaw to Hermes migration generates a structured report highlighting conflicts, skips, and archived items to ensure data integrity across memories and settings.

Can I migrate command allowlists and user skills from OpenClaw to Hermes?

Yes, the migration process imports command allowlists and user skills from OpenClaw into the Hermes structure, transferring them alongside memories and workspace assets.