Hermes Tweet
Use this skill when a Hermes Agent session needs X/Twitter research, social listening, account reads, trend checks, monitor setup, extraction jobs, giveaway draws, media changes, or controlled posting through the native Hermes Tweet plugin.
Source: https://github.com/Xquik-dev/hermes-tweet
Install
Prefer the native Hermes plugin installer:
hermes plugins install Xquik-dev/hermes-tweet --enable
hermes plugins list
hermes tools list
If Git install is unavailable, install the PyPI package into the Hermes Agent virtual environment:
uv pip install --python ~/.hermes/hermes-agent/venv/bin/python hermes-tweet
hermes plugins enable hermes-tweet
hermes tools list
Configuration
tweet_explore works without network access or an API key.
tweet_read requires XQUIK_API_KEY.
tweet_action requires XQUIK_API_KEY and HERMES_TWEET_ENABLE_ACTIONS=true.
- Keep
HERMES_TWEET_ENABLE_ACTIONS=false for public research, public monitoring, support triage, and unattended sessions that do not require private or action-only routes.
- Enable actions only when the user explicitly asks to post, reply, send DMs, follow, run private reads, manage webhooks, manage monitors, run extraction jobs, draw giveaways, or change media.
If XQUIK_API_KEY is added to ~/.hermes/.env while Hermes is running, use /reload in the active CLI session before calling tweet_read.
Operating Procedure
- Run
tweet_explore first to find the exact endpoint and required arguments.
- Use
tweet_read for catalog-listed read-only public routes.
- Use
tweet_action only after confirming the request is private, write-like, or otherwise action-only, and action gating is enabled.
- Never route private or write-like endpoints through
tweet_read.
- Keep action gating disabled for cron and gateway jobs unless the workflow requires private reads or action-only operations.
Smoke Test
hermes -z "Use tweet_explore, then read /api/v1/account. Do not call tweet_action." --toolsets hermes-tweet
Expected behavior:
- Without
XQUIK_API_KEY, Hermes exposes only tweet_explore.
- With
XQUIK_API_KEY, tweet_read can call /api/v1/account.
tweet_action stays unavailable or disabled unless HERMES_TWEET_ENABLE_ACTIONS=true.
References
1---2name: hermes-tweet3description: Install and operate Hermes Tweet, the native Hermes Agent X/Twitter plugin for endpoint discovery, read-only calls, and explicitly gated action-only workflows.4---56# Hermes Tweet78Use this skill when a Hermes Agent session needs X/Twitter research, social listening, account reads, trend checks, monitor setup, extraction jobs, giveaway draws, media changes, or controlled posting through the native Hermes Tweet plugin.910Source: <https://github.com/Xquik-dev/hermes-tweet>1112## Install1314Prefer the native Hermes plugin installer:1516```bash17hermes plugins install Xquik-dev/hermes-tweet --enable18hermes plugins list19hermes tools list20```2122If Git install is unavailable, install the PyPI package into the Hermes Agent virtual environment:2324```bash25uv pip install --python ~/.hermes/hermes-agent/venv/bin/python hermes-tweet26hermes plugins enable hermes-tweet27hermes tools list28```2930## Configuration3132- `tweet_explore` works without network access or an API key.33- `tweet_read` requires `XQUIK_API_KEY`.34- `tweet_action` requires `XQUIK_API_KEY` and `HERMES_TWEET_ENABLE_ACTIONS=true`.35- Keep `HERMES_TWEET_ENABLE_ACTIONS=false` for public research, public monitoring, support triage, and unattended sessions that do not require private or action-only routes.36- Enable actions only when the user explicitly asks to post, reply, send DMs, follow, run private reads, manage webhooks, manage monitors, run extraction jobs, draw giveaways, or change media.3738If `XQUIK_API_KEY` is added to `~/.hermes/.env` while Hermes is running, use `/reload` in the active CLI session before calling `tweet_read`.3940## Operating Procedure41421. Run `tweet_explore` first to find the exact endpoint and required arguments.432. Use `tweet_read` for catalog-listed read-only public routes.443. Use `tweet_action` only after confirming the request is private, write-like, or otherwise action-only, and action gating is enabled.454. Never route private or write-like endpoints through `tweet_read`.465. Keep action gating disabled for cron and gateway jobs unless the workflow requires private reads or action-only operations.4748## Smoke Test4950```bash51hermes -z "Use tweet_explore, then read /api/v1/account. Do not call tweet_action." --toolsets hermes-tweet52```5354Expected behavior:5556- Without `XQUIK_API_KEY`, Hermes exposes only `tweet_explore`.57- With `XQUIK_API_KEY`, `tweet_read` can call `/api/v1/account`.58- `tweet_action` stays unavailable or disabled unless `HERMES_TWEET_ENABLE_ACTIONS=true`.5960## References6162- Repository guide: <https://github.com/Xquik-dev/hermes-tweet#readme>63- PyPI package: <https://pypi.org/project/hermes-tweet/>64- Hermes plugins guide: <https://hermes-agent.nousresearch.com/docs/user-guide/features/plugins/>65- Build a Hermes plugin: <https://hermes-agent.nousresearch.com/docs/guides/build-a-hermes-plugin/>