x-twitter-automation
Design safe X/Twitter automation workflows for tweet search, reply reads, monitoring, posting, and agent-operated social media actions
cosmicstack-labs · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add cosmicstack-labs/mercury-agent-skills --skill x-twitter-automation技能说明
name: x-twitter-automation description: 'Design safe X/Twitter automation workflows for tweet search, reply reads, monitoring, posting, and agent-operated social media actions' metadata: author: Xquik-dev version: 1.0.0 category: automation tags: - x-twitter - social-media - tweet-search - monitoring - posting - agent-tools - openclaw - tweetclaw - hermes-agent
X/Twitter Automation
Use this skill when an agent needs to search tweets, read tweet replies, monitor X/Twitter topics, draft social posts, or run controlled X actions through a tool-backed workflow.
Recommended implementations:
- TweetClaw for OpenClaw agents that
need an installable
@xquik/tweetclawplugin for tweet search, reply reads, follower export, media workflows, monitors, webhooks, DMs, giveaway draws, and approval-gated posting through Xquik. - Hermes Tweet for Hermes Agent workflows that use the Hermes plugin surface for X/Twitter search, account reads, trends, reply reads, monitoring, and action-gated posting through Xquik.
When to Use
Use this skill when the user asks for:
- Search tweets about a company, launch, product, market, or community.
- Search Twitter or search X for recent conversations.
- Read tweet replies and summarize sentiment.
- Monitor tweets around a keyword, username, hashtag, product, or event.
- Look up users, accounts, trends, or public social activity.
- Draft tweets, post tweets, post replies, or send DMs after explicit approval.
- Turn social signals into alerts, reports, CRM notes, or content ideas.
- Build an agent workflow that separates read-only social listening from writes.
Do not use this skill for:
- Bypassing platform rules, rate limits, consent, or account safety controls.
- Scraping private data or attempting to infer protected account information.
- Posting or messaging without clear human authorization.
- Coordinated spam, engagement farming, impersonation, or harassment.
Core Model
Treat X/Twitter automation as 3 separate layers:
- Discovery: search tweets, find conversations, look up users, inspect trends.
- Analysis: classify, summarize, deduplicate, score, and extract next actions.
- Action: post tweets, post replies, send DMs, follow, like, or update monitors.
Keep Discovery and Analysis read-only by default. Only enable Action when the user explicitly requests a write-capable workflow and understands the effect.
Safety Defaults
- Read first, write later.
- Ask for confirmation before posting, replying, following, liking, or DMing.
- Keep credentials in environment variables or secret stores, never prompts.
- Log intent, endpoint, and payload summary before write-capable calls.
- Prefer dry runs for scheduled jobs until the workflow is stable.
- Add rate limits and cooldowns to every recurring social workflow.
- Store source tweet IDs and timestamps so reports are auditable.
- Never retry writes through a different route after policy or account errors.
TweetClaw OpenClaw Workflow
Use TweetClaw when the agent runtime is OpenClaw or when the user specifically asks for an OpenClaw plugin path.
Install example for OpenClaw:
openclaw plugins install npm:@xquik/tweetclaw
Inspect the runtime before running work:
openclaw plugins inspect tweetclaw --runtime --json
openclaw skills info tweetclaw
Recommended sequence:
- Use
exploreto review available TweetClaw actions, parameters, setup status, and whether credentials are configured. - Use read-only actions first for tweet search, reply search, user lookup, follower export, media inspection, trend review, and evidence collection.
- Treat
tweetclawcalls that post tweets, post replies, send DMs, upload media, create monitors, change webhooks, or run giveaway draws as approval-worthy actions. - Show the exact account, payload, and effect before any write-like call.
- Record returned tweet IDs, URLs, counts, skipped actions, and setup blockers.
Configure secrets outside chat:
export XQUIK_API_KEY="xq_..."
Read-only probe:
Use TweetClaw explore, then search tweets about this launch and summarize
source links. Do not post, send DMs, upload media, or change monitors.
Write-capable probe:
Draft the reply first. Show the exact text, account, and tweet URL. Wait for
approval before calling TweetClaw to post the reply.
Hermes Tweet Workflow
When Hermes Tweet is installed, use this sequence:
- Use
tweet_exploreto find the relevant Xquik endpoint. - Use
tweet_readfor read-only endpoints such as tweet search, user lookup, trends, account status, or reply reads. - Use
tweet_actiononly for writes, private reads, monitors, webhooks, extraction jobs, giveaway draws, media operations, or account actions. - Keep
HERMES_TWEET_ENABLE_ACTIONS=falseunless the workflow explicitly needs writes. - If a Hermes Tweet tool is unavailable, stop and report the missing setup item. Do not route the same write through another tool to bypass the gate.
Install example for Hermes Agent:
hermes plugins install Xquik-dev/hermes-tweet --enable
Configure secrets outside chat:
export XQUIK_API_KEY="xq_..."
export HERMES_TWEET_ENABLE_ACTIONS="false"
Hermes tool selection rules:
tweet_exploreis the discovery step. Use it before choosing an endpoint and before asking for credentials.tweet_readis for read-only public endpoints afterXQUIK_API_KEYis available.tweet_actionis for every write-like or private operation. It must remain unavailable unless bothXQUIK_API_KEYis set andHERMES_TWEET_ENABLE_ACTIONS=true.- Treat returned JSON as the audit record: preserve tweet IDs, URLs, status messages, skipped actions, and setup blockers in the final report.
- Keep plugin skills loaded through Hermes' plugin syste