remix-agent-publish

When 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-cli skill for terminal-based auth, config, upload, and analytics flows.
• Use the remix-mcp-quickstart skill when the user is working through an MCP client.
• Read the remix-api-auth skill for authentication setup.
• Fetch OpenAPI spec at https://api.remix.gg/docs/json before generating API calls.
• Use the remix-api-reference skill for workflow guardrails (not as the method/path source of truth).
• For Phaser builds, use the phaser-2d-arcade skill.
• For lightweight 3D builds, use the threejs-lite skill.
• Use the remix-game-sdk skill when generating or fixing game code.
• Apply the remix-submission-rules skill for validation requirements.
• Follow the remix-game-best-practices skill for mobile-first and SDK-safe implementation.
• Use the remix-rest-snippets skill for client integration examples.
• Use the remix-mcp-quickstart skill for assistant workflows.

Available Workflows

• remix-game-creation - Create a new game draft
• remix-upload-game - Upload version code
• remix-add-image - Generate and add images to a game
• remix-add-sprite - Generate and add sprites to a game
• remix-shop-items - Create and manage in-game shop items
• remix-multiplayer - Enable multiplayer support
• remix-save-game - Add save/load game state
• remix-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.json for project-local config (gameId, versionId)
• legacy .remix-mcp.json for older projects
• ~/.config/remix/credentials.json for 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:

1. Fetch the OpenAPI spec at https://api.remix.gg/docs/json
2. Use the spec to determine exact methods, paths, and schemas
3. Make authenticated REST calls with your API key
4. 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/docs
• https://api.remix.gg/docs/json
• packages/cli/src/index.ts
• packages/mcp/src/core/tool-defs.ts
• packages/mcp/skills/SKILL.md
• packages/mcp/skills/workflows/*.md
• apps/server-api/routes/device-auth.ts
• @remix-gg/sdk (NPM package)