x-tweet-by-url

Extracts normalized tweet data from any X search, profile, tweet, or list URL.

5.5k|269|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/browser-act/skills --skill x-tweet-by-url
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-tweet-by-url
Source: https://github.com/browser-act/skills/tree/main/solutions/social-listening/x-tweet-by-url
Command: npx skills add https://github.com/browser-act/skills --skill x-tweet-by-url

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Collecting tweets from X (Twitter) requires handling different URL types — search results, user profiles, single tweets, and lists — each backed by a different internal GraphQL endpoint. This Skill unifies them under one entry point: paste any X URL and get back structured per-tweet data with engagement metrics, media, hashtags, and pagination cursors, without writing API integration code.

Core Features & Use Cases

  • Automatic URL classification: Detects whether a URL is a search, profile (tweets/replies/media), tweet detail, or list timeline, and maps it to the correct GraphQL endpoint.
  • Normalized tweet output: Returns text, author details, retweet/reply/like/quote/bookmark/view counts, media, hashtags, mentions, and conversation IDs in a consistent JSON schema.
  • Scroll-based pagination: Captures successive pages via browser scrolling with cursor tracking, deduplication by tweet ID, and clear termination conditions.
  • Use Case: A social listening analyst pastes a mixed batch of X links — a brand search URL, three KOL profiles, and a curated list — and collects all matching tweets into one dataset for sentiment and engagement analysis.

Quick Start

Use the x-tweet-by-url skill to scrape all tweets from this X search URL and return the results as structured JSON.

Frequently Asked Questions about x-tweet-by-url

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scrape tweets from an X (Twitter) URL?

Paste any supported X URL — search, profile, single tweet, or list — and the Skill classifies it, navigates to the page in a logged-in browser, captures the GraphQL response, and returns normalized tweet JSON with text, author, and engagement counts.

What types of X and Twitter URLs are supported for scraping?

Supported URLs are x.com/search, x.com/{handle}, /with_replies, /media, /status/{id}, and /i/lists/{id}. twitter.com links are rewritten to x.com automatically, but mobile.twitter.com links and pages like Bookmarks or Communities are not supported.

Do I need to be logged in to X to scrape tweets?

Yes, an active X login session in the browser is required. The Skill only reads data already visible to the logged-in user and never bypasses authentication; it verifies login status before starting and stops if the user is not signed in.

How does pagination work when scraping X timelines?

Pagination is driven by scrolling: each scroll triggers the next GraphQL request with the previous cursor_bottom. Collection stops when the target tweet count is reached, a page returns zero tweets, or the cursor stops advancing across two pages.

What are the rate limits when scraping X timelines?

Sustained polling triggers per-session throttling, so stay under roughly 150 timeline calls per 15-minute window per session. For large batches, fan out across multiple browser sessions each with its own login and rate budget.

Why does tweet scraping return empty results for some X URLs?

Protected, suspended, or deleted accounts and access-restricted lists return empty responses, and the Skill terminates and reports the cause. Unsupported URL patterns are classified as unknown and rejected before any navigation occurs.