hermes-action-bridge

name	hermes-action-bridge
description	Delegate external actions, Hermes skills, browser automation, messaging, cron jobs, and integrations to Hermes Agent through hermes-action. Use when a task needs capabilities outside the local coding session.

Hermes Action Bridge

Use this skill when a task needs capabilities outside the local coding session: Hermes skills or memory, messaging platforms, browser automation, scheduled or cron automation, external research, or any platform integration already configured in Hermes Agent.

Do not reimplement those integrations here. Delegate them to Hermes through the hermes-action CLI.

When to use

• The task requires a Hermes skill, tool, profile, or connected service.
• The task needs a real-world action that is not local code editing.
• The task needs research, messaging, browser, or scheduled automation Hermes owns.

Safe default

Ask Hermes for a plan first; it has no side effects:

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

With context

Write a concise handoff to a file and pass it explicitly:

hermes-action run --preset coding --context ./handoff.md "<request>"

External side effects

For public posts, outbound email or messages, deletes, payments, credential changes, or git pushes, require human approval:

hermes-action run --mode request-approval "<request requiring side effects>"

Never use --yolo unless the human explicitly asked for trusted local execution. It bypasses only the bridge policy, not Hermes' own safety rules.

Verify setup

hermes-action status
hermes-action run --dry-run --json "Return BRIDGE_OK only."