Update to Mini Games

{
  "description": "Open the Mini Games hub, start a named game, and relay the player's replies into the running game. Use whenever the user wants to play a game, says \"open mini games\", \"let's play\", names one of the games, or is mid-game and answers a question.",
  "included_files": [],
  "name": "play-mini-games",
  "skill_md_contents": "---\r\nname: play-mini-games\r\ndescription: Open the Mini Games hub, start a named game, and relay the player's replies into the running game. Use whenever the user wants to play a game, says \"open mini games\", \"let's play\", names one of the games, or is mid-game and answers a question.\r\n---\r\n\r\n# Play Mini Games\r\n\r\nMini Games is a click-based game hub rendered inline through the Mini Games widget.\r\nThe widget embeds the game site, which runs gameplay and audio itself. Your job is\r\nto drive it with the MCP tools and relay what the player says.\r\n\r\n## Workflow\r\n\r\n1. **Launch phrases** (\"open mini games\", \"play a game\", \"let's play\", \"games\"):\r\n   call `open_hub` immediately. Do not describe the games in text first.\r\n2. **A named or themed game** (\"play the werewolf\", \"something silly\") when Mini Games is\r\n   not open yet in this conversation: call `open_game` with the closest match from the catalog.\r\n3. **While a game is running**, relay the player's reply with the matching tool:\r\n   - bare agreement (yes, yeah, sure, ok) -> `yes`\r\n   - bare refusal (no, nope, not now) -> `no`\r\n   - asking for instructions -> `help`\r\n   - anything else (a word, a name, a number, a guess) -> `answer` with the text\r\n     lowercased and stripped of filler words\r\n4. **Changing games mid-session**: call `switch_game` (use `\"menu\"` to go back to the game\r\n   menu). It changes the game inside the existing widget instead of opening a new one.\r\n5. **Checking the catalog**: `list_games` only returns the list of games; it opens nothing.\r\n   Use it when the player asks for a game that may not exist, then explain if it is not there.\r\n6. **PLAY tap**: browsers need one tap before game audio can start, so the widget shows a\r\n   PLAY button. If the game is waiting for it, ask the player to tap PLAY in the widget.\r\n\r\n## Session handling\r\n\r\nThe signed-in player's game continues across calls on its own; tools take no session\r\nargument.\r\n\r\n## Account linking\r\n\r\nThe first call may prompt the player to connect their Mini Games account. This is\r\nexpected: linking lets the game save coins and progress. Continue the flow once the\r\naccount is connected.\r\n\r\n## Games available\r\n\r\nTappables: 50 quick tap games such as Balloon Pop, Bonk Bonk, Brick Smash, Puffin Flap\r\nand Snake Snack (`list_games` returns them all). They are played by tapping in the widget;\r\nthere are no answers to relay apart from \"play again\".\r\n\r\nThe Werewolf, Animal Idol, Chocolate Factory, Decision Time, Piranha Tower,\r\nFart Game, Reindeer Racing, Beat the Buzzer, Dad Jokes Duel.\r\n\r\n## Do not\r\n\r\n- Do not narrate game audio or invent game state; the widget shows it.\r\n- Do not send a bare yes/no through `answer`.\r\n- Do not call `open_hub` when the player already named a game; use `open_game`.\r\n- Do not silently substitute another game when the requested one is not in the catalog.\r\n"
}