twitter-automation
Skill8 starsChanged 4 months agoMITView on GitHub
Build and run Twitter/X automations end-to-end — the user describes what they want in plain English and this skill designs it, prices it, and wires it up from twitr.sh primitives. Capabilities: post tweets, reply, quote, post with media (images/video/GIF), like, retweet, follow, unfollow, send DMs, delete tweets, download media from any tweet, AI tweet drafting, real-time monitors on accounts or keywords, webhook event delivery to your own endpoint, scheduled posting via agent cron. Use for: social media automation, content scheduling, engagement bots, auto-reply bots, mention alerts, audience growth, X API alternative. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet, twitter dm, follow users, auto-reply bot, reply to mentions automatically, twitter webhook, watch a twitter account, twitter monitoring, engagement bot. No X developer account, no API keys, no OAuth, no signup — the agent's wallet pays per call in USDC (x402 on Base/Solana, MPP on Tempo).
- Sends data out
4 other projects use a version of this.
Adopted by
Most recently taken up by
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- AngelescuCiprian/claude-skillstheir own version, first seen Aug 22, 2026
- nikunj812/claude-skilltheir own version, first seen Jul 1, 2026
- ai4brands-design/claude-skillstheir own version, first seen Mar 22, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- ai4brands-design/claude-skills★ 2same name
- BrightGold70/skills★ 1same name
- AngelescuCiprian/claude-skills★ 0same name
- nikunj812/claude-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- x-presenceSkill
- x-twitter-dataSkill
- x-twitter-monitorSkill
- x-twitter-publishSkill
- x-twitter-researchSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Confirm with the user: before creating a monitor or posting as their account.
- Distinctive: line 48
Use AgentCash MCP — it handles the 402, payment, and retry automatically:
- Very specific: line 67
All writes go to POST /api/tools/x_write with a mandatory Idempotency-Key header and a connected account:
- Distinctive: line 149
Don't create a monitor or post as the user's account without confirming design + cost first.
- Distinctive: line 150
Don't skip the 402 price check — surface any non-trivial cost before signing.
- Very specific: line 151
Don't resend a write after a 202 or a timeout — reuse the same Idempotency-Key.
- Distinctive: line 152
Don't auto-poll events in a loop without the user asking — burns tokens.
- Distinctive: line 153
Don't keep calling after 3 consecutive failures — surface the error and stop.
- Distinctive: line 154
Don't design spam: mass-follow/unfollow churn, unsolicited DM blasts, or reply floods get the user's X account suspended.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Twitter/X Automation
Automate X/Twitter via twitr.sh — no developer account, no API keys, no
OAuth app review. Every paid call is one POST to https://twitr.sh/api/tools/{tool}; the
first call returns HTTP 402 with the exact price, your wallet pays in USDC, the retry runs.
Failed calls are never charged.
How to use this skill — you are the automation builder
The user states an outcome ("reply to anyone who mentions my brand", "post my changelog every morning", "alert me when a competitor tweets"). Your job:
- Design — compose the automation from the recipe table below.
- Price — state the total running cost BEFORE spending: monitor $/day + per-action price (always shown in the 402 before you commit).
- Wire it up — connect account (if writing), create the monitor, register the webhook or plan the polling, then run the action loop.
- Confirm with the user before creating a monitor or posting as their account. Always.
Recipe table — intent → wiring
| User wants | Wiring | Running cost |
| Auto-reply to mentions | connect account → x_monitor on "query": "@handle" → webhook tweet.mention → x_compose draft → x_write reply | ~$0.61/day + ~$0.04/reply |
| Scheduled posting / "tweet daily" | agent-side cron (Claude Code routine, OpenClaw cron) → x_compose → x_write post | ~$0.037/post |
| Watch an account or topic, get alerted | x_monitor (account or keyword) → poll events free, or webhook to your endpoint | ~$0.61/day |
| Repost / mirror media | x_read download-media → x_write upload_media → x_write post with media_ids | ~$0.05/post |
| Engagement (like/retweet/follow on a topic) | x_monitor keyword → x_write like / retweet / follow | ~$0.61/day + ~$0.012/action |
| DM new engagers | x_timeline engagement lists or monitor events → x_write send_dm | per item + ~$0.036/DM |
| One-off post / reply / thread | x_compose → x_write | ~$0.037 |
Automations that publish or engage should stay useful, not spammy — X suspends accounts for aggressive follow/like churn and unsolicited DM blasts. Keep volumes human-scale and tell the user when a design risks their account.
Quick start
Use AgentCash MCP — it handles the 402, payment, and retry automatically:
mcp__agentcash__fetch({
url: "https://twitr.sh/api/tools/x_write",
method: "POST",
headers: { "Idempotency-Key": "<uuid>" },
body: { "action": "post", "account": "myhandle", "text": "Hello from my agent 🤖" }
})AgentCash surfaces the 402 body BEFORE signing — read amount and confirm with the user when
the price is non-trivial (~$0.10+).
Without AgentCash: any x402/MPP client works. Discovery: https://twitr.sh/openapi.json,
/.well-known/x402, /.well-known/mpp.json.
Actions
All writes go to POST /api/tools/x_write with a mandatory Idempotency-Key header and a
connected account:
| Action | Input | Price |
post | text (+ optional media_ids) | ~$0.036 |
reply | text + reply_to_tweet_id | ~$0.036 |
like / unlike | target_tweet_id | ~$0.012 |
retweet / unretweet | target_tweet_id | ~$0.012 |
follow / unfollow | target_user_id (numeric — get it from x_read get-user) | ~$0.012 |
send_dm | target_user_id + text | ~$0.036 |
delete_tweet | target_tweet_id | ~$0.012 |
remove_follower | target_user_id | ~$0.012 |
upload_media | media_url (public URL) → returns media_id | ~$0.012 |
Reads that pair with automation:
| Tool | What |
x_read | Get a tweet, profile, batch (≤100), or download-media from a tweet (returns download URLs) |
x_compose | AI drafting: generate → refine → score tweet text (~$0.001, posts nothing) |
x_search / x_timeline | Search tweets/users, timelines, engagement lists (resultsLimit required, billed per item) |
A 202 {"status":"pending_confirmation","action_id":"..."} means the write was accepted and
is being applied — do NOT resend (it's already paid). Retrying with the same
Idempotency-Key replays the original result instead of double-posting.
Connect an X account (one-time, free)
Never ask the user for their X password, email, or 2FA secret — never accept one if offered. The connect flow keeps credentials out of your context entirely:
POST /api/x-accounts/start{ "username": "myhandle" }→{connect_url, expires_in}.- Show the user
connect_url: open this in your browser and sign in to X there. The link is single-use and expires in 15 minutes. - Poll
GET /api/x-accounts(free, SIWX) until the handle showslinked.
One X handle belongs to exactly ONE wallet; ownership is re-checked server-side on every
write. Disconnect: DELETE /api/x-accounts/{handle}.
Real-time triggers — monitors + webhooks
Monitors are prepaid by the hour (~$0.025/hr, 24h ≈ $0.61; max 168h per purchase). They stop
at expires_at unless extended; early deletion does not refund. Pay on Base (x402) or Tempo
(MPP) — Solana is not offered for monitors. Idempotency-Key required on create.
POST /api/tools/x_monitor { "action": "create", "username": "vercel", "hours": 24 }
POST /api/tools/x_monitor { "action": "create", "query": "\"launch week\"", "hours": 24 }
POST /api/tools/x_monitor { "action": "extend", "monitorId": "mn_...", "hours": 48 }Event types: tweet.new, tweet.reply, tweet.retweet, tweet.quote, tweet.media,
tweet.link, tweet.mention, tweet.hashtag, tweet.longform, and (account monitors)
profile.*.changed. A terminal monitor.expired / monitor.deleted event always fires.
Poll (free, SIWX): GET /api/monitors/{id}/events?after={last_event_id}&limit=50 —
strictly newer events, oldest→newest. Poll at most 1/s, ideally only when the user asks.
Push (webhooks — free, SIWX, max 3 per wallet):
POST /api/webhooks { "url": "https://your-agent.example.com/hooks", "eventTypes": ["tweet.mention"] }The 201 response contains the signing secret exactly once — store it. Verify every
delivery: sha256=HMAC-SHA256(secret, "{X-Twitr-Timestamp}.{rawBody}") against
X-Twitr-Signature, reject timestamps older than 5 minutes, dedupe on delivery_id.
Respond 2xx within 10s; retries back off over ~36 min.
Worked example — auto-reply agent in 4 calls
- Connect (free):
/api/x-accounts/start→ user opens link →linked. - Monitor:
x_monitorcreate on"query": "@myhandle", 24h (~$0.61). - Listen:
POST /api/webhooksfor["tweet.mention"]— or poll events when asked. - React: on each event,
x_composea draft ($0.001), show the user, then$0.036).x_write{action:"reply", account, reply_to_tweet_id, text}(
Total: ~$0.61/day + ~$0.04 per reply.
Don't do
- Don't create a monitor or post as the user's account without confirming design + cost first.
- Don't skip the 402 price check — surface any non-trivial cost before signing.
- Don't resend a write after a 202 or a timeout — reuse the same
Idempotency-Key. - Don't auto-poll events in a loop without the user asking — burns tokens.
- Don't keep calling after 3 consecutive failures — surface the error and stop.
- Don't design spam: mass-follow/unfollow churn, unsolicited DM blasts, or reply floods get the user's X account suspended.
Related skills
npx skills add lnvestor/twitr-skillsx-twitter-data— live reads, search, timelines, trendsx-twitter-research— bulk exports as downloadable datasetsx-twitter-monitor— deep dive on monitors, events, and webhook verificationx-twitter-publish— deep dive on drafting and publishingx-presence— unattended posting + monitoring routine for cron
Documentation
- Agent guide:
https://twitr.sh/llms.txt - OpenAPI + payment discovery:
https://twitr.sh/openapi.json - Dashboard (browser):
https://twitr.sh/dashboard
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

