@blazium-games/skills 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Divine Games, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,34 @@
+# Blazium Games skills
+
+Agent skills for [Blazium Games](https://blazium.games), the store operated by Divine Games, Inc. They cover store pages, deploys, crash reporting, analytics, keys, and playing or buying games.
+
+This package is the store. It is not the engine skills at [`@blazium-engine/skills`](https://www.npmjs.com/package/@blazium-engine/skills), and it does not install Hub, the engine CLI, or the toolchain. A game on Blazium Games does not have to be made with the Blazium engine.
+
+The guide and the in-repo Cursor plugin source stay in [games_docs](https://github.com/blazium-games/games_docs). This repo is the versioned release.
+
+## Install
+
+```bash
+npm install @blazium-games/skills
+```
+
+Cursor: add `blazium-games/games_skill` from **Cursor Settings > Plugins**.
+
+The catalog is [https://cdn.blazium.app/games-skills/skills.json](https://cdn.blazium.app/games-skills/skills.json).
+
+## Plugins
+
+| Plugin | What it covers |
+|--------|----------------|
+| `blazium-games-developer` | Get started, store page, deploy, crash reporting, debug crash, analytics, keys |
+| `blazium-games-player` | Get started, player, purchases |
+| `blazium-games` | Every skill, plus `mcp.json` |
+
+`mcp.json` points at `https://mcp.blazium.games/mcp` and `https://mcp.blazium.games/player`. A token belongs to one server.
+
+## Hosts
+
+- Claude Code reads `.claude-plugin/marketplace.json`.
+- Cursor reads `.cursor-plugin/marketplace.json`.
+- Codex reads `.agents/plugins/marketplace.json`.
+- Grok reads the Claude marketplace and `./.grok/skills/`. See [GROK.md](GROK.md).

package/package.json

@@ -0,0 +1,23 @@
+{
+  "name": "@blazium-games/skills",
+  "version": "0.1.0",
+  "description": "Agent skills for the Blazium Games platform.",
+  "repository": "https://github.com/blazium-games/games_skill",
+  "license": "MIT",
+  "files": [
+    "skills",
+    "README.md",
+    "LICENSE"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "homepage": "https://blazium.games",
+  "bugs": "https://github.com/blazium-games/games_skill/issues",
+  "author": "Blazium Games",
+  "keywords": [
+    "blazium",
+    "blazium-games",
+    "skills"
+  ]
+}

package/skills/blazium-games-analytics/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: blazium-games-analytics
+description: Read and summarize Blazium Games visitor analytics for a game page, including views, unique visitors, countries, and tracked actions. Use when the user asks how their game page is doing, for traffic numbers, or for a weekly analytics summary.
+license: MIT
+---
+
+# Blazium Games: Analytics
+
+Summarize store page traffic for one game.
+
+## Invoke This Skill When
+
+- "How is my game page doing?", "how many visitors this week?"
+- "Which countries are my players from?"
+- The user runs the `analytics_summary` prompt
+
+## Prerequisites
+
+- The `blazium-games` MCP server is connected (read access is enough)
+
+## 1. Fetch
+
+1. Resolve the game with `list_games` if the user did not give a `uid`.
+2. Call `get_game_analytics` with `uid` (or read `blazium-games://games/{uid}/analytics`).
+
+## 2. Interpret
+
+| Field | Meaning |
+|-------|---------|
+| `total_views` | Page visits (`visited` actions) |
+| `unique_visitors` | Distinct sessions |
+| `country_breakdown.countries[]` | `country`, `count`, `percent` |
+| `per_game[]` | Visitors and actions per game |
+| `actions[]` | Tracked actions such as visits and downloads |
+| `downloads.total` | Downloads that went through in the last 30 days |
+| `downloads.anonymous` | Downloads with no account (anonymous downloads on) |
+| `downloads.by_source[]` | `website`, `asset_library` (Godot or Blazium editor), `api`, `mcp_player`, `mcp_dev` |
+| `downloads.by_access[]` | `anonymous`, `owner`, `free`, `purchase`, `grant`, `key`, `bundle` |
+| `downloads.by_outcome[]` | Every attempt, including refusals such as `sign_in_required` and `payment_required` |
+
+Analytics are aggregate. Individual visitors are not identifiable through the MCP.
+
+## 3. Summarize
+
+Report in a few sentences:
+
+- Views and unique visitors
+- Top three countries with percentages
+- Notable actions (for example downloads compared with views)
+- Downloads by source, and refusals worth fixing (many `payment_required` or `sign_in_required` attempts from the editor asset library, for example)
+- One suggestion, such as improving the tagline if views are high but downloads are low
+
+For crash trends, use `blazium-games-debug-crash` instead.
+
+## Docs
+
+https://docs.blazium.games/docs/mcp/reference

package/skills/blazium-games-crash-reporting/SKILL.md

@@ -0,0 +1,133 @@
+---
+name: blazium-games-crash-reporting
+description: Send crash reports, standard launch events, and custom events from a game to Blazium Games. Configures the Blazium Engine crash reporter or a custom HTTP reporter with X-App-Id and X-Build-Id, adds the session_start, boot_ok, first_input, session_end, and quit events that rate launch health, uploads Breakpad symbols with chauffeur, and verifies reports arrive. Use when the user wants crash reporting, crash dumps, symbols, launch health, error telemetry, or gameplay events for a Blazium Games project.
+license: MIT
+---
+
+# Blazium Games: Crash Reporting
+
+Wire a game to `POST https://api.blazium.online/api/v1/public/crashes` so crashes show up in `list_game_crashes`.
+
+## Invoke This Skill When
+
+- "Add crash reporting", "send crash dumps to Blazium Games", "why aren't my crashes showing up?"
+- The user wants custom gameplay or telemetry events
+- A build was just deployed and needs its `build_id` wired in
+
+## Prerequisites
+
+- The `blazium-games` MCP server is connected
+- At least one registered build (see `blazium-games-deploy`)
+
+## 1. Resolve identity
+
+1. Call `get_deploy_info` with the game `uid`. Read `auth.crash_headers`:
+   - `X-App-Id`: the game uid
+   - `X-Build-Id`: the latest build's `build_id`
+2. If the user ships several platforms or channels, call `list_game_builds` and pick the `build_id` matching the exact version, OS, arch, and channel. Every combination is its own build.
+
+`X-Build-Id` is a build UID, never a version string. Crash ingest needs no secret, so these values are safe to ship inside the game.
+
+## 2a. Blazium Engine games
+
+Set these in Project Settings under `application/crash_reporter/`:
+
+| Setting | Value |
+|---------|-------|
+| `enabled` | `true` |
+| `upload_mode` | `InEngine`, `Sidecar`, or `Both` |
+| `endpoint` | `https://api.blazium.online/api/v1/public/crashes` |
+| `app_id` | the game uid (`X-App-Id`) |
+| `build_id` | the build UID (`X-Build-Id`) |
+| `app_version` | the build version |
+| `build_channel` | `stable`, `beta`, etc. |
+| `require_user_consent` | `true` (recommended) |
+| `privacy_policy_url` | `https://blazium.games/privacy-policy` or your own |
+
+For the sidecar UI, place the [crash_reporter](https://github.com/blazium-games/blazium_crash_reporter) binary next to the game executable. Never put secrets in Project Settings.
+
+In CI, write `build_id` into the project before exporting, so each exported binary reports against its own build.
+
+## 2b. Custom reporter
+
+1. Create the report:
+
+   ```http
+   POST https://api.blazium.online/api/v1/public/crashes
+   X-App-Id: <game uid>
+   X-Build-Id: <build_id>
+   Content-Type: application/json
+
+   { "has_dump": true, "has_log": true, "app_name": "My Game", "app_version": "1.0.0",
+     "engine_version": "4.8", "os": "windows", "arch": "x86_64",
+     "user_message": "It froze on level 3", "anonymous": true, "metadata": {} }
+   ```
+
+   The response is `201` with `id` and an `uploads` object containing `dump` and/or `log` entries: `url`, `method` (`PUT`), `expires_at` (24 hours), `max_bytes` (64 MB), and `filename` (`dump.dmp` or `log.txt`).
+
+2. Upload each file to its `url` with `PUT`, sending the raw bytes (or a multipart `file` part). Each URL works once.
+
+| Error code | Meaning |
+|------------|---------|
+| `4001` | Invalid JSON body |
+| `4010` | Missing `X-App-Id` or `X-Build-Id` |
+| `4030` | Unknown app id, or a `build_id` that doesn't belong to that app. Use the `build_id` from `list_game_builds`, not a version string |
+| `4130` | `metadata` has more than 64 keys (`413`) |
+| `4290` | The game hit its daily crash report limit (`429`); retry tomorrow |
+
+Past the daily upload limit the report is still stored but `uploads` is empty.
+
+## 3. Standard events (always add these)
+
+Every game should send the six standard events so its builds get a launch health band on the store page and new games can reach the Unheard of shelf. Add them without being asked whenever you wire crash reporting, and tell the user you did.
+
+| Event | When | Fields |
+|-------|------|--------|
+| `session_start` | Process started | |
+| `boot_ok` | First frame of the main menu or first scene | `device_uid` (required), `ms` since start (optional, 0 to 600000) |
+| `first_input` | First key, click, touch or gamepad button | `ms` (optional, 0 to 600000) |
+| `session_end` | Normal close | `seconds` (required, whole number 0 to 86400) |
+| `quit` | The player chose Quit | |
+| `crash` | Crash reporter, or next launch after an unclean exit | `device_uid` (required) |
+
+Send them to the events endpoint below with the same random per-install `device_uid` on every event (store it in `user://`). Clamp `ms` and `seconds` to their ranges: one invalid standard event refuses the whole request with `4158`.
+
+For Blazium and Godot, add an autoload (for example `res://autoload/blazium_events.gd`, registered in Project Settings > Autoload) that sends `session_start` in `_ready`, `boot_ok` after the first processed frame, `first_input` from `_input` once, and `session_end` on `NOTIFICATION_WM_CLOSE_REQUEST`, and exposes a `quit_game()` that sends `quit` and `session_end` before quitting. A complete script is in https://docs.blazium.games/docs/crash-reporting#standard-events. Use the same `app_id` and `build_id` as the crash reporter. For other engines, send the same events at the same moments.
+
+Ask before adding them if the game has no privacy policy or the user needs player consent for telemetry.
+
+## 4. Custom events (optional)
+
+```http
+POST https://api.blazium.online/api/v1/public/events
+X-App-Id: <game uid>
+X-Build-Id: <build_id>
+Content-Type: application/json
+
+{ "events": [ { "event": "level_complete", "anonymous": true, "device_uid": "<random per install>" } ] }
+```
+
+Up to 100 events per request (more returns `4130`); the response is `202`. Use a random per-install id, not hardware identifiers.
+
+## 5. Symbols
+
+Stacks from minidumps only show addresses until Breakpad symbols are uploaded for that build. Symbols can only be uploaded with the chauffeur CLI and the game's deploy key:
+
+1. Export with debug symbols (the `.pdb` on Windows, an unstripped binary or `.debug` file on Linux, the `.dSYM` on macOS).
+2. Make `.sym` files: `cargo install dump_syms`, then `dump_syms <pdb|binary|dSYM> > symbols/<name>.sym`.
+3. Upload: `chauffeur symbols --build-id <build_id> symbols/`, or `--symbols symbols/` on `chauffeur addfiles`. `upload_symbols_info` returns the exact command.
+
+Check with `list_build_symbols`. Details: https://docs.blazium.games/docs/cli/symbols
+
+## 6. Verify
+
+1. Trigger a test crash (or send the JSON above with `curl`).
+2. Call `list_game_crashes` and confirm the new report and its `build_id`.
+3. Run the game once and check that the events arrive with `get_game_analytics`. `get_build_health` rates a build once enough devices have launched it.
+4. Hand off to `blazium-games-debug-crash` to read the crash.
+
+If nothing arrives, check that `X-Build-Id` belongs to this game (`get_game_build`) and that the endpoint is the `crash_ingest` URL from `get_deploy_info`.
+
+## Docs
+
+https://docs.blazium.games/docs/crash-reporting

package/skills/blazium-games-debug-crash/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: blazium-games-debug-crash
+description: Investigate Blazium Games crash reports. Lists recent crashes, reads the stack excerpt and metadata, downloads dumps, logs, or stackwalk output, maps the crash to a build and source code, and proposes a fix. Use when the user asks to look at crashes, debug a crash, or triage crash reports for a Blazium Games project.
+license: MIT
+---
+
+# Blazium Games: Debug a Crash
+
+Go from "players are crashing" to a root cause and a fix in the user's code.
+
+## Invoke This Skill When
+
+- "What are my latest crashes?", "debug this crash", "why is my game crashing?"
+- The user pastes a crash id from https://blazium.games
+- After `blazium-games-crash-reporting` verifies reports arrive
+
+## Prerequisites
+
+- The `blazium-games` MCP server is connected (read access is enough)
+- The game's source code is open in the workspace (for step 4, Map to code)
+
+## 1. Find the crash
+
+1. Call `list_crash_groups` with the game `uid`. Each group is one cause (top stack frames, or the crash message and platform before a stackwalk), most recently seen first (up to 100 groups), with counts per build and a `sample_crash_id`.
+2. A group whose reports all come from the newest build usually means a regression in that build.
+3. Pick the crash the user named, or the `sample_crash_id` of the group with the highest count. `list_game_crashes` lists individual reports when you need more than the sample.
+4. Call `list_bug_tickets` for the player's side: what they were doing, in their words. A ticket with an attached dump or log has a `crash_id` you can read like any other crash.
+
+## 2. Read the report
+
+Call `get_crash` with `uid` and `crash_id`. Key fields:
+
+| Field | Meaning |
+|-------|---------|
+| `build_id`, `os`, `arch` | Which build and platform crashed |
+| `user_message` | What the player said they were doing |
+| `has_dump`, `has_log`, `has_stack` | Which artifacts can be downloaded |
+| `analysis` | Server-side analysis, if already run |
+| `metadata` | Reporter metadata (engine version, custom fields) |
+
+Call `get_game_build` with the `build_id` to get the version and channel.
+
+## 3. Download artifacts
+
+Call `request_crash_download` with `kind`:
+
+- `stack`: symbolicated stackwalk output. Start here.
+- `log`: the log tail (`log.txt`).
+- `dump`: the minidump (`dump.dmp`) for a native debugger.
+
+Each call returns a private `url` valid for 1 hour (`expires_in: 3600`). Fetch it promptly; do not share it or paste it into public places.
+
+## 4. Map to code
+
+1. Take the top frames from the stack that belong to the user's code (skip engine and OS frames).
+2. Search the workspace for those functions and files.
+3. Check out or inspect the commit matching the build version when possible, so line numbers line up.
+4. Read the log tail for the last actions before the crash.
+
+## 5. Report
+
+Give the user:
+
+- One sentence root cause
+- The file and function, with a code reference
+- The builds and platforms affected, and how many reports
+- A proposed fix, and a test or reproduction step
+- If the build is live on `stable` and crashing badly, offer `rollback_channel` (needs write access). Players go back to the previous build and nothing is deleted
+- Once a fix ships, offer to mark the matching bug tickets with `update_bug_ticket` (`status` `fixed`, or `closed` if it won't be fixed). `open` reopens one
+
+If the dump has no symbols, say so and suggest exporting with debug symbols for the next build.
+
+## Docs
+
+https://docs.blazium.games/docs/crash-reporting#reading-crashes

package/skills/blazium-games-deploy/SKILL.md

@@ -0,0 +1,185 @@
+---
+name: blazium-games-deploy
+description: Ship game builds to Blazium Games from CI or the command line. Issues rotated deploy keys, registers a build and uploads its zipped files and Breakpad symbols with the chauffeur CLI (or the upload API), and wires the build_id into crash reporting. Use when the user wants to deploy, upload, publish a build, upload symbols or store images, or set up GitHub Actions or GitLab CI for Blazium Games.
+license: MIT
+---
+
+# Blazium Games: Deploy Builds
+
+Register a build, upload its files, and keep the returned `build_id` for crash reporting. Builds and symbols only upload through the chauffeur CLI or the upload API with the game's deploy key. Store images upload through chauffeur or the game's edit page on the website. MCP can list and delete them but never uploads.
+
+## Invoke This Skill When
+
+- "Deploy my game to Blazium Games", "upload a build", "set up CI for Blazium Games"
+- "Upload my debug symbols", "upload my screenshots"
+- The user has a built game folder and a Blazium Games store page
+- A CI job needs `BLAZIUM_ACCESS_TOKEN` / `BLAZIUM_SECRET_KEY`
+
+## Prerequisites
+
+- The `blazium-games` MCP server is connected with write access (see `blazium-games-get-started`)
+- A store page exists. If not, run `blazium-games-store-page` first
+- The game owner's email is verified. Uploads for an unverified owner fail with code `4096`. Check with `get_account` (`email_verified`); if needed, call `request_email_code`, ask the human for the code, and call `verify_email`. A game admin cannot verify for the owner
+- chauffeur, from `https://cdn.blazium.online/tools/chauffeur/<platform>/latest/archive/default` where `<platform>` is `windows-amd64`, `linux-amd64`, `linux-arm64`, `darwin-amd64`, or `darwin-arm64`. The zip contains the `chauffeur` binary
+
+## 1. Read deploy info
+
+Call `get_deploy_info` with the game's `uid` or vanity name. It returns (no secrets):
+
+| Field | Use |
+|-------|-----|
+| `endpoints.upload_build` | `https://api.blazium.online/api/v1/tool/upload/build` |
+| `endpoints.crash_ingest` | Crash reporter endpoint |
+| `endpoints.events_ingest` | Events endpoint |
+| `builds[]`, `latest_build_id` | Existing builds and their `build_id` |
+| `keys[]` | Prefixes of existing deploy keys |
+| `env` | Env var names to set in CI (`BLAZIUM_ACCESS_TOKEN`, `BLAZIUM_SECRET_KEY`, `BLAZIUM_API_URL`, `BLAZIUM_UPLOAD_URL`) plus `BLAZIUM_GAMES_APP_ID` and the latest `BLAZIUM_GAMES_BUILD_ID` for crash reporting |
+
+## 2. Get deploy credentials
+
+If the user already has an access token and secret stored in CI, skip this step.
+
+Issuing a key needs developer mode on the account; `4105` means the human must turn it on at https://blazium.games/settings first.
+
+Otherwise **warn first**: `request_deploy_key` immediately invalidates every previous deploy key for that game, which breaks any pipeline still using an old key. After the user confirms, call `request_deploy_key` with the `uid`. It returns `access_token` and `secret_key` once.
+
+Tell the user to store them as CI secrets (for example GitHub Actions secrets `BLAZIUM_ACCESS_TOKEN` and `BLAZIUM_SECRET_KEY`) or in their shell environment. Do not write them into files that are committed. Do not repeat them after they are stored, and don't pass the secret with `--secret` (other processes can see it).
+
+## 3a. Upload with chauffeur (recommended)
+
+chauffeur reads `BLAZIUM_ACCESS_TOKEN` and `BLAZIUM_SECRET_KEY` from the environment (or `--access` and `--secret-stdin`). `chauffeur info` confirms which game the key belongs to.
+
+1. Generate `build.yml` once: `chauffeur genbuild --version 1.0.0`
+2. Optionally add changelog entries: `chauffeur addchangelog --title "..." --description "..."`
+3. Register the build: `chauffeur build --asset build.yml --os windows --arch x86_64`. It prints `BLAZIUM_GAMES_APP_ID` and `BLAZIUM_GAMES_BUILD_ID`
+4. Generate `addfiles.yml`: `chauffeur setfiles --version 1.0.0 --os windows --arch x86_64 --files ./export/windows`
+5. Upload the files, and symbols if the user has them: `chauffeur addfiles --asset addfiles.yml --symbols ./symbols`
+
+`addfiles` reuses the build with the same version, type, OS, arch, and channel (keeping its notes), zips the files, checksums them, and uploads them, in 16 MB chunks that resume after a dropped connection when over 64 MB. Keep `version` the same in both YAML files.
+
+Example `build.yml`:
+
+```yaml
+version: v1
+spec: build
+asset:
+  title: "1.0.0"
+  type: "game"
+  description: "First release"
+  version: 1.0.0
+  engine_version: "4.3"
+  platforms:
+    - os: windows
+      arch: x86_64
+      channel: stable
+  changelog:
+    - title: "Launch"
+      description: "First public build"
+```
+
+Set `engine_version` so mods can show whether they work with the build.
+
+### Several apps (dedicated server, editor, launcher)
+
+A project can ship more than one app, each with its own builds and channels. Add an `app` block to both YAML files, or pass `--app server --app-name "Dedicated Server"` to `build`, `addfiles`, `genbuild`, and `setfiles`:
+
+```yaml
+asset:
+  app:
+    id: server
+    name: Dedicated Server
+```
+
+`id` is 1-32 lowercase letters, digits, or dashes; leave the block out for the main app. The store page groups downloads by app, and clean files of a non-main app are stored as `<game>-<app>-<channel>-<os>-<arch>.zip`. A build is only reused within its own app.
+
+Other chauffeur commands:
+
+| Task | Command |
+|------|---------|
+| Symbols for an existing build | `chauffeur symbols --build-id <build_id> ./symbols` (`upload_symbols_info` returns it) |
+| Store images | `chauffeur media cover art/cover.png`, `chauffeur media thumbnail art/thumb.png`, `chauffeur media add shots/*.png`, `chauffeur media list` |
+| List builds, files, and symbol counts | `chauffeur builds list` |
+| Machine-readable output | Add `--json`; exit codes are 0 ok, 1 usage, 2 API error, 3 network |
+
+Errors print the API code with a hint. See https://docs.blazium.games/docs/cli/troubleshooting
+
+## 3b. Upload API directly
+
+Use this only when chauffeur can't run.
+
+1. `POST https://api.blazium.online/api/v1/tool/upload/build` with headers `X-Access-Token` and `X-Secret-Key` and JSON:
+
+   ```json
+   { "version": "1.0.0", "build_type": "game", "os": "windows", "arch": "x86_64",
+     "channel": "stable", "title": "1.0.0", "description": "First release",
+     "changelog_items": [{ "title": "Launch", "description": "First public build" }] }
+   ```
+
+   The same version, type, OS, arch, and channel update one build instead of creating another, replacing its title, description, and changelog. The response includes `build_id`.
+
+2. `POST https://uploader.blazium.online/api/v1/tool/upload/files` (multipart, same headers) with fields `build_id`, `os`, `arch`, `channel`, `checksum` (SHA-256 hex of the zip), and `file` (a `.zip`, max 5 GB). Folders inside the zip are kept.
+
+   - `os`: `windows`, `macos`, `linux`, `android`, `ios`, or `web`
+   - `arch`: `x86_64`, `x86`, `arm64`, `arm32`, `arm`, `universal`, `wasm32`, or `wasm`
+   - `channel`: lowercase letters, digits, `-`, `_`; starts with a letter or digit; up to 32 characters
+   - `app` (optional, on both calls): the app id for a second app such as a dedicated server, with `app_name` for its display name
+
+3. For large files, open a session first: `POST https://uploader.blazium.online/api/v1/tool/upload/sessions` (same headers, form fields `filename`, `total_size`, `checksum`, `os`, `arch`, `channel`, and `build_id`). The `201` response has `session_id`, `expected_size`, `current_size`, and `expires_at` (6 hours). Send the chunks in order to `/tool/upload/files` as multipart `file` parts with `X-Upload-Session-ID` and `Content-Range: bytes <start>-<end>/<total>`. Each returns `202` until the last one finishes the upload. On an error, resume from its `current_size`.
+
+| Error code | Meaning |
+|------------|---------|
+| `4020`-`4023` | Missing, unknown, or revoked deploy key headers |
+| `4026` | Missing or too-long field on build registration |
+| `4037` | Missing `file`, or a form that could not be read |
+| `4038` | Missing build identification on file upload |
+| `4039` | Build not found (register it first) |
+| `4041` | Invalid `checksum`, `os`, `arch`, or `channel`, or the file is not a `.zip` |
+| `4043` | Over 5 GB, or larger than the chunk's `Content-Range` (`413`) |
+| `4044` | Missing or invalid session headers, or a chunk that doesn't continue the session (resume from `current_size`) |
+| `4045` | Upload session not found or expired; open a new one |
+| `4046` | Checksum mismatch; recompute the SHA-256 of the zip |
+| `4047` | Another chunk for this session is still uploading; wait and retry |
+| `4096` | The project owner must verify their email before uploading |
+| `4290` / `4291` | Too many uploads or open sessions for this game; wait and retry |
+
+Uploaded build files are private. Players download them through short-lived links after verifying their email, and paid games also need a license.
+
+## 4. GitHub Actions
+
+```yaml
+name: Deploy to Blazium Games
+on:
+  push:
+    tags: ["v*"]
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    env:
+      BLAZIUM_ACCESS_TOKEN: ${{ secrets.BLAZIUM_ACCESS_TOKEN }}
+      BLAZIUM_SECRET_KEY: ${{ secrets.BLAZIUM_SECRET_KEY }}
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install chauffeur
+        run: |
+          curl -fsSL -o chauffeur.zip https://cdn.blazium.online/tools/chauffeur/linux-amd64/latest/archive/default
+          unzip -o chauffeur.zip chauffeur && chmod +x chauffeur
+      - name: Register build
+        run: ./chauffeur build --asset build.yml --os linux --arch x86_64 --json > build.json
+      # Export your game into ./export/linux here, with the build_id from build.json
+      # (jq -r '.builds[0].build_id' build.json) in the crash reporter settings.
+      - name: Upload files and symbols
+        run: |
+          ./chauffeur setfiles --version "${GITHUB_REF_NAME#v}" --os linux --arch x86_64 --files ./export/linux
+          ./chauffeur addfiles --asset addfiles.yml --symbols ./symbols
+```
+
+`build.yml` must use the tag's version without the `v`. For several platforms use a matrix, and for GitLab CI see https://docs.blazium.games/docs/cli/ci
+
+## 5. Hand off to crash reporting
+
+Give the new `build_id` to the crash reporter as `X-Build-Id`: in Blazium Engine, write it into the export's `application/crash_reporter/build_id` project setting. `chauffeur build` prints it as `BLAZIUM_GAMES_BUILD_ID` so CI can pass it to the export step; `list_game_builds` and `get_deploy_info` return it too. Continue with `blazium-games-crash-reporting`, which also adds the standard launch events.
+
+## Docs
+
+- https://docs.blazium.games/docs/deploy
+- https://docs.blazium.games/docs/cli

package/skills/blazium-games-get-started/SKILL.md

@@ -0,0 +1,97 @@
+---
+name: blazium-games-get-started
+description: Connect Cursor to Blazium Games and route to the right skill. Blazium Games is the platform for playing and publishing games, applications, mods, and assets. The developer server (mcp.blazium.games/mcp) publishes pages, builds, crashes, analytics, and keys. The player server (mcp.blazium.games/player) finds, reviews, installs, and buys. Use when the user mentions Blazium Games for the first time, asks how to connect, or is unsure whether they want to play or publish.
+license: MIT
+---
+
+# Blazium Games: Get Started
+
+Blazium Games is the platform for playing and publishing games, applications, mods, and assets. A token belongs to one server:
+
+- Developer server `https://mcp.blazium.games/mcp` (`blazium-games`, keys `bgames_mcp_`): pages, builds, crashes, analytics, and keys. Needs developer mode.
+- Player server `https://mcp.blazium.games/player` (`blazium-games-player`, keys `bgames_play_`): find, review, install, and buy. Works for every account.
+
+Never send a player token to the developer server, or a developer token to the player server. Verify the account, then hand off to the skill that matches the user's goal.
+
+## Read this first
+
+Use these instead of browsing the website. Signed-in pages do not have facts the tools already return.
+
+- Docs map: https://docs.blazium.games/llms.txt
+- Platform map: https://blazium.games/llms.txt
+- One project's public facts: `https://<username>.blazium.games/<vanity_name>/llms.txt`
+- Developer server card: https://mcp.blazium.games/.well-known/mcp/server-card.json
+- Player server card: https://mcp.blazium.games/.well-known/mcp/player-server-card.json
+- Which files exist, and which do not: https://docs.blazium.games/docs/discovery
+
+## Invoke This Skill When
+
+- The user says "set up Blazium Games", "connect Blazium Games", or "what can the Blazium Games MCP do?"
+- A Blazium Games tool call fails with an authentication error
+- The user wants to publish, deploy, or monitor a game on https://blazium.games but has not said which part
+
+## Prerequisites
+
+- A Blazium Games account (sign up at https://blazium.games/signup)
+- The `blazium-games` MCP server enabled in Cursor (this plugin ships it in `mcp.json`)
+
+## 1. Connect
+
+The plugin registers the server as:
+
+```json
+{
+  "mcpServers": {
+    "blazium-games": {
+      "type": "http",
+      "url": "https://mcp.blazium.games/mcp"
+    }
+  }
+}
+```
+
+On first use Cursor opens a browser for OAuth. On the consent page the user chooses:
+
+- **Account**: every game they own or admin, plus account tools such as `create_game` and `request_mcp_key`.
+- **A single project**: only that game. Account-only tools return `403` with code `4030`.
+- **A preset**: **Store page**, **CI**, **Crash triage**, **Keys**, **Money**, **Read-only**, or **Full access**. A tool outside the preset returns `4073`; a write with a read-only token returns `4031`.
+
+For playing and buying as a player, the plugin also ships `blazium-games-player` at `https://mcp.blazium.games/player`, which has its own consent. See the `blazium-games-player` skill.
+
+If OAuth is not possible (headless CI, remote agents), use an API key instead. See [references/auth.md](references/auth.md).
+
+## 2. Verify
+
+1. Call `get_profile`. A username confirms the connection.
+2. Call `get_setup` to see the account, games, public URLs, and key prefixes. It never returns secrets.
+3. If `get_setup` fails with `4030`, the token is bound to one project. Use `list_games` instead.
+
+| Symptom | Cause | Fix |
+|---------|-------|-----|
+| `401` / auth prompt loops | Token expired or revoked | Reconnect the server in Cursor Settings > MCP |
+| `403` code `4031` | Read-only token | Reconnect without "Read-only access" |
+| `403` code `4030` | Project-bound token calling an account-level tool or another game | Reconnect choosing "Account" |
+| `403` code `4073` | The preset doesn't cover this tool | Reconnect with a wider preset |
+| `approval_required` (`4214`) | The action waits for the account owner | Ask the human to open the emailed link, then retry with the same `idempotency_key` |
+| `API 404` on a game | Wrong uid or vanity name | Call `list_games` and use the `uid` |
+
+## 3. Route
+
+| Goal | Skill |
+|------|-------|
+| Create or edit a store page | `blazium-games-store-page` |
+| Ship builds from CI or the CLI | `blazium-games-deploy` |
+| Add crash reporting to a game | `blazium-games-crash-reporting` |
+| Investigate a crash | `blazium-games-debug-crash` |
+| Read visitor analytics | `blazium-games-analytics` |
+| Rotate MCP or deploy keys | `blazium-games-keys` |
+| Find, review, or play games as a player | `blazium-games-player` |
+| Buy a game or donate | `blazium-games-purchases` |
+
+## References
+
+- [references/tools.md](references/tools.md): every tool, its inputs, the access it needs, and what it does
+- [references/resources.md](references/resources.md): `blazium-games://` resources and templates
+- [references/prompts.md](references/prompts.md): server prompts
+- [references/auth.md](references/auth.md): OAuth, API keys, scopes, and project binding
+- Full docs: https://docs.blazium.games/docs/mcp