Installation

Open Claude Code and run this command:

/plugin install hermes-tweet@claude-code-plugins-plus

Use --global to install for all projects, or --project for current project only.

What It Does

> Xquik is an independent third-party service. Not affiliated with X Corp.

> "Twitter" and "X" are trademarks of X Corp.

![CI](https://github.com/Xquik-dev/hermes-tweet/actions/workflows/ci.yml)

![Docs](https://github.com/Xquik-dev/hermes-tweet#readme)

![Ask DeepWiki](https://deepwiki.com/Xquik-dev/hermes-tweet)

![PyPI](https://pypi.org/project/hermes-tweet/)

![piwheels](https://piwheels.org/project/hermes-tweet/)

![Python](https://pypi.org/project/hermes-tweet/)

![PyPI Status](https://pypi.org/project/hermes-tweet/)

![Wheel](https://pypi.org/project/hermes-tweet/#files)

![Downloads](https://pypi.org/project/hermes-tweet/)

![Release](https://github.com/Xquik-dev/hermes-tweet/releases)

![Apify Actor](https://apify.com/xquik/x-tweet-scraper)

![License: MIT](LICENSE)

Native Hermes Agent plugin for

X automation through Xquik.

Hermes Tweet brings X search, account reads, tweet posting, replies, likes,

retweets, follows, DMs, monitors, webhooks, draws, extraction jobs, media, and

trend reads into Hermes as structured tools.

Use it when you need a Hermes Agent Twitter plugin, Hermes X automation, social

media automation for agents, or a native Hermes toolset for X/Twitter.

Skills (2)

hermes-tweet View full skill →

>-.

tweet_exploretweet_readtweet_action

Hermes Tweet

Name: hermes-tweet
Author: Xquik

Overview

Hermes Tweet solves X research and automation tasks without direct HTTP fallbacks

or guessed endpoints. It discovers catalog-listed Xquik routes, performs

authenticated reads, and keeps write-like or private operations behind an

explicit environment gate and user approval.

Use the skill for read-first workflows. Enable action tooling only for a named

operation whose endpoint, payload, account, and side effects the user approves.

When to Use

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.

Prerequisites

Install and enable the plugin with

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

Configure XQUIKAPIKEY on the Hermes runtime host for authenticated reads.

tweet_explore remains available without the key or network access.

Leave HERMESTWEETENABLE_ACTIONS unset or false unless the workflow needs

an approved write-like or private operation.

For project-local plugins, set HERMESENABLEPROJECT_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 tweetexplore, tweetread, 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

XQUIKAPIKEY, HERMESTWEETENABLE_ACTIONS,

hermes-tweet View full skill →

>-.

tweet_exploretweet_readtweet_action

Hermes Tweet

Overview

Hermes Tweet solves X research and automation tasks without direct HTTP fallbacks

or guessed endpoints. It discovers catalog-listed Xquik routes, performs

authenticated reads, and keeps write-like or private operations behind an

explicit environment gate and user approval.

Use the skill for read-first workflows. Enable action tooling only for a named

operation whose endpoint, payload, account, and side effects the user approves.

When to Use

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.

Prerequisites

Install and enable the plugin with

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

Configure XQUIKAPIKEY on the Hermes runtime host for authenticated reads.

tweet_explore remains available without the key or network access.

Leave HERMESTWEETENABLE_ACTIONS unset or false unless the workflow needs

an approved write-like or private operation.

For project-local plugins, set HERMESENABLEPROJECT_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 tweetexplore, tweetread, 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

XQUIKAPIKEY, HERMESTWEETENABLE_ACTIONS,

hermes-tweet

Installation

What It Does

Skills (2)

Hermes Tweet

Overview

When to Use

Prerequisites

Permissions and Capabilities

Hermes Tweet

Overview

When to Use

Prerequisites

Permissions and Capabilities

Ready to use hermes-tweet?

Related Plugins

hermes-tweet

Installation

What It Does

Skills (2)

Hermes Tweet

Overview

When to Use

Prerequisites

Permissions and Capabilities

Hermes Tweet

Overview

When to Use

Prerequisites

Permissions and Capabilities

Ready to use hermes-tweet?

Related Plugins

fairdb-ops-manager

jeremy-firestore

claude-never-forgets

geepers-agents

sprint

geepers-agents