openclaw-migration

Migrate OpenClaw user footprints into Hermes Agent with YAML parsing and backups.

3|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/twjarviszyra-web/hermes-unbound --skill openclaw-migration-twjarviszyra-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/twjarviszyra-web/hermes-unbound/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/twjarviszyra-web/hermes-unbound --skill openclaw-migration-twjarviszyra-web

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill removes the manual work of moving an OpenClaw setup into Hermes Agent by converting compatible persona, memory, allowlist, skill, and workspace assets into Hermes-friendly locations.

Core Features & Use Cases

It supports dry-run discovery, selective migration modes, conflict-aware file handling, backups, and structured reporting so users can safely assess what will migrate before writing changes. Typical uses include importing SOUL.md, MEMORY.md, USER.md, command approval patterns, OpenClaw skills, workspace instructions, and compatible TTS assets while clearly reporting skipped or unsupported items.

Quick Start

Ask the assistant to inspect your OpenClaw directory with a dry run first, then migrate the compatible items into Hermes using the conflict and workspace options you choose.

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 assets into Hermes Agent?

This Skill automates OpenClaw to Hermes Agent migration by converting compatible persona, memory, allowlist, and skill files into Hermes-friendly locations through YAML config parsing and filesystem inspection.

Can I preview my OpenClaw footprint before migrating to Hermes?

Yes, you can run a dry-run discovery to safely assess your OpenClaw footprint before migrating to Hermes, generating a structured report of compatible items and skipped unsupported files without writing any changes.

Does the OpenClaw to Hermes transfer support command allowlist merging?

Yes, the OpenClaw to Hermes transfer supports command allowlist merges, selectively importing command approval patterns alongside SOUL.md, MEMORY.md, and USER.md persona files.

What's the best way to handle file conflicts when importing OpenClaw personas?

The best way to handle file conflicts when importing OpenClaw personas is using conflict-aware file handling with automatic backups, allowing selective migration modes to safely overwrite or preserve existing Hermes assets.

Do I need pyyaml to migrate OpenClaw memory and skills into Hermes?

Yes, you need pyyaml installed to migrate OpenClaw memory and skills into Hermes, as the Skill requires YAML config parsing to read and convert your existing footprint assets.

When should I preserve secrets during an OpenClaw workspace transfer?

You should preserve secrets during an OpenClaw workspace transfer when migrating sensitive configurations, using optional secret-preserving execution to move assets without exposing or overwriting protected authentication data.