> ## 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.

# Grow analytics skill for AI agents

> Read a creator's Summer Grow numbers (page views, launches, sessions, play time), compare windows. A Summer Engine skill for AI agents.

`grow-analytics` 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. Read a creator's Summer Grow numbers (page views, launches, sessions, play time), compare windows.

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

## When your agent uses it

* The user asks how their game is doing on Summer Games: views, launches, players, play time
* Reading summer\_grow\_overview or summer\_grow\_analytics and turning the numbers into one next step
* Comparing two time windows, walking the store funnel or finding where players drop

## Install

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

```bash theme={null}
npx -y summer-engine@latest skills install grow-analytics --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 how to read a creator's Summer Grow numbers (store page views, launches, play sessions, play time) and analyse them: compare windows, walk the funnel, flag drops, give one next step.

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/grow-analytics` 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 `grow-analytics` prompt and the resource `summer://skills/grow-analytics`.
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: Report what the numbers show; do not guess causes the data cannot support.

## 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.
* [`summer-analytics`](/skills/summer-analytics): Send game events to Summer analytics from the authority or client: fire-and-forget, never blocking gameplay.

***

Source: [`library/skills/grow-analytics/SKILL.md`](https://github.com/SummerEngine/summer/blob/main/library/skills/grow-analytics/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.