openclaw-migration

Migrate OpenClaw persona data, memories, and settings into Hermes Agent with a structured report.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/1thirteeng3/greenmoire --skill openclaw-migration-1thirteeng3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/1thirteeng3/greenmoire/tree/main/integrations/hermes-agent/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/1thirteeng3/greenmoire --skill openclaw-migration-1thirteeng3

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrate an OpenClaw customization footprint into Hermes Agent by importing Hermes-compatible memories, SOUL.md, command allowlists, user skills, and selected workspace assets from ~/.openclaw, then reports exactly what could not be migrated and why.

Core Features & Use Cases

  • Import SOUL.md into Hermes home or workspace as a Hermes SOUL, transform MEMORY.md and USER.md into Hermes memories, and merge OpenClaw command approvals into Hermes command_allowlist.
  • Copy OpenClaw skills into ~/.hermes/skills/openclaw-imports/ and optionally mirror workspace assets (e.g., workspace docs and TTS data) into Hermes-enabled locations.
  • Generate a structured migration report listing migrated items, conflicts, skipped items, and archived docs.

Quick Start

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

To migrate OpenClaw footprints to Hermes Agent, import SOUL.md, MEMORY.md, and USER.md from ~/.openclaw. The migration transforms these files into Hermes-compatible memories and generates a structured report of the transfer results.

Can I transfer OpenClaw command allowlists and skills into Hermes?

Yes, OpenClaw command approvals merge into the Hermes command_allowlist, and user skills copy directly into ~/.hermes/skills/openclaw-imports. The migration process preserves your existing command permissions and custom skill configurations during the transfer.

What happens to unmapped workspace documents during OpenClaw to Hermes migration?

Unmapped workspace documents are archived during the OpenClaw to Hermes migration process. The skill generates a structured migration report listing all migrated items, conflicts, skipped files, and archived docs to ensure full visibility of the transfer outcome.

Does the OpenClaw to Hermes migration support workspace assets and secrets?

The migration optionally mirrors workspace assets like docs and TTS data into Hermes-enabled locations and can migrate secrets. It reads openclaw.json for configuration, merges memory entries with size limits, and updates Hermes config files accordingly.

Do I need PyYAML to run the OpenClaw footprint migration?

Yes, PyYAML is required to run the OpenClaw to Hermes migration scripts. This dependency enables the skill to read openclaw.json configuration, parse YAML-based memory and persona files, and update Hermes config and allowlist files properly.

What is OpenClaw to Hermes migration and when do I need it?

OpenClaw to Hermes migration is the process of importing persona data, memories, settings, and workspace assets from ~/.openclaw into Hermes Agent format. You need it when transitioning from OpenClaw while preserving your custom agent footprint and configurations.