メニュー
Fetch tweet content directly from fxtwitter API. Use when given a tweet/X URL to extract the tweet text, author, media, and engagement stats without loading x.com.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate true pixel art sprites, tilesets, and animations with the Retro Diffusion API — the best dedicated pixel art model. Use when the user says "generate pixel art", "make a sprite with AI", "use Retro Diffusion", "rdpk", or wants high-quality pixel art faster than hand-coded sprite arrays. Requires a Retro Diffusion account and RETRODIFFUSION_API_KEY (paid credits). Great for quick prototyping of 2D Phaser games.
Add music and sound effects to a game using the Web Audio API — background music, gameplay themes, and SFX. Zero dependencies. Use when the user says "add music", "add sound effects", "add audio", "make it sound good", "add BGM", or "add SFX to my game". Do NOT use for gameplay features or visual design.
Audit and improve the visual design, polish, and player experience of an existing game. Use when the user says "make my game look better", "improve the design", "add polish", "add juice", "add particles", "fix the UI", or "make it more visually appealing". Do NOT use for gameplay logic changes (use add-feature instead).
Analyze a game, find what needs work, and implement the highest-impact improvements. Use when the user says "improve my game", "make my game better", "fix my game", "what's wrong with my game", or "polish my game". Run repeatedly — each pass finds the next most impactful thing to fix. Do NOT use for adding specific new features (use add-feature) or initial game creation (use viral-game for one-shot builds, make-game for milestone-driven projects).
Use when the user wants to design, scaffold, build, or iterate on a video game — including brainstorming new game ideas, planning a gameplay loop, choosing an engine, scaffolding a project, adding features, fixing gameplay bugs, or working on assets. Triggers on phrases like "make a game", "create a [genre] game", "build a [type] game", "I want to make a [genre]", or any session inside a game project directory (has docs/, src/, or an engine config).
Register your game on Play.fun (OpenGameProtocol), add the browser SDK, and get a monetized play.fun URL. Use when the user says "monetize my game", "add Play.fun", "add rewards", "register on Play.fun", or "get a play.fun URL". Requires Play.fun MCP server for game registration.
| name | fetch-tweet |
| description | Fetch tweet content directly from fxtwitter API. Use when given a tweet/X URL to extract the tweet text, author, media, and engagement stats without loading x.com. |
| argument-hint | [tweet-url] |
| license | MIT |
| metadata | {"author":"OpusGameLabs","version":"1.3.0","tags":["twitter","tweet","fetch","fxtwitter","social-media"]} |
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.