Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated tweet actions. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing guarded tweet actions. Use proactively when a Hermes Agent workflow needs current X/Twitter context. Requires XQUIK_API_KEY for read and action tools.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-14 | ✗→✓ | ▲ Improved | -12% | 0% |
| case-01 | ✗→✓ | ▲ Improved | 23% | 0% |
| case-04 | ✗→✓ | ▲ Improved | -5% | 0% |
| case-05 | ✗→✓ | ▲ Improved | 2% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -16% | 0% |
Hermes Tweet adds an X/Twitter toolset to Hermes Agent. It is useful for social listening, account research, launch monitoring, support triage, giveaway audits, and controlled publishing workflows where actions stay explicit.
Use this skill when the user wants to:
Install the package into the Hermes Python environment, then enable the plugin:
bash~/.hermes/hermes-agent/venv/bin/python -m pip install hermes-tweet hermes plugins enable hermes-tweet
Set the API key on the Hermes runtime host:
bashexport XQUIK_API_KEY="<your-key>" export HERMES_TWEET_ENABLE_ACTIONS="false"
Keep HERMES_TWEET_ENABLE_ACTIONS false for read-first sessions. Set it to true only for sessions that intentionally need posting, replies, DMs, follows, webhooks, monitors, media changes, or other account-changing routes.
Ask for these inputs before selecting routes:
XQUIK_API_KEYtweet_explore to find matching routes.tweet_read after selecting a catalog route.tweet_action only after explicit approval.campaign, monitor, support, or giveaway workflow instead of a single read.
| Tool | Purpose | | --- | --- | | tweet_explore | Search the bundled endpoint catalog without using the API key. | | tweet_read | Call catalog-listed read-only endpoints when XQUIK_API_KEY is set. | | tweet_action | Call action routes only when action gating is enabled. |
Return concise operational output:
textSummary: - What was checked and why Read routes: - Catalog path, input, and result summary Action plan: - Proposed account-changing actions, each awaiting explicit approval Next check: - Follow-up route or monitoring cadence when useful
Research an account before drafting a reply:
textUse Hermes Tweet to inspect recent public context for @example before drafting a reply. Keep actions disabled.
Monitor a launch keyword:
textTrack X/Twitter mentions for "Example Launch" today. Summarize themes and notable accounts. Do not post.
Prepare a guarded post:
textDraft a launch tweet and list the exact tweet_action call you would use. Wait for approval before any action route.
Capture structured route notes:
json{ "objective": "support-triage", "route": "/api/v1/x/search", "action_gate": "disabled", "approval_required": true }
tweet_explore appears, configure XQUIK_API_KEY on the Hermes runtimehost and reload or restart the active Hermes session.
HERMES_TWEET_ENABLE_ACTIONS=true only for an approved action session.
tweet_explore again and choose a catalog-listedpath instead of guessing endpoints.
tweet_read or tweet_action.The social-publishing plugin complements Hermes Tweet for broad multi-platform publishing. Hermes Tweet is focused on the Hermes Agent X/Twitter toolset and its read-first, approval-gated operating model.
See the official guide at https://github.com/Xquik-dev/hermes-tweet#readme.
Other measured skills in the registry, with their headline benchmark lift.