openclaw-migration

Migrate OpenClaw memories, persona, commands, skills, and workspace assets into Hermes Agent.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Plaidmustache/hermes-nulab --skill openclaw-migration-plaidmustache
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/Plaidmustache/hermes-nulab/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/Plaidmustache/hermes-nulab --skill openclaw-migration-plaidmustache

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

OpenClaw users who want to move to Hermes Agent can migrate memories, persona, workspace settings, and skills with minimal manual cleanup, and receive a clear report on any migration gaps.

Core Features & Use Cases

  • Import MEMORY.md and USER.md into Hermes memories to preserve long-term context.
  • Migrate SOUL.md into Hermes persona and merge OpenClaw command approval patterns into Hermes command_allowlist.
  • Copy OpenClaw skills into ~/.hermes/skills/openclaw-imports/ for later activation.
  • Optionally copy or align workspace instructions and assets into Hermes workspace; archive unmapped docs for review.
  • Produce a structured migration report listing migrated items, conflicts, archives, and unresolved items.

Quick Start

Run the migration to import your OpenClaw footprint into Hermes and review the resulting 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 persona into Hermes Agent?▼

To migrate OpenClaw memories and persona into Hermes Agent, this tool imports MEMORY.md and USER.md into Hermes memories, converts SOUL.md into a Hermes persona, and merges command allowlists. It handles the end-to-end transfer automatically.

What data cannot be migrated from OpenClaw to Hermes?▼

Unmappable workspace documents and unresolved configuration conflicts cannot be migrated from OpenClaw to Hermes. The tool archives unmapped docs for manual review and outputs a structured migration report detailing exactly what failed and why.

Can I import OpenClaw skills into the Hermes workspace?▼

Yes, you can import OpenClaw skills into the Hermes workspace. The migration process copies your existing user skills directly into the ~/.hermes/skills/openclaw-imports/ directory, making them available for later activation within Hermes.

Do I need PyYAML to run the OpenClaw to Hermes migration?▼

Yes, PyYAML is required to run the OpenClaw to Hermes migration. The script depends on PyYAML to read and merge YAML configuration files, parse SKILL.md frontmatter for skill discovery, and process workspace assets correctly.

How does the migration handle command approval patterns from OpenClaw?▼

The migration handles command approval patterns by merging OpenClaw command approval settings directly into the Hermes command_allowlist. It uses interactive conflict handling to resolve any overlaps or discrepancies during the transfer process.

What is the best way to move workspace assets from OpenClaw to Hermes?▼

The best way to move workspace assets from OpenClaw to Hermes is using an automated migration tool that optionally copies or aligns workspace instructions, archives unmapped documents, and produces a structured report of all migrated items and conflicts.