Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, a

Hermes Tweet 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 workflows where private or state changing operations stay explicit. When to Use This Skill Use this skill when the user wants to: Install Hermes Tweet into a Hermes Agent runtime Discover available X/Twitter read and action routes Read X/Twitter account, tweet, trend, monitor, or search data Summarize public signal before drafting responses or campaigns Keep private and state changing operations gated behind explicit operator intent Setup Install and enable the plugin through Hermes: Hermes scans plugins during installation and updates. Review each warning. A dangerous verdict blocks installation or disables an update. Set the API key on the Hermes runtime host: Keep HERMES TWEET ENABLE ACTIONS false for read first sessions. Set it to true only for an approved private read, write, monitor, webhook, extraction, draw, or media operation. Inputs Ask for these inputs before selecting routes: Objective: research, monitoring, support triage, giveaway audit, or action prep Target: account handle, tweet URL, keyword, list, monitor, or trend Time window and freshness needs Whether any private or state changing operation is in scope Confirmation that the Hermes runtime has XQUIK API KEY Workflow 1. Search the bundled endpoint catalog with tweet explore to find matching routes. 2. Read public X/Twitter data through tweet read after selecting a catalog route. 3. Use tweet action for private or state changing routes only after explicit approval. 4. Keep API keys in environment variables or the Hermes runtime env file. 5. Do not paste credentials into prompts, issues, PR comments, or tool inputs. 6. Load [workflow patterns](references/workflows.md) when the user asks for a campaign, monitor, support, or giveaway workflow instead of a single read. Tool Model Tool Purpose tweet explore Search the bundled endpoint catalog without using the API key. tweet read Call catalog listed public read only endpoints when XQUIK API KEY is set. tweet action Call private reads, writes, monitors, webhooks, extractions, draws, and media operations only when action gating is enabled. Output Format Return concise operational output: Usage Examples Research an account before drafting a reply: Monitor a launch keyword: Prepare a guarded post: Capture structured route notes: Troubleshooting If only tweet explore appears, configure XQUIK API KEY on the Hermes runtime host and reload or restart the active Hermes session. If action routes are unavailable, keep public reads separate. Set HERMES TWEET ENABLE ACTIONS=true only for an approved private or state changing operation. If a route does not match, use tweet explore again and choose a catalog listed path instead of guessing endpoints. Best Practices Treat Hermes Tweet as the Hermes native X/Twitter layer, not a generic API wrapper. Keep research read only by default. Require approval before creating or changing monitors. Use Desktop or gateway operator review before private or state changing calls. Validate the exact catalog path before calling tweet read or tweet action . Restart gateway, cron, or long running Hermes sessions after env changes. See Also 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 endpoint and approval contract](references/endpoint contract.md) when a route boundary is unclear. See the official guide at https://github.com/Xquik dev/hermes tweet readme.

hermes-tweet