openclaw-migration

Migrate OpenClaw customization files into Hermes Agent with conflict handling.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/JKhyro/HERMES-AGENT --skill openclaw-migration-jkhyro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/JKhyro/HERMES-AGENT/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/JKhyro/HERMES-AGENT --skill openclaw-migration-jkhyro

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill moves an existing OpenClaw personalization footprint into Hermes Agent so users do not have to rebuild memories, persona data, command approvals, and workspace assets by hand.

Core Features & Use Cases

  • Guided migration of SOUL.md, MEMORY.md, USER.md, allowlists, messaging settings, skills, and selected workspace files.
  • Dry-run previews, conflict handling, backups, and clear reporting of skipped, archived, or unresolved items.
  • Useful when upgrading from OpenClaw to Hermes, onboarding an existing agent setup, or auditing what can be transferred safely.

Quick Start

Ask the agent to inspect my OpenClaw installation and migrate the compatible parts into Hermes with a dry run first.

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

To migrate OpenClaw setups into Hermes safely, the skill performs guided or dry-run transfers of SOUL.md, MEMORY.md, USER.md, allowlists, skills, and selected workspace files using deterministic helper scripts.

Can I preview what gets transferred before moving my OpenClaw workspace to Hermes?

Yes, requesting a dry-run migration previews exactly which persona files, memories, allowlists, and workspace assets will be migrated, skipped, archived, or left unresolved before applying any changes to Hermes.

Does the OpenClaw to Hermes migration tool handle conflict resolution for duplicate workspace files?

Yes, the migration process includes built-in conflict resolution and backup creation to safely handle overlapping workspace assets, skills, and configuration files without overwriting existing Hermes data.

What do I need to set up before moving my OpenClaw customization footprint into Hermes?

You need an existing OpenClaw installation at ~/.openclaw with YAML-frontmatter skill instructions, the PyYAML dependency installed, and a Hermes Agent environment ready to receive the migrated data.

Why are some OpenClaw skills or workspace assets skipped or marked unresolved during migration?

Items are skipped or marked unresolved when they lack compatible YAML-frontmatter skill instructions or when workspace assets have structural conflicts that cannot be deterministically resolved by the migration scripts.

What is the best way to audit my OpenClaw installation before upgrading to Hermes?

Running a guided dry-run migration audits your OpenClaw setup by generating a structured report of all compatible persona files, memories, allowlists, and skills that can be safely transferred to Hermes.