openclaw-migration

Migrate OpenClaw persona, memory, and skill files into Hermes Agent.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill moves an existing OpenClaw customization footprint into Hermes Agent so users do not have to recreate memories, persona files, allowlists, skills, and workspace assets by hand.

Core Features & Use Cases

  • Persona and memory migration: Imports SOUL.md, MEMORY.md, and USER.md content into Hermes-friendly destinations.
  • Config and access translation: Merges messaging settings, command approval patterns, and selected secrets when explicitly allowed.
  • Skill and asset transfer: Copies compatible OpenClaw skills and workspace assets, then records conflicts, skips, and archive items for review.

Quick Start

Ask the skill to dry-run an OpenClaw migration from your local workspace and summarize what will migrate, what will be skipped, and what needs manual review.

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

Migrating OpenClaw persona and memory files into Hermes requires importing SOUL.md, MEMORY.md, and USER.md content into Hermes-friendly destinations using a Python helper that preserves conflicts for review.

Can I dry-run an OpenClaw migration before applying changes?

Yes, you can dry-run an OpenClaw migration from your local workspace to summarize what will migrate, what will be skipped, and what needs manual review before any files are modified.

Does the OpenClaw migration transfer command allowlists and messaging settings?

Yes, OpenClaw migration translates and merges messaging settings, command approval patterns, and selected secrets into Hermes when explicitly allowed by configuration.

How are workspace asset conflicts handled during OpenClaw migration?

Workspace asset conflicts during OpenClaw migration are preserved, logged as skips, and recorded in a structured report for manual review rather than being overwritten automatically.

Do I need PyYAML to run the OpenClaw to Hermes migration?

Yes, PyYAML is required as a dependency to parse the SKILL.md entry point with YAML frontmatter and execute the Python migration helper for reading OpenClaw files.

What is the best way to back up existing Hermes targets before an OpenClaw migration?

The best way to back up existing Hermes targets is using the built-in migration helper, which automatically creates backups of existing targets before writing new OpenClaw workspace assets.