openclaw-migration

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

OpenClaw footprints are not directly usable in Hermes and require manual consolidation of memories, persona data, and configurations. This skill automates the migration, preserving memory entries, persona files, workspace assets, and skill mappings while reporting any items that cannot be migrated.

Core Features & Use Cases

  • Import SOUL.md into Hermes as the Hermes persona file.
  • Convert MEMORY.md and USER.md from OpenClaw into Hermes memories and profiles.
  • Merge OpenClaw command approvals into Hermes command_allowlist.
  • Copy OpenClaw skills into ~/.hermes/skills/openclaw-imports/ for review or usage.
  • Migrate workspace assets and optional workspace instructions, with a detailed migration report.
  • Archive unmapped docs for manual review.

Quick Start

Run hermes claw migrate to begin migrating your OpenClaw footprint into Hermes with an interactive dry-run option.

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

Migrate OpenClaw memories and persona files into Hermes by running the migration pipeline, which imports SOUL.md, MEMORY.md, and USER.md while preserving workspace assets and generating a detailed report of any migration gaps.

Can I transfer OpenClaw command approvals to Hermes automatically?

Yes, OpenClaw command approvals are merged directly into the Hermes command_allowlist during the migration process, ensuring your existing permissions carry over without manual reconfiguration.

What happens to OpenClaw skills and unmapped docs during migration?

OpenClaw skills are copied into ~/.hermes/skills/openclaw-imports/ for review, while unmapped documents are archived separately so you can manually review any content that cannot be mapped automatically.

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

Yes, the migration supports optional secret migration and workspace instructions across local paths, allowing you to consolidate configurations while controlling what sensitive data is transferred.

How do I handle memory conflicts when importing OpenClaw data into Hermes?

The migration pipeline supports options for handling memory conflicts, workspace targets, and optional secret migration, providing a structured merge process that reports any items requiring manual review.

What is the best way to preview an OpenClaw footprint migration before committing?

Run the interactive dry-run option to preview the migration of your OpenClaw footprint into Hermes, allowing you to review memory merges and configuration imports before executing the full transfer.