tweetclaw-twitter-automation
Skill18 starsChanged 9 days agoMITView on GitHub
Guide agents through approved TweetClaw workflows for X/Twitter automation, including tweet scraping, reply search, follower export, user lookup, media, DMs, monitors, webhooks, giveaway draws, and confirmation-gated posts or replies.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ax-extract-workflowSkill
- conversation-json-to-mdSkill
- feature-doc-splitterSkill
- frontend-quality-guardrailsSkill
- git-commit-onlySkill
- git-pushing-fastSkill
- git-push-secondary-merge-primarySkill
- git-stepwise-commitSkill
- git-weekly-reportSkill
- linkedinSkill
- logo-design-boardSkill
- mac-software-storage-cleanupSkill
- multi-lang-readmeSkill
- novel-writerSkill
- react-component-hook-guidelinesSkill
- routerbase-api-integrationSkill
- routerbase-media-generationSkill
- routerbase-model-routingSkill
- topic-bookmarks-reorganizerSkill
- tree-ring-memorySkill
- ui-layout-analyzerSkill
- wechat-theme-extractorSkill
- weixin-article-to-obsidianSkill
- xquik-dataSkill
- x-twitter-scraperSkill
- yuque-lakebook-exportSkill
- ax-extract-workflow-cnSkill
- conversation-json-to-md-cnSkill
- feature-doc-splitter-cnSkill
- frontend-quality-guardrails-cnSkill
- git-commit-only-cnSkill
- git-pushing-fast-cnSkill
- git-push-secondary-merge-primary-cnSkill
- git-stepwise-commit-cnSkill
- git-weekly-report-cnSkill
- linkedin-cnSkill
- logo-design-board-cnSkill
- mac-software-storage-cleanup-cnSkill
- multi-lang-readme-cnSkill
- novel-writer-cnSkill
- react-component-hook-guidelines-cnSkill
- routerbase-api-integration-cnSkill
- routerbase-media-generation-cnSkill
- routerbase-model-routing-cnSkill
- topic-bookmarks-reorganizer-cnSkill
- tree-ring-memory-cnSkill
- tweetclaw-twitter-automation-cnSkill
- ui-layout-analyzer-cnSkill
- wechat-theme-extractor-cnSkill
- weixin-article-to-obsidian-cnSkill
- xquik-data-cnSkill
- x-twitter-scraper-cnSkill
- yuque-lakebook-export-cnSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use TweetClaw when a user asks an agent to work with X/Twitter through Xquik or the TweetClaw OpenClaw plugin.
- Distinctive: line 12
Use this skill when the user asks for:
- Distinctive: line 23
Do not use this skill for:
- Distinctive: line 34
Check current docs before install, configuration, limits, or API details matter:
- Distinctive: line 44
After install or update, verify the runtime before live work:
- Distinctive: line 51
Keep credentials in the Xquik dashboard, OpenClaw plugin config, or environment-backed secret storage.
- Distinctive: line 52
Use TweetClaw discovery or Xquik docs to choose the smallest endpoint and request limit that satisfies the user.
- Distinctive: line 53
Before any visible, state-changing, private, paid, recurring, extraction, monitor, webhook, draw, or account-scoped action, summarize the …
- Distinctive: line 62
Use TweetClaw when the user needs X/Twitter search from an agent.
- Distinctive: line 74
Create a monitor only after the user confirms the account, keyword, or event target.
≈ “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
TweetClaw Twitter Automation
Use TweetClaw when a user asks an agent to work with X/Twitter through Xquik or the TweetClaw OpenClaw plugin.
When to Use
Use this skill when the user asks for:
- Scraping tweets, threads, replies, quotes, mentions, likes, or media
- Searching tweets or tweet replies
- Looking up users, followers, following, or verified followers
- Posting tweets, replying to tweets, or uploading media after approval
- Reading or sending direct messages after account authorization
- Creating monitors, webhooks, or giveaway draws
- Checking which TweetClaw or Xquik endpoint can perform a task
Do not use
Do not use this skill for:
- Spam, harassment, deceptive engagement, impersonation, or platform evasion
- Bulk unsolicited DMs, mass follows, mass likes, mass retweets, or engagement farming
- X ads, analytics dashboards, or scheduling features that TweetClaw does not provide
- Writing actions when only read-only access is configured
- Accessing private or account-scoped data without clear user authorization
- Asking users to paste API keys, signing keys, cookies, or tokens into chat
Instructions
- Restate the user job as one workflow: read, extraction, write, media, DM, monitor, webhook, draw, or discovery.
- Check current docs before install, configuration, limits, or API details matter:
- For OpenClaw installs, prefer the explicit npm selector:
openclaw plugins install npm:@xquik/tweetclaw- After install or update, verify the runtime before live work:
openclaw plugins inspect tweetclaw --runtime --json
openclaw skills info tweetclaw- Keep credentials in the Xquik dashboard, OpenClaw plugin config, or environment-backed secret storage. Never print or echo credential values.
- Use TweetClaw discovery or Xquik docs to choose the smallest endpoint and request limit that satisfies the user.
- Before any visible, state-changing, private, paid, recurring, extraction, monitor, webhook, draw, or account-scoped action, summarize the target, account, action, limits, data handling, and usage impact if available. Wait for explicit confirmation.
- For posting or replying, show the final text and media list before sending. Do not add links, mentions, hashtags, or claims the user did not request.
- For monitors and webhooks, state the target, event types, delivery behavior, and how the user can stop the resource.
- Return concise results with IDs, URLs, counts, and any partial failures.
Common Workflows
Search Tweets
Use TweetClaw when the user needs X/Twitter search from an agent. Keep the query narrow, choose a result limit, and summarize returned tweet IDs, URLs, authors, timestamps, and matched text.
Export Followers
Confirm the account or profile, the requested limit, and whether the user needs raw rows or a summary. Keep private account data scoped to the user's authorization.
Post a Tweet
Show the exact tweet text and attached media. Ask for confirmation before sending. Report the created tweet URL after the action succeeds.
Monitor Activity
Create a monitor only after the user confirms the account, keyword, or event target. Explain what will be watched and how results will be delivered.
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.

