mcpField
H
hermes-tweet

hermes-tweet

github.com/maystudiosMarketing & growth2643 installsUpdated 11w ago
Repository

About hermes-tweet

hermes-tweet is an X/Twitter workflow plugin for Hermes Agent, for users who need public data or publishing actions. It separates endpoint discovery and read-only access from actions that require explicit configuration.

Key features

  1. 01Discover bundled X/Twitter endpoints
  2. 02Read public, read-only data
  3. 03Draft, schedule, or publish posts
  4. 04Require API key and action enablement

Use cases

  1. 01Find public timelines, profiles, or search data
  2. 02Review analytics data
  3. 03Draft or publish posts after approval

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/maystudios/claude-skills --skill hermes-tweet

After installing, type/hermes-tweetin Claude Code to confirm it loaded.

Details

From the project README

Hermes Tweet

Hermes Tweet is a Hermes Agent plugin for X/Twitter workflows. It keeps endpoint discovery separate from reads and requires explicit configuration before account data or publishing actions are available.

Install

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

Set XQUIK_API_KEY before using read or action tools. Set HERMES_TWEET_ENABLE_ACTIONS=true only for projects where publishing actions are intentionally enabled.

Tool Routes

  • tweet_explore: discover the bundled X/Twitter endpoint catalog without network access.
  • tweet_read: read public, read-only X/Twitter data from a cataloged GET endpoint when XQUIK_API_KEY is configured.
  • tweet_action: run private or action-marked GET endpoints, draft, schedule, or publish only when XQUIK_API_KEY is configured and HERMES_TWEET_ENABLE_ACTIONS=true.

Workflow

  1. Use tweet_explore to find the endpoint that matches the user's request.
  2. Use tweet_read for public timelines, profile reads, search, or analytics.
  3. Use tweet_action for connected-account state, private GET endpoints, action-marked endpoints, or publishing after clear user approval.
  4. Report what was read or drafted without exposing private account state.

Safety

  • Keep all publishing actions explicit and reviewable.
  • Treat private account state as sensitive context.
  • Do not enable tweet_action for unattended projects.
  • Do not store API keys, account data, or drafts in the repository.

Links

Comments

Markdown supported