openclaw-migration

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrate a user's OpenClaw customization footprint into Hermes Agent. It imports 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 Hermes-compatible memories from MEMORY.md and USER.md, and import SOUL.md into the Hermes home directory.
  • Merge OpenClaw command allowlists into Hermes command_allowlist, preserving security settings, with a detailed migration report of conflicts.
  • Copy OpenClaw skills into ~/.hermes/skills/openclaw-imports/ and migrate workspace assets, while preserving backups and documenting outcomes.
  • Generate a structured report detailing what was migrated, what was archived/skipped, and any conflicts for manual review.

Quick Start

Run the migration tool in dry-run mode first to preview changes, then execute the migration to import data 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 my OpenClaw footprint into Hermes?

You can migrate memories, SOUL.md profiles, command allowlists, user skills, and workspace assets from OpenClaw into Hermes while generating a detailed report of any items that cannot be migrated.

How does command allowlist migration work when importing OpenClaw to Hermes?

Command allowlist migration merges OpenClaw command permissions into the Hermes command_allowlist while preserving existing security settings and generating a detailed conflict report for manual review.

Can I preview OpenClaw to Hermes migration changes before applying them?

Yes, you can run the migration tool in dry-run mode to preview exactly which memories, skills, and workspace assets will be imported or skipped before executing the actual migration into Hermes.

What happens to OpenClaw skills during the Hermes migration?

OpenClaw skills are copied into the ~/.hermes/skills/openclaw-imports/ directory during migration, preserving backups and documenting the migration outcomes in a structured report.

Does the OpenClaw to Hermes migration support conflict resolution and secret migration?

Yes, the migration supports configurable conflict resolution strategies, optional secret migration, and workspace-target handling to ensure a complete OpenClaw setup port into Hermes.

What limitations exist when porting an OpenClaw setup to Hermes?

The migration reports exactly what could not be migrated and why, as not all OpenClaw customizations may be Hermes-compatible, requiring manual review of archived or skipped items in the structured report.