Menú
Upload and validate HTML game code for Remix. Use when creating or updating a draft version through the CLI, MCP tools, or direct REST calls.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Generate and add images to a Remix game
Generate and add sprites to a Remix game
Build and publish Remix games with the current Remix toolchain. Use when work touches the official Remix CLI, MCP server, REST publishing APIs, or the @remix-gg/sdk game runtime.
OpenAPI-first endpoint reference for Remix game publishing REST routes
Use the official Remix CLI for authentication, config inspection, game creation, uploads, and analytics. Trigger this skill when a task involves `remix login`, `remix whoami`, `.remix-cli.json`, `REMIX_API_KEY`, or terminal-based game management on Remix.
Quickstart for the official Remix MCP server. Use when configuring or operating `@remix-gg/mcp`, wiring MCP auth, or choosing the right Remix MCP tools and skill resources.
| name | remix-upload-game |
| description | Upload and validate HTML game code for Remix. Use when creating or updating a draft version through the CLI, MCP tools, or direct REST calls. |
This skill guides you through uploading a completed HTML game to the Remix platform. It covers creating the game entry (if needed) and uploading the code.
remix loginremix games create --name "..."remix games versions code update --code-path ./game.htmlFind the path to the HTML file to upload. It should be a single self-contained HTML document with inline CSS and JS.
Read the HTML file and verify:
<!DOCTYPE html> declaration<meta name="viewport" ...> tag<script src="https://cdn.jsdelivr.net/npm/@remix-gg/sdk@latest/dist/index.min.js"></script>@farcade/game-sdk script tagsinglePlayer.actions.gameOver( OR multiplayer.actions.gameOver( (not both).onPlayAgain( callback.onToggleMute( callbacklocalStorage or sessionStorage usageonclick=, onload=, etc.)Fix any reported issues before proceeding.
First, use gameId and versionId from task context or prior tool results
when available.
Otherwise, check the nearest .remix-cli.json. Older projects may still use
.remix-mcp.json. If either already contains gameId and versionId, skip
creation and proceed to step 4.
If none of those sources provide IDs, create the game via CLI or REST.
CLI:
remix games create --name "My Game"
REST:
POST https://api.remix.gg/v1/games
Authorization: Bearer $REMIX_API_KEY
Content-Type: application/json
{ "name": "<game name>" }
The response returns the game ID and version ID.
After creation succeeds, write the returned IDs to .remix-cli.json:
{
"gameId": "<returned game ID>",
"versionId": "<returned version ID>",
"name": "<game name>"
}
Read gameId and versionId from task context, prior tool results,
.remix-cli.json, or legacy .remix-mcp.json.
Preferred CLI path:
remix games versions code update --code-path ./game.html
remix games versions validate get
remix games launch-readiness get
Read the HTML file and pass its content as the code field in the request body:
POST https://api.remix.gg/v1/games/{gameId}/versions/{versionId}/code
Authorization: Bearer $REMIX_API_KEY
Content-Type: application/json
{ "code": "<HTML file contents>" }
The response returns a confirmation with the game ID, version ID, and thread ID.
remix games versions status get and remix games versions thread get are useful post-upload inspection commands.