hermes - 💡(How to fix) Fix [Feature] claude-to-hermes migration skill — official Claude plugin import path

Summary

Hermes ships an official openclaw-migration skill that migrates OpenClaw → Hermes. Claude Code has a large ecosystem of community skills (1000+ in ComposioHQ/awesome-claude-skills alone, 228 in affaan-m/everything-claude-code). There is no equivalent official path to import Claude skills into Hermes.

Feature Request

Add an official claude-to-hermes-migration skill (or rename/generalize the existing migration skill) to help users bring their Claude plugin investments into Hermes.

Context

Existing reference: openclaw-migration

hermes claw migrate is backed by official/migration/openclaw-migration, which:

• Inventories the source workspace (~/.openclaw/)
• Maps OpenClaw concepts (SOUL.md, hooks, plugins, memory) → Hermes equivalents
• Handles credential scrubbing and path translation
• Produces a Hermes-ready workspace snapshot

Related work: ECC hermes-imports

The everything-claude-code (ECC) project ships a hermes-imports skill that does the reverse: converts Hermes workflows → ECC skills. Their cross-harness architecture doc explicitly states:

"SKILL.md is the most portable unit. A good ECC skill should: use YAML frontmatter with name, description, and origin..."

This suggests the structural gap is not in SKILL.md format but in the migration tooling — hooks, commands, and plugin-level integration points differ between Claude and Hermes.

The ecosystem gap

Without an official Claude → Hermes migration, users who invest in Claude skill ecosystems have no upgrade path when choosing Hermes as their operator shell.

Proposed Solution

Add official/migration/claude-to-hermes-migration (or generalize openclaw-migration into a multi-source migration skill) that:

1. Inventories Claude plugin surfaces — skills/, instructions/, hooks/, commands/, AGENTS.md

2. Maps Claude concepts → Hermes equivalents:

   Claude concept	Hermes equivalent
   skills/*.md	~/.hermes/skills/*/ — mostly SKILL.md compatible
   instructions/	Agent prompts / SOUL.md
   hooks/hooks.json	Hermes hooks system
   commands/	Hermes commands
   .mcp.json	MCP server registration in config.yaml
   rules/	Hermes rules / AGENTS.md

3. Handles sanitization — scrub absolute paths, credentials, personal data (similar to ECC's sanitization checklist)

4. Produces a migration report — what was migrated, what requires manual attention, what is unsupported

Alternatives Considered

• Rely on ECC's hermes-imports — only does Hermes → ECC (reverse direction), not Claude → Hermes
• Treat SKILL.md compatibility as sufficient — hooks, commands, and MCP integration differ enough that this is not a zero-effort port
• Let community maintain migration tools — the OpenClaw precedent shows official tooling is preferred for this migration path

Related Reference: Pantheon — Hermes + Claude multi-agent orchestration

Repo: https://github.com/5percentdrops/pantheon

Pantheon is an AI-native software studio (33 agents) that uses Hermes as the unified runtime for all agents, with Claude Code models integrated as specific agent engines. It provides a reference implementation for Hermes ↔ other harness interoperability.

Relevant pattern: cross-harness escalation schema

Pantheon defines an escalation_packet.schema.json that explicitly supports routing between different harnesses:

{
  "origin_harness": "OpenClaw",
  "target_harness": "Hermes",
  "escalation_type": "missing_input|tool_error|ambiguous_decision|quality_failure|..."
}

This proves Hermes can serve as the control-plane runtime while delegating specialized tasks (e.g. code review) to Claude Code — suggesting the architecture for a claude-to-hermes-migration skill is viable and already partially demonstrated.

Key takeaway

Pantheon shows Hermes is already capable of acting as the coordination layer for a mixed harness environment. A Claude → Hermes migration skill would extend this pattern from "runtime co-existence" to "full skill portability", giving users a concrete upgrade path from the Claude ecosystem into Hermes.

Labels

type/feature, comp/plugins, tool/skills