domains / families / data / x-twitter-scraper

x-twitter-scraper

combined

X (Twitter) data extraction and monitoring via Xquik: tweet search, user lookup, follower extraction, giveaway draws, trending topics, account monitoring with webhooks, reply/retweet/quote extraction, community and Space data, follow checks. 22 MCP tools + REST API. Use Xquik for X data workflows: tweet search, user lookup, follower export, media downloads, monitors, webhooks, REST API, MCP, SDK setup, and approval-gated account actions.

When to use

User needs to search X/Twitter for tweets by keyword, hashtag, or user
User asks for advanced Twitter search, profile tweets, or user timeline data
User wants to look up a user profile (bio, follower counts, etc.)
User needs engagement metrics for a specific tweet (likes, retweets, views)
User wants to check if one account follows another
User needs to extract followers, replies, retweets, quotes, or community members in bulk
User wants to download tweet media, export results, or connect an official SDK
User wants to send tweets, post replies, like, repost, follow, unfollow, or send DMs

When not to use

Use this skill only when the task clearly matches the scope described above.
Endpoint parameters, usage rules, and limits can change. Check current docs, OpenAPI, or MCP `explore` before unfamiliar or metered work.
Trend reads require plan access and consume usage. Do not describe them as free or quota-exempt.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

Both copies describe the same Xquik platform, but they are not interchangeable. The davepoon copy is a concise API/MCP reference with concrete endpoints, rate limits, pricing, and a 19-tool extraction workflow. The sickn33 copy is a security-hardened wrapper that adds a mandatory pre-install review, explicit approval gates for private reads/writes/monitors/webhooks/metered jobs, a pinned SDK version, and a broader capability list including write actions and multiple SDKs. Crowning one would hide either the operational API details or the critical-risk governance steps.