> ## Documentation Index
> Fetch the complete documentation index at: https://docs.summerengine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Store listing skill for AI agents

> Write a Summer Games store page: title, tagline, descriptions, tags, per platform, and what never to write. A Summer Engine skill for AI agents.

`store-listing` is a skill from the [Summer skill library](/mcp/skills): a guide your AI agent reads when the task matches, so it builds the good version on the first try. Write a Summer Games store page: title, tagline, descriptions, tags, per platform, and what never to write.

| | |
| - | - |
| Status | Stable |
| Domains | Publishing and growth, Product language |
| Version | `1.0.0` |
| Recommended set | No, installed by `--all` or by name |

## When your agent uses it

* Writing or fixing a game's store page text on Summer Games: title, tagline, description, tags
* Store.update\_listing or store.get\_listing says a text field is missing or wrong
* Choosing the targets (web, Mac, Windows, Linux, iPhone, Android) that decide the desktop and mobile store flows

## Install

`summer setup` installs every skill for your agent. To add only this one:

```bash theme={null}
npx -y summer-engine@latest skills install store-listing --agent claude-code
```

Swap `claude-code` for your agent, such as `codex` or `cursor`. See [Skills](/mcp/skills#quick-start) for every option.

## The skill

This skill covers the store page text per flow (desktop and mobile): targets, title, tagline, descriptions, tags, and what never to write.

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:

1. `summer_docs_read` with id `skill/store-listing` returns the current text when this machine is signed in (`summer login`).
2. A host that shows MCP prompts or resources has it as the `store-listing` prompt and the resource `summer://skills/store-listing`.
3. Without a store sign-in: [https://docs.summerengine.com/llms.txt](https://docs.summerengine.com/llms.txt) lists every docs page; fetch any page as .md.

The one rule to keep even before you load it: Never invent features, modes, player counts, awards or prices.

## From a shell

No Summer MCP tools in this session? Run each one as a command; when `summer --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.

| In this skill | Command |
| - | - |
| `summer_docs_read` | `summer docs read` |

## Related skills

* [`publish-your-game`](/skills/publish-your-game): Publish a game on Summer Games through MCP: store page, art, build upload, submit, owner approval link.
* [`store-art`](/skills/store-art): Make Summer Games store art per slot: key art, covers, icons, screenshots, trailer, size and text rules.

***

Source: [`library/skills/store-listing/SKILL.md`](https://github.com/SummerEngine/summer/blob/main/library/skills/store-listing/SKILL.md), rendered from `summer-engine@4.3.0` on npm.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.