Nakama matchmaking and social state
Connects matchmaking, parties and competitive results to trusted player state. It distinguishes temporary online presence from durable membership and defines what happens when a search is cancelled or ownership changes.
nakama-matchmaking-social
See how it helpsWhen is it useful?
Use it when parties, presence, search cancellation and leaderboard submissions interact in a multiplayer flow.
What does it help you do?
- Derives player eligibility from validated server state.
- Separates temporary presence, durable membership and party ownership.
- Controls score submission and defines cancellation transitions.
Try asking this
Create ranked matchmaking for a party of three. Try a client-forged rating, a leader disconnect and cancellation just as a match is found. Verify server eligibility and party ownership, prevent duplicate joins and accept leaderboard results only through the trusted outcome path.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Nakama — matchmaking social
Use when implementing Nakama matchmaking, parties, lobbies, leaderboards or social game flows.
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
Define player eligibility and match properties from validated state. Distinguish temporary presence from durable membership and clarify party ownership. Keep matchmaking filters separate from authorization. Make leaderboard score submission server-controlled where game integrity requires it.
Deliver
A matchmaking/social state map with allowed transitions and explicit cancellation behavior. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Client-selected properties and a leaderboard API alone do not prove score integrity or eligibility.
Acceptance scenario
Cancel a search, change party leader, leave during matching and submit an invalid score from another identity. 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