Use this skill when a user wants to integrate Xquik into an app, script, data pipeline, or AI agent workflow for X API and Twitter scraper tasks.
Before writing code, inspect the current Xquik source material:
Do not invent endpoint names, request fields, response fields, scopes, pricing, limits, or package names. Read the relevant SDK README and API reference page first.
When application code is involved, match the SDK to the user's project language:
Use project-native typed request and response models. Keep network calls in server-side code unless the SDK docs explicitly support browser use.
Use the Apify path when a workflow needs hosted runs, datasets, schedules, or Apify-native orchestration.
| Need | Actor | REST ID |
|---|---|---|
| Tweets, search, timelines, lists, articles, replies, quotes, threads, retweeters, or best-effort favoriters | xquik/x-tweet-scraper |
xquik~x-tweet-scraper |
| Followers, following, verified followers, list members, list subscribers, or community members | xquik/x-follower-scraper |
xquik~x-follower-scraper |
Authenticate with an Apify API token. Keep it in APIFY_API_TOKEN. Fetch the current input schema from the relevant Actor page before selecting fields.
Start a bounded tweet run:
curl --fail --silent --show-error --request POST \
"https://api.apify.com/v2/actors/xquik~x-tweet-scraper/runs" \
--header "Authorization: Bearer ${APIFY_API_TOKEN}" \
--header "Content-Type: application/json" \
--data '{"twitterHandles":["apify"],"outputVariant":"rich","maxItems":25}'
Start a bounded follower run:
curl --fail --silent --show-error --request POST \
"https://api.apify.com/v2/actors/xquik~x-follower-scraper/runs" \
--header "Authorization: Bearer ${APIFY_API_TOKEN}" \
--header "Content-Type: application/json" \
--data '{"twitterHandles":["apify"],"relation":"followers","outputMode":"compact","maxItems":50}'
Record the returned run ID. Poll the Actor run with a bounded retry loop. Stop on SUCCEEDED, FAILED, ABORTED, or TIMED-OUT. On success, read defaultDatasetId, then fetch its dataset items.
Treat maxItems as the cap for the entire tweet run, including runs with several search terms. Keep follower target metadata when attribution matters. Treat rows with resultType: "diagnostic" as status information, not scraped records. Inspect any run-report row before trusting an incomplete result.
Review each Actor's live Apify pricing box before every paid run. Apify platform usage may apply separately. Start with a small maxItems value and ask before raising the cap.
When adding webhook handlers:
Use the MCP server when the user wants an agent to explore or call Xquik tools directly. Keep application code on REST or SDK clients when the app needs stable typed contracts, tests, or internal abstractions.
Use TweetClaw when the user is working in OpenClaw, wants installable plugin metadata, or needs an approval-reviewed path for account-changing X actions. Keep application services on REST or SDK clients when the project needs typed contracts, server-side abstractions, or long-lived backend jobs outside OpenClaw.
Before suggesting install commands or tool names, read the TweetClaw README and package metadata. Do not assume the published npm version matches source HEAD.
Treat create, reply, quote, like, bookmark, retweet, follow, delete, media, and monitor actions as approval-worthy unless the current TweetClaw docs state a narrower policy. Keep read-only tweet search, reply search, profile lookup, follower export, and evidence collection low risk, while still respecting rate limits and account authorization.
Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.