gameplay-sql

SQL-driven game testing validates mechanics through deterministic queries. This Skill provides game_start, game_state, game_turn, game_find_place, and game_submit tools that execute pure SQL flows to control session lifecycle, manage candidates, handle state transitions, and generate reproducible outputs for location-guessing gameplay.

Yes. Start a game session with game_start, query current state via game_state, process turns with game_turn, locate places with game_find_place, submit final answers via game_submit, and retrieve summaries with game_summary—all executed as SQL-driven operations without external dependencies.

Pure SQL flows eliminate non-determinism in game testing. This approach exercises session initiation, candidate querying, turn logic (yes/no/not_sure answers), location searches, and final submissions through SQL tools, ensuring consistent, reproducible validation of game mechanics and state transitions.

No. This Skill has zero dependencies and operates entirely through SQL-based game tools. Template sessions demonstrate typical gameplay workflows, enabling immediate testing of session lifecycle control, candidate management, and game state without additional frameworks or setup.

Follow the session lifecycle: invoke game_start with a description, check game_state to retrieve current candidates and turn count, execute game_turn to answer questions or progress state, use game_find_place to search locations, submit answers via game_submit, then generate session_summary for deterministic output records.