About remix-agent-publish
remix-agent-publish guides agents, terminal workflows, and external services through creating, uploading, validating, and inspecting Remix games. It covers REST API management and game-specific workflows, with steps grounded in the OpenAPI spec and submission rules.
Key features
- 01Create game drafts
- 02Upload game code and assets
- 03Manage shop items and multiplayer
- 04Add game save support
- 05Validate submissions before upload
Use cases
- 01Create a Remix game through an agent
- 02Upload game versions and assets
- 03Configure multiplayer or game saves
- 04Check a game against submission requirements
MCP support
For work through an MCP client, the skill points to remix-mcp-quickstart. It also notes that MCP can reuse CLI credentials.
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ farworld-labs/ remix-skills --skill remix-agent-publishAfter installing, type/remix-agent-publishin Claude Code to confirm it loaded.
Details
From the project READMEWhen to use
Use this skill when users want to create, upload, validate, or inspect Remix games from an agent, terminal workflow, or external service.
How to use
- Prefer the
remix-cliskill for terminal-based auth, config, upload, and analytics flows. - Use the
remix-mcp-quickstartskill when the user is working through an MCP client. - Read the
remix-api-authskill for authentication setup. - Fetch OpenAPI spec at
https://api.remix.gg/docs/jsonbefore generating API calls. - Use the
remix-api-referenceskill for workflow guardrails (not as the method/path source of truth). - For Phaser builds, use the
phaser-2d-arcadeskill. - For lightweight 3D builds, use the
threejs-liteskill. - Use the
remix-game-sdkskill when generating or fixing game code. - Apply the
remix-submission-rulesskill for validation requirements. - Follow the
remix-game-best-practicesskill for mobile-first and SDK-safe implementation. - Use the
remix-rest-snippetsskill for client integration examples. - Use the
remix-mcp-quickstartskill for assistant workflows.
Available Workflows
remix-game-creation- Create a new game draftremix-upload-game- Upload version coderemix-add-image- Generate and add images to a gameremix-add-sprite- Generate and add sprites to a gameremix-shop-items- Create and manage in-game shop itemsremix-multiplayer- Enable multiplayer supportremix-save-game- Add save/load game stateremix-upload-asset- Upload images, audio, or 3D models as hosted game assets
Game Settings
Current config files:
- task context or prior tool results first
.remix-cli.jsonfor project-local config (gameId,versionId)- legacy
.remix-mcp.jsonfor older projects ~/.config/remix/credentials.jsonfor CLI credentials that MCP can also reuse
Reuse existing IDs instead of inventing new ones or blindly calling createGame. Some upstream MCP docs still mention .remix-settings.json; prefer the current packaged MCP skills and package source when those conflict.
Inline Validation
Before uploading code, run through the validation checklist in the remix-submission-rules skill to catch blockers early.
REST API Workflow
All game management is done through REST API calls to https://api.remix.gg. The general pattern is:
- Fetch the OpenAPI spec at
https://api.remix.gg/docs/json - Use the spec to determine exact methods, paths, and schemas
- Make authenticated REST calls with your API key
- Check responses for success/error envelopes
See the remix-rest-snippets and remix-api-reference skills for details.
Source of truth
When docs and runtime behavior disagree, defer to the server API source and OpenAPI docs:
https://api.remix.gg/docshttps://api.remix.gg/docs/jsonpackages/cli/src/index.tspackages/mcp/src/core/tool-defs.tspackages/mcp/skills/SKILL.mdpackages/mcp/skills/workflows/*.mdapps/server-api/routes/device-auth.ts@remix-gg/sdk(NPM package)