Automate X (Twitter) Data and Actions from Hermes

Hermes Tweet installs as a Hermes Agent plugin that registers the hermes-tweet toolset with exploration, read, and action tools for X endpoints, plus a skill and slash commands like /xstatus and /xtrends for account status and trends.

Hermes Intermediate Copied: 0
1 resource

Requirements

  • Set XQUIK_API_KEY in ~/.hermes/.env before using tweet_read; if Hermes is already running, apply it with /reload or restart gateway and cron sessions.
  • Reading account state requires XQUIK_API_KEY to be configured.
  • Hermes plugin system.
  • The hermes-tweet toolset.
  • An Xquik API key for read calls.
  • Optional: Hermes cron or gateway for scheduled monitoring.

How to use

tweet_explore searches the generated Xquik endpoint catalog without network credentials.

Endpoint exploration does not require an Xquik API key.

tweet_read calls safe read-only endpoints after an API key is configured.

tweet_action is blocked unless the operator explicitly enables write actions with HERMES_TWEET_ENABLE_ACTIONS=true.

Safety boundary for write calls: keep actions disabled until the operator authorizes them.

The default posture is read-first: write actions require a separate environment flag and an explicit operator-approved payload.

Operator approval remains a separate gate after the environment flag is enabled.

hermes tools list is the scriptable diagnostics command for current Hermes v0.12.x runtimes.

Bare hermes tools opens an interactive UI.

This is a focused Xquik integration, not a general social scheduler.

Use it when Hermes needs direct X data and action endpoints.

Interactive plugin installation:

Install and enable the plugin from the public repository.

hermes plugins install Xquik-dev/hermes-tweet --enable

For non-interactive hosts, install the Python package inside the Hermes environment and enable it.

~/.hermes/hermes-agent/venv/bin/python -m pip install hermes-tweet
hermes plugins enable hermes-tweet
hermes tools list

Set XQUIK_API_KEY in ~/.hermes/.env before using tweet_read. If Hermes is already running, use /reload in the interactive CLI, or restart gateway and cron sessions so the updated environment is loaded. Leave HERMES_TWEET_ENABLE_ACTIONS unset unless the current run is allowed to perform write actions.

Credential-free endpoint exploration:

Explore the available X endpoints without credentials.

Use tweet_explore to find X/Twitter search endpoints. Do not call tweet_action.
Return the safest read endpoint and required query fields.

Read account state after configuring XQUIK_API_KEY.

Use tweet_explore, then read /api/v1/account with tweet_read.
Summarize the account status and do not call tweet_action.

Monitor trends from an interactive session.

/xtrends

Operator-approved posting flow.

Draft a short product update for X. Before any write, show the exact endpoint,
method, and JSON body you would send through tweet_action. Wait for approval.

Source: aliaihub/awesome-hermes-usecases and its contributors. License: CC-BY-4.0. Source license notice.

Translation and editorial adaptation by ClawCases.

>Resources

>Related Use Cases

>More at this level: Intermediate