hermes-tweet
Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X/Twitter context. Requires XQUIK_API_KEY for read and action tools.
- License 许可
- MIT
- 最近更新
- 2026-09-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- license
- MIT
- metadata
- { "source": "https://github.com/Xquik-dev/hermes-tweet", "version": "0.1.13", "homepage": "https://github.com/Xquik-dev/hermes-tweet#readme" }
- description
- Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X/Twitter context. Requires XQUIK_API_KEY for read and action tools.
02 资源文件 2
- 参考文档references/endpoint-contract.md1.6 KB
- 参考文档references/workflows.md1.4 KB
03 SKILL.md 正文
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 workflows where private or state-changing operations 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 private and state-changing operations gated behind explicit operator intent
Setup
Install and enable the plugin through Hermes:
hermes plugins install Xquik-dev/hermes-tweet --enable
Hermes scans plugins during installation and updates. Review each warning. A dangerous verdict blocks installation or disables an update.
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 an approved private read, write, monitor, webhook, extraction,
draw, or media operation.
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 private or state-changing operation is in scope
- Confirmation that the Hermes runtime has
XQUIK_API_KEY
Workflow
- Search the bundled endpoint catalog with
tweet_exploreto find matching routes. - Read public X/Twitter data through
tweet_readafter selecting a catalog route. - Use
tweet_actionfor private or state-changing routes only after explicit approval. - Keep API keys in environment variables or the Hermes runtime env file.
- Do not paste credentials into prompts, issues, PR comments, or tool inputs.
- Load workflow patterns when the user asks for a campaign, monitor, support, or giveaway workflow instead of a single read.
Tool Model
| Tool | Purpose |
|---|---|
tweet_explore |
Search the bundled endpoint catalog without using the API key. |
tweet_read |
Call catalog-listed public read-only endpoints when XQUIK_API_KEY is set. |
tweet_action |
Call private reads, writes, monitors, webhooks, extractions, draws, and media operations 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 private or state-changing operations, 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_exploreappears, configureXQUIK_API_KEYon the Hermes runtime host and reload or restart the active Hermes session. - If action routes are unavailable, keep public reads separate. Set
HERMES_TWEET_ENABLE_ACTIONS=trueonly for an approved private or state-changing operation. - If a route does not match, use
tweet_exploreagain 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 read-only by default. Require approval before creating or changing monitors.
- Use Desktop or gateway operator review before private or state-changing calls.
- Validate the exact catalog path before calling
tweet_readortweet_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 endpoint and approval contract when a route boundary is unclear. See the official guide at https://github.com/Xquik-dev/hermes-tweet#readme.
04 同仓库更多 Skills
runpodctl
Runpod CLI for managing GPU/CPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send/receive). Use for terminal/CI/scripting, Hub browse/deploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.
runpod
Start here for any Runpod task — running GPU/CPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.
runpod-usage
How Runpod works and how to work it — pods vs serverless, GPU/VRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv/apt). Use to answer "how does X work", "which GPU", "how do I build a container", or "how do I stand up a workload on a pod". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.
runpod-templates
Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says "run <X> on a pod" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.
runpod-migrate
Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.
runpod-mcp
Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU/CPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.