openclaw-migration

Migrate OpenClaw data into Hermes Agent with a detailed report.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/gqf2008/hermez-ai --skill openclaw-migration-gqf2008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/gqf2008/hermez-ai/tree/main/skills/migration/openclaw-migration
Command: npx skills add https://github.com/gqf2008/hermez-ai --skill openclaw-migration-gqf2008

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 memories, SOUL.md, command allowlists, user skills, and workspace assets, and by generating a clear report of what could not be migrated and why.

Core Features & Use Cases

  • Imports Hermes-compatible memories (MEMORY.md and USER.md equivalents) and the SOUL persona, preserving context and branding.
  • Merges OpenClaw command allowlists and skills into Hermes structure, with optional conflict handling and backup preservation.
  • Copies workspace assets and builds a migration report that highlights migrated items, conflicts, and items archived for manual review.
  • Supports dry-run previews, per-item conflict resolution prompts, and optional secret-migration when explicitly requested.

Quick Start

Run the migration to import OpenClaw memories, SOUL.md, command allowlists, user skills, and workspace assets into Hermes and review the detailed migration report.

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 memories and SOUL.md into Hermes Agent?

To migrate OpenClaw memories and SOUL.md, use this Skill to import data from ~/.openclaw into Hermes structures. It validates and merges your persona and memory files while preserving context and generating a detailed report of migrated items.

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

Yes, you can preview OpenClaw data migration using the dry-run feature. This allows you to review exactly what memories, skills, and workspace assets will be imported or skipped before modifying your Hermes configuration.

Does the OpenClaw to Hermes migration handle command allowlist and workspace assets?

Yes, the OpenClaw to Hermes migration copies workspace assets and merges command allowlists. It integrates your existing configurations into the Hermes structure while preserving backups and handling any conflicts during the transfer.

What happens to conflicting user skills during the OpenClaw to Hermes transfer?

During the OpenClaw to Hermes transfer, conflicting user skills are managed with per-item conflict resolution prompts. The Skill archives items needing manual review and reports exactly what was skipped or merged.

Do I need pyyaml to import OpenClaw configurations into Hermes?

Yes, pyyaml is required as a dependency to import OpenClaw configurations into Hermes. The Skill relies on this library to parse and validate the YAML-formatted configuration files stored under your ~/.openclaw directory.

How does the migration tool report skipped or archived OpenClaw items?

The migration tool reports skipped or archived OpenClaw items by generating a detailed migration report. This report highlights exactly which memories, skills, and assets were successfully migrated, skipped, or archived for manual review.