| name | x-twitter-scraper |
| description | Use Xquik for authorized X/Twitter data workflows, including tweet search, profile reads, follower exports, media lookup, monitoring, webhooks, REST API calls, SDK usage, and MCP setup. |
| zh_description | 用于抓取和分析 X/Twitter 公开内容、线程和增长信号。 |
| version | 1.0.0 |
| author | Xquik-dev |
| source | github:Xquik-dev/x-twitter-scraper |
| source_url | https://github.com/Xquik-dev/x-twitter-scraper |
| license | MIT |
| tags | ["growth", "social-media", "twitter", "x", "api", "mcp"] |
| created_at | 2026-06-22 |
| updated_at | 2026-06-22 |
| quality | 4 |
| complexity | intermediate |
X Twitter Scraper
Use this skill when a user needs structured, authorized X/Twitter data through Xquik.
Trigger When
- The user asks to search public X/Twitter posts.
- The user needs profile tweets, replies, quotes, reposts, likes, followers, or following data.
- The workflow needs media download, account monitoring, webhook delivery, or repeatable exports.
- An agent needs a stable REST API, generated SDK, or MCP entry point for X/Twitter workflows.
- A task asks for X/Twitter data as one input in research, OSINT, growth, support, or content operations.
Do Not Use When
- The user asks to bypass platform rules, scrape private data, or impersonate accounts.
- The task requires access to non-public content without authorization.
- The user only needs general copywriting, trend brainstorming, or social strategy with no live X/Twitter data.
- Another project-specific skill already defines the exact X/Twitter data source for that repository.
Setup Checklist
- Read the public setup guide at https://docs.xquik.com.
- Confirm the user has an Xquik API key for REST or MCP usage.
- Store keys only in the local secret store or runtime environment.
- Use the public package and repository as the source of examples: https://github.com/Xquik-dev/x-twitter-scraper.
- Prefer the generated SDK for application code and raw REST only for quick checks.
- For agent integrations, use the documented MCP endpoint and authentication header from the public docs.
Core Workflows
Search and Research
Use Xquik search when the user needs structured post results for a topic, account, URL, keyword, or monitoring seed. Ask for the query, time window, result limit, and output format before making calls.
Return a concise table or JSON summary with:
- post URL or ID
- author handle
- created time
- text excerpt
- engagement fields when returned
- source query
Profile and Network Review
Use profile and network endpoints when the user asks for account-level context. Keep the output task-focused. For example, summarize profile tweets for campaign research, export followers for an authorized audit, or collect replies for support triage.
Do not infer identity, intent, or private attributes from public profile data. Report only what the returned fields support.
Media and Export Jobs
Use media and export workflows when the user asks for durable artifacts. Confirm whether the output should be CSV, JSON, Markdown, or a downstream dataset. Preserve original URLs and IDs so later steps can verify provenance.
