> 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.
npx skills add https://github.com/wshobson/agents --skill 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.
Use this skill when the user wants to:
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.
Ask for these inputs before selecting routes:
XQUIK_API_KEYtweet_explore to find matching routes.tweet_read after selecting a catalog route.tweet_action only after explicit approval.campaign, monitor, support, or giveaway workflow instead of a single read.
| Tool | Purpose |
| --- | --- |
| tweet_explore | Search the bundled endpoint catalog without using the API key. |
| tweet_read | Call catalog-listed read-only endpoints when XQUIK_API_KEY is set. |
| tweet_action | Call action routes only when action gating is enabled. |
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
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
}
tweet_explore appears, configure XQUIK_API_KEY on the Hermes runtimehost and reload or restart the active Hermes session.
HERMES_TWEET_ENABLE_ACTIONS=true only for an approved action session.
tweet_explore again and choose a catalog-listedpath instead of guessing endpoints.
tweet_read or tweet_action.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.
Skill converted from mcp-deploy-manage-agents.prompt.md
Use this skill when the user wants to launch a new AltClaw, OpenClaw, PicoClaw, or Ottie deployment through Cloud Claw. Covers the same user-facing fields and constraints exposed in the Cloud Claw UI, using the local altllm cloud-claw-* commands. Do NOT use for post-launch lifecycle tasks like start/stop/delete/logs; use cloud-claw-manage-vm.
Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition. Use when creating container-based agents in Azure AI Foundry.
Build MCP (Model Context Protocol) servers on Cloudflare Workers with tools, resources, and prompts.
Chain agent outputs as inputs in sequential or parallel pipelines for data flow orchestration
Audit cloned or reimplemented websites for fidelity gaps, tracking scripts, source-brand and language residue, placeholders, and risky external dependencies. Use before handoff or deployment, or when asked to review a website clone for cleanup and readiness.
Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and continuous monitoring. Use when the user mentions create evaluator, LLM judge, hallucination, faithfulness, correctness, relevance, run eval, score spans, score experiment, trigger-run, column mapping, continuous monitoring, or improve evaluator prompt.
This skill should be used when the user wants to build an "MCP app", add "interactive UI" or "widgets" to an MCP server, "render components in chat", build "MCP UI resources", make a tool that shows a "form", "picker", "dashboard" or "confirmation dialog" inline in the conversation, or mentions "apps SDK" in the context of MCP. Use AFTER the build-mcp-server skill has settled the deployment model, or when the user already knows they want UI widgets.
Take wshobson/hermes-tweet from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference pip.
Without those the skill loads but fails at the first command.