openclaw-migration

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

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ar0cket1/Hermes-Agent-Online-RL --skill openclaw-migration-ar0cket1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/ar0cket1/Hermes-Agent-Online-RL/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/ar0cket1/Hermes-Agent-Online-RL --skill openclaw-migration-ar0cket1

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrate a user's OpenClaw footprint into Hermes Agent by importing persona, memories, workspace settings, commands, and skills, then report exactly what could not be migrated.

Core Features & Use Cases

  • Import SOUL.md into Hermes persona and migrate MEMORY.md and USER.md into Hermes memories.
  • Merge OpenClaw command approvals into Hermes command_allowlist and copy OpenClaw skills into ~/.hermes/skills/openclaw-imports/.
  • Optionally migrate Hermes-compatible secrets, copy workspace instructions, and preserve and archive unmapped docs for manual review.
  • Generate a structured migration report that details migrated items, conflicts, skipped items, and any archival actions.

Quick Start

Run a dry-run migration to preview what would be migrated, then execute with a chosen preset and conflict-resolution strategy.

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

You can migrate an OpenClaw footprint into Hermes by importing SOUL.md, MEMORY.md, and USER.md, merging command_allowlist, and copying skills. A dry-run preview shows exactly what will transfer before execution.

Can I preview what gets migrated before executing the OpenClaw import?

Yes, you can run a dry-run migration to preview what would be migrated from OpenClaw into Hermes. This generates a structured report detailing migrated items, conflicts, skipped items, and archival actions before executing.

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

The migration optionally copies Hermes-compatible secrets and workspace TTS/assets into Hermes. Unmapped docs are preserved and archived for manual review, with all archival actions tracked in the final report.

What happens to OpenClaw commands and skills during the Hermes migration?

OpenClaw command approvals merge into Hermes command_allowlist, and OpenClaw skills copy into ~/.hermes/skills/openclaw-imports/. The report identifies any conflicts or items that could not be migrated.

How are migration conflicts and unmapped files resolved when importing to Hermes?

Migration conflicts are resolved using a chosen conflict-resolution strategy during execution. Unmapped docs are preserved and archived for manual review, while the structured report details all conflicts and skipped items.