Hermes Tweet Hermes Agent X/Twitter Skill
Safety-reviewed Agent Skill for Hermes Tweet, the Hermes Agent plugin for X/Twitter endpoint discovery, credentialed reads, and approval-gated actions through Xquik.
Open the source and read safety notes before installing.
Citation facts
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
- Source URLs
- https://github.com/Xquik-dev/hermes-tweet#readme, https://github.com/Xquik-dev/hermes-tweet
- Safety notes
- Start with `tweet_explore` for credential-free planning before using credentialed tools., Treat `tweet_action` as approval-gated and review exact endpoint, method, and payload before any public or account-changing action., Do not use Hermes Tweet for spam, deceptive engagement, harassment, impersonation, credential collection, or bulk unsolicited outreach.
- Privacy notes
- Xquik API keys must stay in plugin config or environment variables, never in prompts, shared logs, issues, PRs, screenshots, or committed files., Credentialed reads can expose account-scoped timelines, searches, user data, or workflow context., Return concise summaries and source URLs without exposing raw private runtime logs or credentials.
- Platform compatibility
- claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
- Author
- Xquik-dev
- Submitted by
- kriptoburak
- Claim status
- unclaimed
- Last verified
- 2026-06-21
Safety notes
- Start with `tweet_explore` for credential-free planning before using credentialed tools.
- Treat `tweet_action` as approval-gated and review exact endpoint, method, and payload before any public or account-changing action.
- Do not use Hermes Tweet for spam, deceptive engagement, harassment, impersonation, credential collection, or bulk unsolicited outreach.
Privacy notes
- Xquik API keys must stay in plugin config or environment variables, never in prompts, shared logs, issues, PRs, screenshots, or committed files.
- Credentialed reads can expose account-scoped timelines, searches, user data, or workflow context.
- Return concise summaries and source URLs without exposing raw private runtime logs or credentials.
Prerequisites
- Hermes Agent with plugin support
- Xquik API key before using account-backed reads
- Agent client with Agent Skills support for `npx skills add`
- `HERMES_TWEET_ENABLE_ACTIONS=true` plus explicit user approval before posts, follows, likes, reposts, deletes, or other account-changing actions
Schema details
- Install type
- package
- Reading time
- 4 min
- Difficulty score
- 62
- Troubleshooting
- Yes
- Breaking changes
- No
- Scope
- Source repo
- Skill type
- general
- Skill level
- advanced
- Verification
- validated
- Verified at
- 2026-06-21
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
Full copyable content
# Trigger
"Use Hermes Tweet to plan a safe Hermes Agent X/Twitter workflow."
# Skill install
npx skills add xquik-dev/hermes-tweet
# Plugin source
https://github.com/Xquik-dev/hermes-tweet
# Required gates
XQUIK_API_KEY for credentialed reads
HERMES_TWEET_ENABLE_ACTIONS=true for account-changing actionsAbout this resource
Overview
Hermes Tweet is an Agent Skill bundled with the Hermes Agent X/Twitter plugin. It helps agents use Xquik safely by separating endpoint discovery, authenticated reads, and account-changing actions behind explicit tool gates.
Use the skill when a Hermes Agent workflow needs to find the right X/Twitter endpoint, read tweets or profiles with an API key, or prepare posts and other workflow actions for approval before execution.
Install
Install the reusable Agent Skill:
npx skills add xquik-dev/hermes-tweet
Use the canonical repository as the Hermes Agent plugin source:
https://github.com/Xquik-dev/hermes-tweet
After plugin install, verify that Hermes Agent lists the Hermes Tweet toolset and exposes tweet_explore, tweet_read, and tweet_action according to the configured environment gates.
Workflow Scope
- Use
tweet_explorefirst to inspect available Xquik endpoints without credentials. - Configure
XQUIK_API_KEYbefore account-backed reads. - Keep
HERMES_TWEET_ENABLE_ACTIONSdisabled unless the session intentionally allows account-changing actions. - Use
tweet_readfor catalog-listed GET endpoints that do not change account or workflow state. - Use
tweet_actiononly after the user approves the exact endpoint, method, payload, and expected side effects.
Safety Checklist
- Confirm the user owns or is authorized to access the account or workflow.
- Keep API keys out of chat, logs, screenshots, issues, PRs, and commits.
- Start with endpoint discovery before credentialed reads or actions.
- Show final post text, media choices, targets, and scheduling details before publishing.
- Re-confirm when scope, account, target, recurrence, or limits change.
Troubleshooting
- If
tweet_readis unavailable, configureXQUIK_API_KEYwhere the Hermes runtime executes. - If
tweet_actionis unavailable, setHERMES_TWEET_ENABLE_ACTIONS=trueonly for sessions that need approved actions. - If a route is not returned by
tweet_explore, do not guess it or call a direct HTTP fallback. - If the plugin is installed in a project-local Hermes directory, enable trusted project plugins only for repositories you trust.
Retrieval Sources
Source citations
Add this badge to your README
Show that Hermes Tweet Hermes Agent X/Twitter Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/hermes-tweet-hermes-agent-x-twitter)How it compares
Hermes Tweet Hermes Agent X/Twitter Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Safety-reviewed Agent Skill for Hermes Tweet, the Hermes Agent plugin for X/Twitter endpoint discovery, credentialed reads, and approval-gated actions through Xquik. Open dossier | Safety-reviewed Agent Skill for using TweetClaw, the OpenClaw plugin for X and Twitter search, posting, follower export, media workflows, monitors, webhooks, and giveaway draws through Xquik. Open dossier | MIT-licensed Agent Skills collection for context engineering, harness engineering, multi-agent architectures, filesystem context, memory systems, tool design, evaluation, hosted agents, and production agent operating loops for Claude Code, Cursor, Codex, and Open Plugins-compatible agent tools. Open dossier | Microsoft .NET team skill marketplace for AI coding agents working on .NET, C#, ASP.NET Core, Blazor, MAUI, diagnostics, MSBuild, NuGet, upgrades, tests, AI workflows, RAG pipelines, and C# MCP servers. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | |
| Category | skills | skills | skills | skills |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Xquik-dev | Xquik-dev | Muratcan Koylan | .NET Team at Microsoft |
| Added | 2026-06-21 | 2026-06-09 | 2026-06-18 | 2026-06-18 |
| Platforms | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLIVS Code |
| Source repo | — | — | — | — |
| Safety notes | ✓Start with `tweet_explore` for credential-free planning before using credentialed tools. Treat `tweet_action` as approval-gated and review exact endpoint, method, and payload before any public or account-changing action. Do not use Hermes Tweet for spam, deceptive engagement, harassment, impersonation, credential collection, or bulk unsolicited outreach. | ✓TweetClaw can perform public X account actions after OpenClaw tool opt-in and approval; review exact posts, replies, DMs, follows, media, monitors, webhooks, and draws before allowing a call. Keep `tweetclaw` as an optional OpenClaw tool and start with read-only `explore` until the user confirms the workflow. Do not use TweetClaw for spam, deceptive engagement, harassment, credential collection, impersonation, or bulk unsolicited outreach. | ✓These skills alter how agents select context, delegate work, persist state, design tools, evaluate outputs, and operate autonomous loops; use them as engineering guidance, not as automatic authority to change a production agent system. Filesystem-context and memory-system patterns can cause agents to write durable plans, scratchpads, logs, summaries, preferences, or shared handoff files. Keep cleanup, ownership, and review rules explicit. Harness-engineering, hosted-agent, and evaluation workflows can launch long-running loops, background agents, benchmark suites, paid model calls, or remote sandbox work. Require budgets, kill switches, rollback rules, and approval gates. Tool-design guidance can change MCP schemas, tool descriptions, return formats, and error contracts. Test routing and compatibility before deploying changes to users. Benchmark results are source evidence for this repository's claims, but they are workload-specific. Re-run or adapt benchmarks before relying on the reported routing numbers in a different agent stack. | ✓.NET build, test, upgrade, package, template, publish, and migration tasks can modify project files, lock files, generated code, packages, app settings, and deployment artifacts. Diagnostics skills may suggest collecting traces, dumps, counters, crash data, MSBuild binlogs, or performance profiles; collect those artifacts only with explicit approval and storage controls. MCP server skills can expose local code, files, APIs, credentials, or production services as callable tools; review tool descriptions, parameter validation, authorization, and transport choice before connecting clients. NuGet and publish workflows can push packages or artifacts to public or private feeds; verify package IDs, versions, API keys, feed targets, and release policy before publishing. Upgrade and modernization guidance should be verified against each application's framework support window, deployment target, package compatibility, and rollback plan. |
| Privacy notes | ✓Xquik API keys must stay in plugin config or environment variables, never in prompts, shared logs, issues, PRs, screenshots, or committed files. Credentialed reads can expose account-scoped timelines, searches, user data, or workflow context. Return concise summaries and source URLs without exposing raw private runtime logs or credentials. | ✓Xquik API keys and MPP signing keys must stay in OpenClaw plugin config or environment variables, never in prompts, shared logs, PRs, or committed files. Tweet searches, timelines, DMs, bookmarks, follower exports, media metadata, monitors, webhook details, and account usage can expose private or account-scoped data. Use the Xquik dashboard and public docs for current billing, account, and data-handling details. | ✓Context-engineering work often touches prompts, system instructions, tool definitions, retrieved documents, message history, tool outputs, logs, scratch files, memory stores, benchmark prompts, and model responses. Do not persist secrets, customer data, private source code, incident data, unpublished strategy, or regulated records into scratchpads, skill examples, benchmark fixtures, or shared agent workspaces. If benchmark runners or hosted-agent examples call external models or remote sandboxes, review what prompts, traces, files, and logs are sent outside the local workspace. Agent memory and filesystem-context patterns should include deletion, redaction, retention, and access-control rules before being used with private projects. | ✓.NET repositories may contain connection strings, appsettings secrets, user secrets, certificates, environment variables, telemetry keys, logs, traces, dumps, package credentials, and production data. MSBuild binlogs, crash dumps, profiler output, and test artifacts can contain source paths, dependency graphs, request data, exception payloads, configuration values, and environment details. MCP servers created with these skills may forward prompts and tool inputs to local processes, HTTP services, databases, cloud APIs, or third-party model providers depending on the implementation. Keep private NuGet credentials, signing keys, deployment secrets, customer data, dumps, and proprietary source out of public prompts, issues, pull requests, and shared artifacts. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Related guides
Source-backed guides for putting this to work.
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.