
Fetch Tweet
- 405 installs
- 305 repo stars
- Updated May 25, 2026
- opusgamelabs/game-creator
Pull tweet text and metadata from X into a game or content pipeline for dynamic quests, leaderboards, community prompts, or live event copy.
About
fetch-tweet integrates X.com tweet retrieval into game-creator workflows, enabling dynamic quests, community challenges, and live event copy by piping post text and metadata directly into game content systems.
- X tweet retrieval for games
- Dynamic in-game content feeds
- Community prompt automation
- Metadata for quests and events
- Reduces manual social copy work
Fetch Tweet by the numbers
- 405 all-time installs (skills.sh)
- +11 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #57 of 247 Game Development skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/opusgamelabs/game-creator --skill fetch-tweetAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 405 |
|---|---|
| repo stars | ★ 305 |
| Last updated | May 25, 2026 |
| Repository | opusgamelabs/game-creator ↗ |
What it does
Pull tweet text and metadata from X into a game or content pipeline for dynamic quests, leaderboards, community prompts, or live event copy.
Files
Fetch Tweet
You fetch tweet content using the fxtwitter API, which returns structured JSON without requiring JavaScript rendering or authentication.
Why fxtwitter
X/Twitter requires JavaScript to render tweets. WebFetch on x.com returns an empty shell. The fxtwitter API (api.fxtwitter.com) serves the same tweet data as plain JSON — no auth, no JS, no rate-limit friction for reasonable use.
URL Conversion
Given any tweet URL, convert it to the fxtwitter API endpoint:
| Input URL pattern | API URL |
|---|---|
https://x.com/<user>/status/<id> | https://api.fxtwitter.com/<user>/status/<id> |
https://twitter.com/<user>/status/<id> | https://api.fxtwitter.com/<user>/status/<id> |
https://fxtwitter.com/<user>/status/<id> | https://api.fxtwitter.com/<user>/status/<id> |
https://vxtwitter.com/<user>/status/<id> | https://api.fxtwitter.com/<user>/status/<id> |
Extract the <user> and <id> from the input URL, then construct https://api.fxtwitter.com/<user>/status/<id>.
How to Fetch
Use WebFetch with the converted API URL:
WebFetch(url: "https://api.fxtwitter.com/<user>/status/<id>", prompt: "Extract the tweet JSON. Return: author name, handle, tweet text, date, media URLs (if any), likes, retweets, replies, views.")Response Structure
The fxtwitter API returns JSON with this structure:
{
"code": 200,
"message": "OK",
"tweet": {
"url": "https://x.com/user/status/123",
"text": "The tweet content...",
"author": {
"name": "Display Name",
"screen_name": "handle"
},
"created_at": "Thu Jan 30 12:00:00 +0000 2026",
"likes": 1000,
"retweets": 500,
"replies": 200,
"views": 50000,
"media": {
"photos": [...],
"videos": [...]
}
}
}Usage Pattern
When you receive a tweet URL (x.com, twitter.com, fxtwitter.com, or vxtwitter.com):
1. Parse the URL to extract username and tweet ID 2. Convert to https://api.fxtwitter.com/<user>/status/<id> 3. Fetch using WebFetch with the API URL 4. Present the tweet content in a readable format:
**Author Name** (@handle) — Date
"Tweet text here"
Engagement: X views, Y likes, Z retweets, W repliesIf the tweet contains media (photos/videos), include the URLs.
Error Handling
- If fxtwitter returns a non-200 status, the tweet may have been deleted or the account suspended
- If the URL doesn't match any known tweet URL pattern, ask the user for a valid tweet link