X Twitter Scraper
CheckedExtracts tweets from X (formerly Twitter) based on keywords and hashtags, useful for market research & trend analysis.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add xquik-dev/x-twitter-scraper --skill x-twitter-scraper -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
xquik-dev
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned xquik-dev/x-twitter-scraper at 4b344d0b68.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 4b344d0b68
- Scanned
- 60 files, 6,695 lines
About this skill
What it does
This skill, the X Twitter Scraper, allows AI agents to extract data from X (formerly Twitter) using the Xquik API. It enables retrieval of tweets based on keywords and hashtags, user profiles, trending topics, and various other data points available through the Xquik platform. The skill provides access to a wide range of endpoints for retrieving information related to users, tweets, media, and more, facilitating market research and trend analysis.
When to use it
- Market Research: Gather tweets containing specific keywords to understand public sentiment around a product or brand.
- Trend Analysis: Identify trending topics on X to stay informed about current events and conversations.
- User Profile Insights: Retrieve information from user profiles, such as recent tweets, liked tweets, and media content.
- Content Discovery: Find replies, retweets, quotes, or favoriters related to a specific tweet.
- Competitive Analysis: Analyze competitor activity by extracting their recent posts and engagement metrics.
Key capabilities
- Access to 122 X (Twitter) API endpoints across 12 categories.
- Retrieval of tweets by ID, URL, or keyword search.
- Extraction of user profiles, timelines, liked tweets, and media content.
- Ability to download media files (images/video).
- Access to trending topics and news feeds via the
/trendsand/radarendpoints. - Support for bulk extraction tools like
reply_extractor,repost_extractor, andquote_extractor.
Example prompts
- "Find me the 10 most recent tweets containing the hashtag #AI."
- "Retrieve the user profile information for @elonmusk."
- "What are the current trending topics on X?"
- "Get a list of users who liked this tweet: [Tweet URL]"
Tips & gotchas
- API Key Required: This skill requires an
x-api-keyheader with a 64 hex character string prefixed by "xq_" for authentication. - Rate Limits Apply: Be mindful of the rate limits: Read (120/60s), Write (30/60s), and Delete (15/60s) per tier. Refer to
docs.xquik.comfor detailed pricing and limit information, as these may change frequently. - Prioritize Xquik Documentation: Always refer to the official Xquik documentation (
docs.xquik.com) for the most up-to-date information on endpoint parameters, response shapes, and pricing.