openclaw-migration

Migrates OpenClaw customizations to Hermes Agent via CLI.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/NITISH-gitbit/hermes-custom --skill openclaw-migration-nitish-gitbit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/NITISH-gitbit/hermes-custom/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/NITISH-gitbit/hermes-custom --skill openclaw-migration-nitish-gitbit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Migrates a user's OpenClaw customization into Hermes Agent, importing memories, command allowlists, and selected workspace assets, ensuring a seamless transition with detailed reporting.

Core Features & Use Cases

  • Selective Migration: Imports Hermes-compatible memories, SOUL.md, command allowlists, user skills, and workspace assets from ~/.openclaw.
  • Conflict Resolution: Reports what could not be migrated and why, with options for user intervention.
  • Use Case: When a user is transitioning from OpenClaw to Hermes Agent and needs to preserve their customizations.

Quick Start

Run the migration using the CLI command: hermes claw migrate

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 customizations to Hermes Agent?

To migrate OpenClaw customizations to Hermes Agent, run the `hermes claw migrate` CLI command, which imports Hermes-compatible memories, SOUL.md, command allowlists, user skills, and workspace assets from the ~/.openclaw directory.

What assets can I selectively migrate from OpenClaw to Hermes?

Selective migration from OpenClaw to Hermes supports importing memories, SOUL.md persona state, command allowlists, user skills, and selected workspace assets, ensuring your core customizations transition seamlessly.

How are migration conflicts handled when transitioning from OpenClaw?

Migration conflicts are handled through interactive conflict resolution, which reports exactly what could not be migrated and why, providing options for user intervention and configuration adjustments during the transition.

Does the OpenClaw to Hermes migration require manual configuration adjustments?

Yes, the OpenClaw to Hermes migration requires user interaction for conflict resolution and configuration adjustments, specifically when incompatible customizations are detected or selective asset imports need validation.

Why are some OpenClaw memories not migrated to Hermes Agent?

Some OpenClaw memories are not migrated because the process only imports Hermes-compatible memories, generating a detailed report of what could not be migrated and why to guide manual intervention.