菜单
Uses Xquik from Hermes Agent for X research, monitoring, and approval-gated actions. Use when the user requests X data or an approved X action. Trigger with "search X", "monitor X", "post tweet", or "X trends".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill hermes-tweet命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Implement user sign-up and sign-in flows with Clerk. Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login. Trigger with phrases like "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk. Use when managing user sessions, configuring route protection, or implementing token refresh and custom JWT templates. Trigger with phrases like "clerk session", "clerk middleware", "clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls. Trigger with phrases like "clerk SSO", "clerk RBAC", "clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
| name | hermes-tweet |
| description | Uses Xquik from Hermes Agent for X research, monitoring, and approval-gated actions. Use when the user requests X data or an approved X action. Trigger with "search X", "monitor X", "post tweet", or "X trends". |
| allowed-tools | ["tweet_explore","tweet_read","tweet_action"] |
| version | 0.1.6 |
| author | Burak Bayır (@kriptoburak), Xquik |
| license | MIT |
| compatibility | Requires Hermes Agent plugin support and Xquik API access. |
| argument-hint | [X task, endpoint, or approved action] |
| tags | ["hermes-agent","xquik","twitter","x","social-media","automation"] |
| metadata | {"version":"0.1.6","author":"Xquik","tags":["hermes-agent","xquik","twitter","x","social-media","automation"]} |
| required_environment_variables | [{"name":"XQUIK_API_KEY","prompt":"Xquik API key","help":"Create an API key at https://dashboard.xquik.com","required_for":"tweet_read, /xstatus, /xtrends, and authenticated Xquik API calls"}] |
| capabilities | {"shell":{"required":false,"justification":"Optional Hermes CLI checks are used only for installation and registry diagnostics."},"network":{"required":true,"justification":"Hermes Tweet tools call Xquik API routes for X/Twitter reads and approved actions."},"files":{"required":false,"justification":"Normal use does not require local file reads or writes."},"environment":{"required":true,"variables":["XQUIK_API_KEY","HERMES_TWEET_ENABLE_ACTIONS","HERMES_ENABLE_PROJECT_PLUGINS"],"justification":"Runtime configuration controls authenticated reads, gated actions, and trusted project-local plugin loading."},"mcp":{"required":false,"justification":"No MCP server access is required."},"tools":["tweet_explore","tweet_read","tweet_action"]} |
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.
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.
hermes plugins install Xquik-dev/hermes-tweet --enable.XQUIK_API_KEY on the Hermes runtime host for authenticated reads.
tweet_explore remains available without the key or network access.HERMES_TWEET_ENABLE_ACTIONS unset or false unless the workflow needs
an approved write-like or private operation.HERMES_ENABLE_PROJECT_PLUGINS=true only in a
trusted repository./reload.tweet_explore, tweet_read, and tweet_action only through the enabled
Hermes Tweet toolset.XQUIK_API_KEY, , and
. Never request or echo their values.HERMES_TWEET_ENABLE_ACTIONSHERMES_ENABLE_PROJECT_PLUGINShermes plugins list and confirm tool
registration with hermes tools list.tweet_explore to find the catalog endpoint and method.tweet_read for public read-only endpoints after the API key is
configured.tweet_action, state the exact endpoint, payload, account, reason,
and expected side effects, then get explicit approval.tweet_explore with a short
query.GET and the catalog does not mark it as an
action, THEN call tweet_read.GET, or the route touches private account
state, THEN call tweet_action only when actions are enabled and the user has
approved the operation.tweet_action is unavailable or disabled, THEN explain that action tools
are intentionally gated by HERMES_TWEET_ENABLE_ACTIONS=true.XQUIK_API_KEY is missing, THEN ask the user to set it in the Hermes
runtime environment without requesting the key value in chat.not enabled, THEN tell the user to run
hermes plugins enable hermes-tweet or reinstall with --enable..hermes/plugins/ copy, THEN
remind the user that Hermes requires HERMES_ENABLE_PROJECT_PLUGINS=true for
trusted repositories.tweet_read and keep tweet_action disabled unless the workflow has a
clear approval step./api/v1/... endpoints.tweet_action.tweet_explore, prefer tweet_read, and require a
user-approved endpoint plus payload before tweet_action./api/v1/... paths and reject direct
HTTP fallbacks.HERMES_TWEET_ENABLE_ACTIONS=false by default and summarize
side effects before any account-changing call.tweet_explore has no external side effects, tweet_read
performs authenticated reads, and tweet_action may change account or
workflow state only after explicit approval.Use the narrowest recovery step that preserves the read-first and action-gated contract:
hermes tools list.XQUIK_API_KEY on the runtime host without pasting
its value into chat, then run /reload in an active CLI session or run
hermes gateway restart and start a new gateway session.tweet_explore again. Never guess paths or create a
direct HTTP fallback.HERMES_TWEET_ENABLE_ACTIONS=true is intentionally configured.Example: Search tweets
{"query":"tweet search","method":"GET"}
Then call:
{"path":"/api/v1/x/tweets/search","query":{"q":"AI agents","limit":25}}
Example: Inspect trends
Run /xtrends in an active Hermes session. Use tweet_explore when the task
needs a catalog endpoint or structured response instead of the slash command.
Example: Post a tweet
{"query":"post tweet","include_actions":true}
Then call tweet_action with:
{"path":"/api/v1/x/tweets","method":"POST","body":{"account":"@example","text":"Hello from Hermes Tweet"},"reason":"Post the user-approved tweet."}
After installing or upgrading the plugin in Hermes Agent:
hermes plugins enable hermes-tweet unless the install used --enable.hermes plugins list and confirm the plugin is enabled.hermes tools list and confirm the hermes-tweet toolset is enabled.tweet_explore is available without XQUIK_API_KEY.tweet_read appears only when XQUIK_API_KEY is configured.tweet_action stays hidden or disabled unless HERMES_TWEET_ENABLE_ACTIONS=true.Useful CLI checks:
hermes plugins enable hermes-tweet
hermes tools list
Before presenting this skill as NVIDIA-verified or ready for broad enterprise deployment:
skill-card.md with owner, license, use case, deployment
geography, risks, references, output shape, and release version.BENCHMARK.md for the reviewed release.skill.oms.sig.Do not claim NVIDIA verification when those release artifacts are absent.