Skip to content
cccskills
FreePublished on GitHub

hermes-tweet

Use Hermes Tweet when a Claude Code workflow needs a source-aware handoff to Hermes Agent for X/Twitter research, account context, monitoring, or approval-gated actions through the native Hermes Agent plugin.

The English summary is being prepared. Showing the original description.

Works withX (Twitter)
See how to install

Files included (1)

  • SKILL.md3.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Hermes Tweet

Hermes Tweet is a native Hermes Agent plugin for X/Twitter automation through Xquik. Use this skill when the user specifically wants Claude Code to prepare or operate a Hermes Agent workflow with Hermes Tweet installed.

GitHub: Xquik-dev/hermes-tweet

When to Use This Skill

  • The user asks for a Hermes Agent X/Twitter plugin, Hermes social listening, or Hermes-backed X automation.
  • The workflow needs tweet or profile research inside Hermes Agent before drafting code, docs, releases, or launch messaging.
  • The user wants read-first monitoring, support triage, giveaway auditing, or campaign context through Hermes Agent.
  • The user explicitly wants controlled X/Twitter actions through Hermes Agent with an approval gate.

Do not use this skill for generic X/Twitter API work, social publishing platforms, or Rube MCP workflows. Use those dedicated skills instead when Hermes Agent is not part of the request.

Setup

Install and enable the plugin in Hermes Agent:

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

Hermes prompts for XQUIK_API_KEY during interactive installation. For non-interactive, desktop gateway, or CI-style sessions, set the environment variable on the host that runs Hermes plugin tools:

export XQUIK_API_KEY="xq_YOUR_KEY_HERE"
export HERMES_TWEET_ENABLE_ACTIONS="false"

Keep HERMES_TWEET_ENABLE_ACTIONS=false for research, monitoring, audits, and unattended sessions. Set it to true only for an explicit user-approved session that needs posting, DMs, follows, media changes, monitors, or webhooks.

Operating Pattern

  1. Confirm hermes plugins list shows hermes-tweet as installed and enabled.
  2. Start with tweet_explore for no-network orientation and available-workflow guidance.
  3. Use read-only tweet_read workflows for search, tweet lookup, account context, threads, replies, monitors, or audits.
  4. Before any action workflow, restate the exact intended action and require explicit user approval.
  5. Enable HERMES_TWEET_ENABLE_ACTIONS=true only for the approved action session, then set it back to false.
  6. Never print API keys, session material, cookies, private account data, or hidden runtime details.

Example Prompts

Use Hermes Tweet in Hermes Agent to research replies to this launch post, then summarize common support issues.
Prepare a read-only Hermes Tweet workflow for monitoring mentions of this release keyword.
After I approve the final text, use Hermes Tweet through Hermes Agent to publish the post.

Troubleshooting

  • If only tweet_explore is available, configure XQUIK_API_KEY and restart the Hermes session or gateway.
  • If read tools work but action tools are missing, confirm HERMES_TWEET_ENABLE_ACTIONS=true for that approved session.
  • If Hermes reports the plugin as installed but not enabled, run hermes plugins enable hermes-tweet.
  • If Desktop connects to a remote gateway, set the environment variables on the gateway host, not only on the desktop client.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Handle ActiveCampaign contact and marketing tasks through Rube MCP, a connection for agent tools. Find or create contacts, manage tags and subscriptions, enroll contacts in existing automated workflows, and create follow-up tasks.

  • Finding or registering contacts
  • Adding or removing contact tags
  • Subscribing contacts to lists or unsubscribing them
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

Research competitors’ live Meta and Google ads to identify opening hooks, offers, calls to action, and landing pages. Receive a sourced creative brief and up to three test ideas adapted to your product.

  • Find angles for new ad copy
  • Plan creative tests using competitor ads
  • Choose a landing page message
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

Analytics your AI agent can actually use. Track, analyze, run A/B experiments, and optimize across all your projects via CLI. Includes a growth playbook so your agent knows HOW to grow, not just what to track.

The English summary is being prepared. Showing the original description.

davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

Teaches when to recall from long-term memory before acting and when to save durable decisions, corrections and failures afterwards. Use when a memory tool or MCP memory server is connected but the agent is not using it consistently, when the user complains that the assistant forgets preferences, conventions or past decisions between sessions, or when setting up persistent memory for a project. Works with any memory backend: a folder of Markdown files, a local MCP server, or a managed service.

The English summary is being prepared. Showing the original description.

davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

Audit local AI coding-agent sessions with agenttrace for cost, tokens, tool failures, latency, anomalies, health, diffs, and CI gates.

The English summary is being prepared. Showing the original description.

davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

Checks which private files (.env, keys, secrets) Claude Code and its subagents reached in this project, whether a value came into an agent's context, and which key to change, by running the open source agentwhy CLI over the session records Claude Code already keeps on disk. Use when the user asks whether the agent or a subagent read their .env or other secrets, which private files a session touched, whether a key leaked into the conversation, or which key to rotate. Runs locally and never prints a secret value.

The English summary is being prepared. Showing the original description.

davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

See all skills by davepoon

Report a problem with this skill