openclaw-migration

Migrate OpenClaw persona, memories, skills, and workspace data into Hermes Agent structures.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/afel6/scal-ai-pipeline --skill openclaw-migration-afel6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/afel6/scal-ai-pipeline/tree/main/hermes_skills_library/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/afel6/scal-ai-pipeline --skill openclaw-migration-afel6

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrates a user's OpenClaw footprint into Hermes Agent by importing persona, memories, skills, and workspace data, then reports exactly what could not be migrated and why.

Core Features & Use Cases

  • Import SOUL.md as Hermes persona
  • Convert MEMORY.md and USER.md into Hermes memories
  • Merge OpenClaw command approvals into Hermes command_allowlist and sync messaging settings
  • Copy OpenClaw skills into ~/.hermes/skills/openclaw-imports/
  • Copy workspace instructions and TTS assets when present
  • Produce a structured migration report detailing migrated items, conflicts, archives, and any skipped data

Quick Start

Run the migration CLI to migrate your OpenClaw footprint into Hermes, starting with a dry-run to preview changes and conflicts before executing.

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

Migrating an OpenClaw footprint into Hermes imports persona, memories, commands, and workspace data into Hermes-compatible structures. The CLI performs an interactive dry-run to preview changes before executing the end-to-end relocation.

Does OpenClaw migration support importing command approvals and messaging settings into Hermes?

OpenClaw migration merges command approvals into the Hermes command_allowlist and synchronizes messaging settings. This ensures Hermes adopts existing OpenClaw permissions without requiring manual reconfiguration of your agent environment.

What happens to OpenClaw skills when migrating to Hermes?

OpenClaw skills are copied directly into the ~/.hermes/skills/openclaw-imports/ directory during migration. This preserves your existing skill configurations and makes them immediately available within the Hermes Agent workspace.

Can I preview OpenClaw to Hermes migration conflicts before executing changes?

The migration CLI supports an interactive dry-run phase to preview changes and conflicts before execution. It uses configurable conflict handling during the execute phase and produces a detailed migration report of migrated items and skipped data.

What data cannot be migrated from OpenClaw to Hermes?

The migration process produces a structured report detailing exactly what could not be migrated and why. This includes skipped data, conflicts, and archived items, ensuring full transparency regarding any unmigrated workspace or configuration elements.

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

Yes, pyyaml is a required dependency for executing the OpenClaw to Hermes migration scripts. This Python library handles the parsing and conversion of configuration files during the relocation process.