hermes-tweet

name	hermes-tweet
description	Search Twitter/X, read replies, find users, monitor accounts, export followers & gate X actions through Xquik. Not affiliated with X Corp.
version	0.1.13
author	Xquik
license	MIT
tags	["hermes-agent","xquik","twitter","x","social-media","automation"]
metadata	{"version":"0.1.13","author":"Xquik","repository":"https://github.com/Xquik-dev/hermes-tweet","plugin":"hermes plugins install Xquik-dev/hermes-tweet --enable"}
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

Use this ASK-compatible wrapper when a Hermes Agent user needs the native Hermes Tweet plugin for X/Twitter automation through Xquik.

Install

Install the native plugin in Hermes Agent:

hermes plugins install Xquik-dev/hermes-tweet --enable
hermes tools list

Review Hermes security-scan warnings. Dangerous plugins are blocked.

Set XQUIK_API_KEY in the Hermes runtime environment before using authenticated read or action tools. Do not paste the key into chat.

When to use Hermes Tweet

Use Hermes Tweet for:

• Search tweets or Twitter/X.
• Read tweet replies and details.
• Find users and public profiles.
• Monitor tweets or accounts.
• Export followers and following lists.
• Post, reply, send DMs, or automate X after explicit approval.

Choose a tool

1. Use tweet_explore to find the catalog endpoint.
2. Use tweet_read for public read-only endpoints.
3. Use tweet_action only for approved writes, private reads, monitors, webhooks, extraction jobs, giveaway draws, or media operations.

Safety

• Never ask for API keys, passwords, cookies, or TOTP secrets.
• Never pass credentials in tool arguments.
• Use only catalog-listed /api/v1/... endpoints.
• Copied endpoint URLs are accepted only when they resolve to catalog-listed paths.
• Keep write actions gated behind HERMES_TWEET_ENABLE_ACTIONS=true.
• Summarize the exact action before posting, replying, sending DMs, or changing account state.

Permissions and trust

• Tools. Use only tweet_explore, tweet_read, and tweet_action through the enabled Hermes Tweet toolset.
• Network. Call only catalog-listed Xquik API routes through those tools. Do not create direct HTTP fallbacks.
• Files. Do not write files, logs, screenshots, cached payloads, or credentials unless the user asks for an explicit export workflow.
• Environment. Check only whether XQUIK_API_KEY, HERMES_TWEET_ENABLE_ACTIONS, and HERMES_ENABLE_PROJECT_PLUGINS are configured. Never request or echo values.