geekjourneyx

Openclaw To Hermes Migration — Development skill for Claude Code

Development community

Agent skill for safely migrating OpenClaw workspaces to Hermes Agent with providers, gateways, cron jobs, and rollback.

How to install Openclaw To Hermes Migration

This entry records only its repository, not the path inside it, so there is no exact command to give. Open geekjourneyx/openclaw-to-hermes-migration and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Openclaw To Hermes Migration does

Agent skill for safely migrating OpenClaw workspaces to Hermes Agent with providers, gateways, cron jobs, and rollback.

Alternatives in Development

Agent Skills Platform — Build tested agent skills and govern their lifecycle through a user-defined marketplace: evidence, discovery 2.4k ★
Agent Skill Creator — Build tested agent skills and govern their lifecycle through a user-defined marketplace: evidence, discovery 2.3k ★
Agentic Stack — One brain, many harnesses 2.2k ★

README

OpenClaw to Hermes Migration

**A production-safe Codex skill for migrating OpenClaw workspaces to Hermes Agent**

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](./LICENSE) [![Skill](https://img.shields.io/badge/Codex-Skill-4b5563.svg)](./SKILL.md) [![Migration](https://img.shields.io/badge/OpenClaw-to%20Hermes-c96442.svg)](./SKILL.md) [![Evals](https://img.shields.io/badge/Evals-5%20scenarios-2563eb.svg)](./evals/evals.json)

What This Is

OpenClaw to Hermes Migration is a Codex skill that turns a risky agent-runtime migration into a staged, verifiable operating procedure. It preserves the parts that matter: identity, memory, skills, provider configuration, messaging gateways, cron intent, and rollback safety.

The skill is designed for real cutovers where OpenClaw may still be writing runtime files, Hermes must be configured with new model providers, and messaging channels such as Feishu or Weixin need to keep working after migration.

Input:  An existing ~/.openclaw installation with skills, memory, providers, gateways, and cron jobs
Output: A verified ~/.hermes setup with imported user data, tested provider access, gateway service, and rollback path

Core Capabilities

The SOP emphasizes behavior preservation over blind file copying. It uses dry-runs, checksums, explicit backups, non-secret inspection commands, and acceptance checks before treating Hermes as the replacement runtime.