gameflow-troubleshooting
Installation
SKILL.md
GameFlow troubleshooting
Triage a broken GameFlow integration: collect facts, match the symptom, run the check, apply the fix. Conventions (base URL, auth header, casing, error envelope) are in the gameflow skill's api-conventions.md; this skill links to it rather than repeating it.
Rules while debugging
- Never ask the user to paste their API key into chat, logs or a support ticket. Run commands that read
$GAMEFLOW_API_KEYfrom their environment. - If you find a key in game-client code (Unity/Godot/Unreal client, browser, mobile), stop and flag it: move the call to the backend and rotate the key. That's a bug in its own right, whatever else is wrong.
- Read-only checks first. Don't stop servers, delete builds or cancel tickets without asking.
- Causes marked (inferred) come from reading the platform code, not from a documented guarantee.
- A field the API silently ignores is often a renamed or misspelled field. If the GameFlow docs MCP is connected, compare the user's request body with
get_api_operation. If the names differ, don't tell them to rename yet: the docs can be ahead of the deployed API. Show both names and suggest a test call to see which one takes effect.
Step 1: Collect facts
Get these before guessing:
- The exact error body:
{"code": <int>, "message": "...", "details": []}and the HTTP status. Themessageis the most useful clue; look it up in references/error-catalog.md. - Endpoint + method as actually sent (full URL, including
/v1). gameId,gameMode, region, and for servers theserverName; for builds thebuildId.- Who makes the call: backend, dedicated server, CI, or (bug) the client.