OpenClaw -> Hermes Migration

Use this skill when a user wants to move their OpenClaw setup into Hermes Agent with minimal manual cleanup.

CLI Command

For a quick, non-interactive migration, use the built-in CLI command:

hermes claw migrate              # Full interactive migration
hermes claw migrate --dry-run    # Preview what would be migrated
hermes claw migrate --preset user-data   # Migrate without secrets
hermes claw migrate --overwrite  # Overwrite existing conflicts
hermes claw migrate --source /custom/path/.openclaw  # Custom source

The CLI command runs the same migration script described below. Use this skill (via the agent) when you want an interactive, guided migration with dry-run previews and per-item conflict resolution.

First-time setup: The hermes setup wizard automatically detects ~/.openclaw and offers migration before configuration begins.

What this skill does

It uses scripts/openclaw_to_hermes.py to:

• import SOUL.md into the Hermes home directory as SOUL.md
• transform OpenClaw MEMORY.md and USER.md into Hermes memory entries
• merge OpenClaw command approval patterns into Hermes command_allowlist
• migrate Hermes-compatible messaging settings such as TELEGRAM_ALLOWED_USERS and MESSAGING_CWD
• copy OpenClaw skills into ~/.hermes/skills/openclaw-imports/
• optionally copy the OpenClaw workspace instructions file into a chosen Hermes workspace
• mirror compatible workspace assets such as workspace/tts/ into ~/.hermes/tts/
• archive non-secret docs that do not have a direct Hermes destination
• produce a structured report listing migrated items, conflicts, skipped items, and reasons

Path resolution

The helper script lives in this skill directory at:

• scripts/openclaw_to_hermes.py

When this skill is installed from the Skills Hub, the normal location is:

• ~/.hermes/skills/migration/openclaw-migration/scripts/openclaw_to_hermes.py

Do not guess a shorter path like ~/.hermes/skills/openclaw-migration/....

Before running the helper:

1. Prefer the installed path under ~/.hermes/skills/migration/openclaw-migration/.
2. If that path fails, inspect the installed skill directory and resolve the script relative to the installed SKILL.md.
3. Only use find as a fallback if the installed location is missing or the skill was moved manually.
4. When calling the terminal tool, do not pass workdir: "~". Use an absolute directory such as the user's home directory, or omit workdir entirely.

With --migrate-secrets, it will also import a small allowlisted set of Hermes-compatible secrets, currently:

• TELEGRAM_BOT_TOKEN

Default workflow