| name | hermes-tweet |
| description | Use Xquik in Hermes Agent for public X research, monitoring, thread summaries, creator discovery & approved actions. Not affiliated with X Corp. Use when the user requests X data or a named action. Trigger with "search X", "monitor X", "post tweet", or "X trends". |
| allowed-tools | ["tweet_explore","tweet_read","tweet_action"] |
| version | 0.1.13 |
| author | Burak Bayır (@kriptoburak), Xquik |
| license | MIT |
| compatibility | Requires Hermes Agent plugin support and Xquik API access. |
| argument-hint | [X task, endpoint, or approved action] |
| repo | https://github.com/Xquik-dev/hermes-tweet |
| homepage | https://github.com/Xquik-dev/hermes-tweet#readme |
| commit | c6ebdd7060965dd16a89e8cc12675ff834b5cc94 |
| languages | ["en"] |
| tags | ["hermes-agent","xquik","twitter","x","social-media","automation"] |
| metadata | {"version":"0.1.13","author":"Xquik","tags":["hermes-agent","xquik","twitter","x","social-media","automation"]} |
| required_environment_variables | [{"name":"XQUIK_API_KEY","prompt":"Xquik API key","help":"Create an API key at https://dashboard.xquik.com","required_for":"tweet_read, /xstatus, /xtrends, and authenticated Xquik API calls"}] |
| capabilities | {"shell":{"required":false,"justification":"Optional Hermes CLI checks are used only for installation and registry diagnostics."},"network":{"required":true,"justification":"Hermes Tweet tools call Xquik API routes for X/Twitter reads and approved actions."},"files":{"required":false,"justification":"Normal use does not require local file reads or writes."},"environment":{"required":true,"variables":["XQUIK_API_KEY","HERMES_TWEET_ENABLE_ACTIONS","HERMES_ENABLE_PROJECT_PLUGINS"],"justification":"Runtime configuration controls authenticated reads, gated actions, and trusted project-local plugin loading."},"mcp":{"required":false,"justification":"No MCP server access is required."},"tools":["tweet_explore","tweet_read","tweet_action"]} |
Hermes Tweet
Overview
Discover catalog-listed Xquik routes and run authenticated reads without guessed endpoints.
Private or state-changing operations require the action gate and user approval.
Enable tweet_action only after the user approves its endpoint, payload, account, and effects.
When to use Hermes Tweet
Use this Skill for X/Twitter research, social listening, monitoring, support triage,
creator research, giveaway audits, community audits, and controlled publishing.
Use tweet_explore first when the user asks for a capability, endpoint, route,
or Xquik API route. 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.
Prerequisites
- Install and enable the plugin with
hermes plugins install Xquik-dev/hermes-tweet --enable.
- Review Hermes security-scan warnings. Dangerous plugins are blocked.
- Configure
XQUIK_API_KEY on the Hermes runtime host for authenticated reads.
tweet_explore remains available without the key or network access.
- Leave
HERMES_TWEET_ENABLE_ACTIONS unset or false unless the workflow needs
an approved write-like or private operation.
- For project-local plugins, set
HERMES_ENABLE_PROJECT_PLUGINS=true only in a
trusted repository.
- Restart a gateway after environment changes and start a new session. Active
CLI sessions can use
/reload.
Permissions and capabilities
- Use
tweet_explore, tweet_read, and tweet_action only through the enabled
Hermes Tweet toolset.
- Network access is limited to catalog-listed Xquik API routes reached by those
tools. Do not create direct HTTP fallbacks.
- Shell access is not part of normal operation. Use Hermes CLI commands only for
the install and registry checks listed in Testing.
- Local file access is not part of normal operation. Do not write reports,
credentials, logs, screenshots, or cached API payloads unless the user asks
for an explicit export workflow.
- Environment access is limited to configuration presence checks for
XQUIK_API_KEY, HERMES_TWEET_ENABLE_ACTIONS, and
HERMES_ENABLE_PROJECT_PLUGINS. Never request or echo their values.
- MCP access is not required.
