openclaw-migration

Migrate OpenClaw memories, skills, and workspace assets into Hermes Agent.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/jacardl/New-Radar --skill openclaw-migration-jacardl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/jacardl/New-Radar/tree/main/backend/frameworks/hermes-agent/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/jacardl/New-Radar --skill openclaw-migration-jacardl

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrate and normalize an OpenClaw user footprint into Hermes Agent by importing persona data, memories, skills, and workspace assets, plus reporting what couldn't be migrated.

Core Features & Use Cases

  • Import SOUL.md into Hermes home as SOUL.md and convert MEMORY.md and USER.md into Hermes memories.
  • Merge OpenClaw command approval patterns into Hermes command_allowlist and preserve workspace assets for later use.
  • Copy OpenClaw skills into ~/.hermes/skills/openclaw-imports/ and optionally archive unmapped docs for review.
  • Generate a detailed migration report listing migrated items, conflicts, and skipped items.

Quick Start

Run the OpenClaw-to-Hermes migration tool to begin transferring your data and then review the generated 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 workspace assets to Hermes Agent?

To migrate OpenClaw memories and workspace assets to Hermes Agent, run the openclaw-migration script to import user footprints from ~/.openclaw into Hermes directories, converting MEMORY.md and USER.md into Hermes memories while preserving workspace assets for later use.

Can I import OpenClaw SOUL.md and command allowlists into Hermes without overwriting existing data?

You can import OpenClaw SOUL.md and merge command approval patterns into Hermes command_allowlist using conflict handling policies, allowing you to preserve existing Hermes data while integrating OpenClaw footprint configurations safely.

Does the OpenClaw to Hermes migration support a dry-run before executing the actual data import?

The OpenClaw to Hermes migration supports a dry-run mode to validate data and preview the transfer of memories, skills, and workspace assets, producing a structured report of migrated items, conflicts, and skipped items before execution.

What is the best way to transfer OpenClaw user skills into Hermes directories?

The best way to transfer OpenClaw user skills is using the migration tool to copy them directly into ~/.hermes/skills/openclaw-imports/, which normalizes the skill format and optionally archives unmapped docs for review.

Why does my OpenClaw footprint migration report show skipped items and conflicts?

Migration reports show skipped items and conflicts when the tool detects data validation issues or overlapping configurations between OpenClaw footprints and existing Hermes Agent files, requiring user-specified policies to resolve them.

Do I need yaml dependencies to run the OpenClaw footprint migration script?

You need the yaml dependency installed to run the OpenClaw footprint migration script, as the tool relies on it to parse configuration files and validate workspace assets during the Hermes Agent import process.