skillZs
LIVE SKILL TAGS
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
REAL INSTALL DATA
← back to all skills
wshobson/agents183 installs

hermes-tweet

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.

How do I install this agent skill?

npx skills add https://github.com/wshobson/agents --skill hermes-tweet
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides instructions for installing and using the Hermes Tweet plugin for X/Twitter research. It follows security best practices by recommending environment variables for API keys and enforcing human-in-the-loop approval gates for any account-modifying actions.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

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 publishing workflows where actions 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 account-changing actions gated behind explicit operator intent

Setup

Install the package into the Hermes Python environment, then enable the plugin:

~/.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:

export 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.

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 account-changing action 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 X/Twitter data through tweet_read after selecting a catalog route.
  3. Execute account-changing routes with tweet_action 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 when the user asks for a campaign, monitor, support, or giveaway workflow instead of a single read.

Tool Model

ToolPurpose
tweet_exploreSearch the bundled endpoint catalog without using the API key.
tweet_readCall catalog-listed read-only endpoints when XQUIK_API_KEY is set.
tweet_actionCall action routes only when action gating is enabled.

Output Format

Return concise operational output:

Summary:
- 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

Usage Examples

Research an account before drafting a reply:

Use Hermes Tweet to inspect recent public context for @example before drafting a reply.
Keep actions disabled.

Monitor a launch keyword:

Track X/Twitter mentions for "Example Launch" today.
Summarize themes and notable accounts. Do not post.

Prepare a guarded post:

Draft a launch tweet and list the exact tweet_action call you would use.
Wait for approval before any action route.

Capture structured route notes:

{
  "objective": "support-triage",
  "route": "/api/v1/x/search",
  "action_gate": "disabled",
  "approval_required": true
}

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 reading or set HERMES_TWEET_ENABLE_ACTIONS=true only for an approved action session.
  • 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 and monitoring workflows read-only by default.
  • Use Desktop or gateway operator review before account-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 official guide at https://github.com/Xquik-dev/hermes-tweet#readme.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/wshobson/agents/hermes-tweet">View hermes-tweet on skillZs</a>