Agent skill · software engineering · github
x-twitter-scraper
Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.
Why this skill is useful
Adds specific integration patterns and commands for using the Xquik X API SDKs and Apify Actors that the AI wouldn't reliably generate on its own.
What it needs
Requires apify installed locally. Requires xquik account access. About 5k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
X Twitter Scraper 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. Use Cases Search tweets, fetch tweet details, read timelines, and download media. Look up users, check relationships, and export followers or following. Start extraction jobs for replies, reposts, quotes, likes, lists, communities, articles, and search results. Create account monitors and verify HMAC-signed webhook events. Add TypeScript, Python, Go, Java, Kotlin, C#, Ruby, PHP, CLI, or Terraform clients. Run hosted tweet and audience collection through Apify Actors. Connect agent runtimes through the Xquik MCP server. Install TweetClaw when the workflow belongs inside OpenClaw and needs plugin-managed approvals for X account actions. Source Checks Before writing code, inspect the current Xquik source material: REST API docs: https://docs.xquik.com/api-reference/overview SDK index: https://docs.xquik.com/sdks OpenAPI spec: https://xquik.com/openapi.json MCP server docs: https://docs.xquik.com/mcp/overview Skill repo: https://github.com/Xquik-dev/x-twitter-scraper TweetClaw OpenClaw plugin: https://github.com/Xquik-dev/tweetclaw TweetClaw npm registry metadata: https://registry.npmjs.org/@xquik%2Ftweetclaw X Tweet Scraper Actor: https://apify.com/xquik/x-tweet-scraper X Follower Scraper Actor: https://apify.com/xquik/x-follower-scraper 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. Implementation Flow 1. Identify the workflow: search, lookup, extraction, monitor, webhook, media, write action, billing, or MCP. 2. Choose the integration surface: generated SDK for application code, REST for custom clients, Apify Actors for hosted collection, MCP for agents, TweetClaw for OpenClaw plugin workflows, or webhooks for event delivery. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/x-twitter-scraper