hermes-agent-compatibilitylisted

# Hermes Agent Compatibility Maintain Socket's deliberate compatibility boundary with Hermes Agent. Start by classifying the requested Socket surface, then choose the narrowest Hermes surface that preserves its real behavior. ## Surface Map | Socket surface | Hermes equivalent | Compatibility outcome | | --- | --- | --- | | `SKILL.md` workflow | GitHub skill tap or direct GitHub skill install | Export when the workflow is portable instructions plus existing tools. | | Codex plugin bundle | None | Do not present `.codex-plugin/plugin.json` as a Hermes plugin. Keep it as Codex packaging only. | | `.mcp.json` server declaration | `mcp_servers` entry in `~/.hermes/config.yaml` | Translate the transport and required environment, then validate the server in Hermes. | | Hook, app, or custom-agent surface | Host-specific decision | Document the limit or build a real Hermes extension only if a concrete behavior needs it. | | Runtime integration with tools, hooks, commands, or bundled skills | Python Hermes plugin | Use `plugin.yaml` plus `register(ctx)` only when instruction-only or MCP configuration cannot express the behavior. | ## Maintain the Skill Tap Socket's Hermes tap is the checked-in root `skills/` export. Its authored source remains `plugins/agent-portability-skills/skills/`; do not edit the export manually. 1. Add or revise the authored skill under `plugins/agent-portability-skills/skills/`. 2. Use a lowercase hyphenated `name` that matches the skill directory and a