From hermes-tweet
Automates X/Twitter actions via Xquik: search, post, reply, like, retweet, follow, DM, monitor, extract, draw, media, and trends. Use for social listening, launch monitoring, support triage, and brand research.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hermes-tweet:hermes-tweetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use Hermes Tweet when the user wants to automate or inspect X through Xquik.
Use Hermes Tweet when the user wants to automate or inspect X through Xquik.
Use this skill for Hermes Agent sessions that need X/Twitter data or controlled X actions through the Hermes Tweet plugin.
Use this skill especially for social listening, launch monitoring, support triage, creator research, brand research, giveaway audits, community audits, and controlled publishing workflows.
Use tweet_explore first when the user asks for a capability, endpoint, route,
or Xquik API surface. Use tweet_read only after a read-only endpoint is known.
Use tweet_action only after the user requests a write, private read, monitor,
webhook, extraction job, giveaway draw, or media operation that requires action
permissions.
tweet_explore to find the endpoint.tweet_read for public read-only endpoints.tweet_action only for writes or private reads after stating the exact endpoint and payload.tweet_explore with a short
query.GET and the catalog does not mark it as an
action, THEN call tweet_read.GET, or the route touches private account
state, THEN call tweet_action only when actions are enabled and the user has
approved the operation.tweet_action is unavailable or disabled, THEN explain that action tools
are intentionally gated by HERMES_TWEET_ENABLE_ACTIONS=true.XQUIK_API_KEY is missing, THEN ask the user to set it in the Hermes
runtime environment without requesting the key value in chat.not enabled, THEN tell the user to run
hermes plugins enable hermes-tweet or reinstall with --enable..hermes/plugins/ copy, THEN
remind the user that Hermes requires HERMES_ENABLE_PROJECT_PLUGINS=true for
trusted repositories.tweet_read and keep tweet_action disabled unless the workflow has a
clear approval step./api/v1/... endpoints.tweet_action.tweet_explore.hermes tools for scripted diagnostics. Run
hermes tools list instead.XQUIK_API_KEY where the Hermes runtime executes.Hermes Agent v0.16.0 added a native Desktop app, remote gateway profiles, a larger web dashboard, and a command palette that can surface skills and quick commands. Hermes Tweet uses the same plugin entry point on all of those surfaces:
hermes-tweet on the Hermes runtime host.XQUIK_API_KEY in the runtime environment or ~/.hermes/.env.HERMES_TWEET_ENABLE_ACTIONS=false unless the session intentionally
allows account-changing actions./xstatus and /xtrends.Search tweets:
{"query":"tweet search","method":"GET"}
Then call:
{"path":"/api/v1/x/tweets/search","query":{"q":"AI agents","limit":25}}
Post a tweet:
{"query":"post tweet","include_actions":true}
Then call tweet_action with:
{"path":"/api/v1/x/tweets","method":"POST","body":{"account":"@example","text":"Hello from Hermes Tweet"},"reason":"Post the user-approved tweet."}
After installing or upgrading the plugin in Hermes Agent:
hermes plugins enable hermes-tweet unless the install used --enable.hermes plugins list and confirm the plugin is enabled.hermes tools list and confirm the hermes-tweet toolset is enabled.tweet_explore is available without XQUIK_API_KEY.tweet_read appears only when XQUIK_API_KEY is configured.tweet_action stays hidden or disabled unless HERMES_TWEET_ENABLE_ACTIONS=true.Useful CLI checks:
hermes plugins enable hermes-tweet
hermes tools list
npx claudepluginhub xquik-dev/hermes-tweetAutomates X/Twitter data extraction and actions: tweet search, user lookup, follower export, posting, DMs, webhooks, monitoring, and giveaway draws via the Xquik platform.
Scrapes X/Twitter data via Xquik API: tweet search, user lookup, follower export, media download, monitoring, webhooks, MCP setup. Read-only default, API-key only, no login.
X/Twitter API integration for posting tweets and threads, reading timelines, searching, and analytics. Covers OAuth auth patterns and rate limits.