fetch-tweet by opusgamelabs/game-creator
npx skills add https://github.com/opusgamelabs/game-creator --skill fetch-tweet您可以使用 fxtwitter API 获取推文内容,该 API 返回结构化的 JSON 数据,无需 JavaScript 渲染或身份验证。
X/Twitter 需要 JavaScript 来渲染推文。在 x.com 上使用 WebFetch 只会返回一个空壳。fxtwitter API (api.fxtwitter.com) 以纯 JSON 格式提供相同的推文数据——无需身份验证、无需 JavaScript,在合理使用情况下没有速率限制的困扰。
给定任何推文 URL,将其转换为 fxtwitter API 端点:
| 输入 URL 模式 | API URL |
|---|---|
https://x.com/<user>/status/<id> | https://api.fxtwitter.com/<user>/status/<id> |
https://twitter.com/<user>/status/<id> |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
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> |
从输入 URL 中提取 <user> 和 <id>,然后构建 https://api.fxtwitter.com/<user>/status/<id>。
使用 WebFetch 并传入转换后的 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.")
fxtwitter API 返回具有以下结构的 JSON:
{
"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": [...]
}
}
}
当您收到一个推文 URL(x.com、twitter.com、fxtwitter.com 或 vxtwitter.com)时:
https://api.fxtwitter.com/<user>/status/<id>WebFetch 和 API URL 进行获取**Author Name** (@handle) — Date
"Tweet text here"
Engagement: X views, Y likes, Z retweets, W replies
如果推文包含媒体(照片/视频),请包含其 URL。
每周安装量
83
代码仓库
GitHub 星标数
32
首次出现
Feb 21, 2026
安全审计
安装于
claude-code72
opencode43
gemini-cli41
github-copilot41
amp41
codex41
You fetch tweet content using the fxtwitter API, which returns structured JSON without requiring JavaScript rendering or authentication.
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.
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>.
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.")
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": [...]
}
}
}
When you receive a tweet URL (x.com, twitter.com, fxtwitter.com, or vxtwitter.com):
https://api.fxtwitter.com/<user>/status/<id>WebFetch with the API URL**Author Name** (@handle) — Date
"Tweet text here"
Engagement: X views, Y likes, Z retweets, W replies
If the tweet contains media (photos/videos), include the URLs.
Weekly Installs
83
Repository
GitHub Stars
32
First Seen
Feb 21, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
claude-code72
opencode43
gemini-cli41
github-copilot41
amp41
codex41
lark-cli 共享规则:飞书资源操作指南与权限配置详解
35,100 周安装