openclaw-migration

Migrate OpenClaw customization data into Hermes Agent with conflict reporting.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/big4council-prog/b4c-agent --skill openclaw-migration-big4council-prog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/big4council-prog/b4c-agent/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/big4council-prog/b4c-agent --skill openclaw-migration-big4council-prog

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It eliminates the manual cleanup work required to port your OpenClaw persona, memory, command approvals, user skills, and workspace/compatible assets into Hermes Agent, while producing a precise report of what could not be migrated and why.

Core Features & Use Cases

  • Guided migration with safeguards: Performs a dry-run first, then executes only after required conflict decisions are clarified.
  • Faithful footprint import: Migrates Hermes-compatible items such as SOUL.md, memory entries, USER profile, command allowlists, messaging settings, and OpenClaw skills.
  • Conflict reporting and remediation: Detects conflicts (e.g., existing Hermes targets) and supports configurable conflict handling modes, producing structured output for manual review.

Quick Start

Tell Hermes to run the migration with a preview first by saying: Run OpenClaw to Hermes migration in dry-run mode.

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

OpenClaw migration imports your persona, memory, messaging settings, command allowlists, and skills into Hermes Agent by running the openclaw_to_hermes.py script. It performs a dry-run first, then executes after conflict decisions are clarified.

What is migrated when moving OpenClaw workspace assets to Hermes?

Migrating OpenClaw workspace assets imports Hermes-compatible items such as SOUL.md, memory entries, USER profile, command allowlists, messaging settings, and OpenClaw skills. Unmapped or incompatible items are archived.

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

Yes, you can run OpenClaw to Hermes migration in dry-run mode to preview changes. The migration generates a transparent, redacted report detailing what will be migrated and what could not be mapped.

How are conflicts handled during OpenClaw persona and memory import?

OpenClaw persona and memory import detects conflicts like existing Hermes targets and supports configurable conflict handling modes. It produces structured output for manual review to ensure safe onboarding transitions.

Does the OpenClaw migration require a specific environment setup?

OpenClaw migration requires a root SKILL.md frontmatter with name and description, and the yaml dependency. It is designed for first-time Hermes setup and planned onboarding transitions with minimal manual cleanup.

What happens to unmapped or incompatible OpenClaw items during Hermes onboarding?

During Hermes onboarding, unmapped or incompatible OpenClaw items are archived rather than discarded. The migration script produces a precise report explaining exactly what could not be migrated and why.