Nakama diagnostics
Verifies that the intended server module and gameplay handler actually run after delivery. It separates match, storage and socket problems instead of treating a healthy status endpoint as complete game verification.
nakama-diagnostics-delivery
See how it helpsWhen is it useful?
Use it when deployments look healthy but RPCs, matches or persistence behave unexpectedly.
What does it help you do?
- Records server, runtime and module versions with a reproduction.
- Separates match tick, storage contention and socket measurements.
- Verifies the expected runtime handler actually loads after deployment.
Try asking this
After releasing our arena backend, one attack RPC still behaves like the previous version. Record the loaded module and runtime, invoke the actual handler and trace its match or storage path. Confirm the corrected handler runs, then test reconnect rather than stopping at a successful health response.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Nakama — diagnostics delivery
Use when diagnosing Nakama runtime errors, match load, latency or deployment behavior.
Version and project gate
Inspect Nakama server and client SDK versions, chosen Go/TypeScript/Lua runtime, compiled module deployment, database topology, match handlers, RPC registrations, auth/session handling, storage collections and permission rules. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Capture exact server/runtime/module versions and the bounded reproduction. Correlate request, match and outcome IDs without sensitive payloads. Measure tick duration, storage contention and socket behavior separately. Define compatible module rollout and recovery with the existing topology.
Deliver
A diagnostic timeline, scoped fix and deployment handover tied to an observed version. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
A healthy server endpoint does not establish a loaded runtime module or correct match behavior.
Acceptance scenario
Restart with the intended module, execute a representative RPC/match path and inspect whether the expected handler actually ran. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Kairo. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md