Skip to content

TheBlueHouse75/hermes-action-bridge / plugins/hermes-action/skills/hermes-action-bridge

hermes-action-bridge

Verified

Use Hermes Agent for Hermes-owned skills, memory, connected services, messaging, browser workflows, schedules, and external automation. Prefer the installed hermes_* MCP tools; use the CLI only as a fallback.

Hermes Action Bridge

Use this skill when a task needs state or capabilities owned by Hermes Agent: Hermes skills or memory, connected services, messaging platforms, browser workflows, scheduled automation, or another integration configured in Hermes.

Do not reimplement a Hermes-owned integration in the coding agent. Prefer the installed hermes_* MCP tools so the host can discover, approve, and inspect the delegation.

When to use

  • The task names Hermes, a Hermes skill, memory, preset, or connected service.
  • The task needs messaging, scheduling, browser work, or persistent external automation Hermes owns.
  • The task must continue as a cancellable background job outside the local coding step.

Do not use Hermes for ordinary local code edits or repository inspection that the current agent can perform directly.

Discover first

Call hermes_capabilities before assuming an integration is configured. Use hermes_status to check the runtime without spending provider tokens.

Safe delegation

  • Use hermes_plan for plan-mode analysis, but treat it as open-world and review its output.
  • Use hermes_submit, then hermes_job_status / hermes_result, for a long cancellable plan or draft.
  • Use hermes_cancel when a queued or running job is no longer wanted.

External side effects

For public posts, outbound messages, deletes, payments, credential changes, or git pushes:

  1. Call hermes_prepare to produce a local no-tool summary and approval ID.
  2. Call hermes_approve to open the MCP client's interactive confirmation form. The bridge shows the exact action and executes only if the human accepts and checks the confirmation field.
  3. Call hermes_reject when the action is no longer wanted.

Never answer or simulate the confirmation form yourself. Clients without MCP form elicitation fail closed; use plan, draft, or direct supervised CLI work instead of trying to bypass that boundary.

CLI fallback

If MCP tools are unavailable, use the local CLI:

hermes-action run --mode plan "<describe what Hermes should do>"

Verify setup

hermes-action doctor
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall