publish-your-game is a skill from the Summer skill library: a guide your AI agent reads when the task matches, so it builds the good version on the first try. Publish a game on Summer Games over MCP: store page, art, build upload, go live.
When your agent uses it
- The user says ‘publish my game’, ‘put it on summer.games’, ‘launch it on the store’ or ‘make it live’
- Taking a built Summer game to live: listing text, art, build upload, the release checklist and summer_go_live
- An agent publishes for the owner end to end and needs the order of the store.* operations
Install
summer setup installs every skill for your agent. To add only this one:
claude-code for your agent, such as codex or cursor. See Skills for every option.
The skill
This skill covers the whole publishing journey: find the game, make its store page, write the text, set the art, export and upload the build, and take it live. Its current text lives on the hosted Summer Engine MCP, the same text the Studio agent reads, so it changes with the store and is never stale here. Load it before you act:summer_docs_readwith idskill/publish-your-gamereturns the current text when this machine is signed in (summer login).- A host that shows MCP prompts or resources has it as the
publish-your-gameprompt and the resourcesummer://skills/publish-your-game. - Without a store sign-in: https://docs.summerengine.com/llms.txt lists every docs page; fetch any page as .md.
The journey in operations
A call writtenarea.action({...}) is the tool summer_area_action when your client lists it, else summer_call({ op: "area.action", input: {...} }); summer_search finds any operation and its exact input. Engine tools keep their summer_* names.
games.list()finds the game;games.create({ title, targets })makes a new one with its first store page draft. Includewebintargetsso it plays in the browser. Keep thegameId.store.get_listing({ gameId })reads the page: text per store, art per slot, the publish checklist and the tags a page can pick.store.update_listing,store.set_art,store.set_trailerandstore.set_soundfill it untilreadyToPublishis true. Editing never publishes.- Export with
summer_export_game, runrelease-readinesson the exact.zip, and report each check to the owner; a hosted game’s upload checks can pass while every online join fails. Then upload it withsummer_publish_build({ gameId, clientVersion, confirm: true })once the owner approved the exact file and version. It waits for Summer’s automated checks and answers each platform’s result (checks), with the fix for a failed one. - Run the
release-checklistskill: the export, the upload’s checks, the store art and every listing detail.summer_store_set_detailsfills the sectionsstore.update_listingdoes not edit: the content questionnaire, the AI disclosure, genres, features, credits, languages and system requirements. summer_go_live({ gameId, publicationId })shows the plan; after the owner approves going live, call it again withconfirm: true. It releases the Build to the platforms that passed, publishes the store page and watches until players get it, or names the failing check and its fix. Web builds and downloads go live with the page. It needs no owner approval link while the person’s Agent permissions allow Publish (the default); with Publish off it answersneeds_permission, andstore.publishreturns a link for the owner instead.store.status({ gameId })shows every upload, what players get now on each platform, and Summer’s decision when there is one.
launch-ready skill (summer_docs_read with id skill/launch-ready).
The one rule to keep even before you load it: a game goes live as soon as Summer’s automated checks pass. Summer’s staff review it after it is live, so never tell the creator to wait for a review. When summer_go_live answers waiting with waitingOn: "summer", every check passed and the platform is still holding the launch on Summer’s side: nothing to fix, and it goes live by itself; call again to keep watching.
When the automatic checks reject the store page (needs_changes), fix what store.status says failed with store.update_listing, then call summer_go_live again. When Summer’s staff, reviewing the live game afterwards, put it on hold (summer_go_live answers on_hold, or store.status says the review is rejected), make the changes in their message with store.update_listing and call summer_go_live again: publishing the newer store page lifts the hold, and a new build alone does not. If there is no written message, say so and ask the owner instead of guessing. A game taken down (taken_down) needs Summer support.
From a shell
No Summer MCP tools in this session? Run each one as a command; whensummer --version is missing or below 4.0, use npx -y summer-engine@latest in place of summer. Fields are flags in kebab-case (--scene-path res://main.tscn) or one --input '<json>', and summer ops describe <op> prints the exact input. The summer-cli skill has the rest.
Related skills
store-listing: Write a Summer Games store page: title, tagline, descriptions, tags, what never to write.store-art: Make Summer Games store art per slot: key art, icons, screenshots, trailer, sizes.grow-analytics: Read a creator’s Summer Grow numbers (page views, launches, sessions, play time), compare windows.export-and-ship: Prepare a game export: check templates and targets, validate release assets, build after approval.release-checklist: Pre-launch check for Summer Games: export, upload checks, store art, listing fields.
Source:
library/skills/publish-your-game/SKILL.md, rendered from summer-engine@4.9.2 on npm.
