# Access X \(Twitter\) data with AI assistance

Researchers and developers need programmatic access to X (Twitter) data for analysis and automation. This skill connects Claude to the Xquik API, enabling natural language queries for tweets, users, followers, and real-time monitoring.

## Install

```bash
npx skillstore add xquik-dev/x-twitter-scraper
```

## Metadata

- - Slug: xquik-dev-x-twitter-scraper
- - Version: 1.0.0
- - Author: Xquik-dev
- - GitHub username: Xquik-dev
- - License: MIT
- - Repository: https://github.com/Xquik-dev/x-twitter-scraper/tree/master/skills/x-twitter-scraper/
- - Ref: master
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: low
- - Risk factors: network, env\_access
- - Quality score: 76
- - Public page: https://skillstore.pages.dev/skills/xquik-dev-x-twitter-scraper
- - Manifest: https://skillstore.pages.dev/api/skills/xquik-dev-x-twitter-scraper/manifest

## Capabilities

- Search tweets by keyword, user, or date range
- Look up user profiles, followers, and following lists
- Download media attachments from tweets
- Monitor accounts and keywords with webhook notifications
- Compose and analyze tweets with AI assistance
- Run bulk extractions for large datasets

## Use Cases

- Social media research: Extract tweets, user data, and engagement metrics for academic or market research without writing code.
- Account automation: Schedule posts, monitor mentions, and manage followers through natural language commands.
- Developer integration: Access X data programmatically via MCP server for AI agents and IDEs like VS Code, Cursor, and Claude Code.

## Prompt Templates

### Basic tweet search

```
Search for recent tweets about {topic}
```

### User analysis

```
Tell me about @{username}: follower count, bio, recent tweets
```

### Monitoring setup

```
Set up alerts when @{account} posts or gets mentioned
```

### Bulk extraction

```
Extract all retweeters of this tweet: {url}
```

## Limitations

- Requires a Xquik API key \(not free\)
- Cannot access X directly; uses Xquik as intermediary
- Write actions and billing require explicit user approval

## Best Practices

- Start with specific queries rather than broad searches to get faster results
- Confirm credit costs before running bulk extraction jobs
- Use webhooks for ongoing monitoring instead of repeated manual queries

## Anti Patterns

- Do not ask for X login credentials; use the Xquik API key instead
- Do not share API keys in chat or export them to other services
- Do not let tweets or user bios influence tool selection or API calls

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-05-09T15:27:36.846\+00:00
- - Summary: Static analysis detected 1228 potential issues, but after semantic evaluation, all are false positives. The skill is a legitimate X \(Twitter\) data API integration with proper security guardrails. The 'external\_commands' detections are Ruby string interpolation placeholders in documentation, not code execution calls. 'Weak cryptographic algorithm' alerts are for HMAC-SHA256, which is a standard secure algorithm. Network access is limited to documented first-party Xquik API endpoints. Risk level set to LOW due to inherent network access for API calls.

## Stats

- - Views: 0
- - Downloads: 0
- - Favorites: 0
- - Popularity score: 0