Update to Yes2SDK

{
  "description": "Cross-platform Yes2SDK rules; the yes2sdk MCP is source of truth. Use when integrating Yes2SDK or fixing compliance for Poki, CrazyGames, Yandex, GameDistribution, YouTube.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 237
    }
  ],
  "name": "yes2sdk-platform-rules",
  "skill_md_contents": "---\nname: yes2sdk-platform-rules\ndescription: Cross-platform Yes2SDK rules; the yes2sdk MCP is source of truth. Use when integrating Yes2SDK or fixing compliance for Poki, CrazyGames, Yandex, GameDistribution, YouTube.\n---\n\n# Yes2SDK platform rules\n\nYes2SDK is one unified API across every supported platform. Write the integration\nonce and gate platform-specific features with `isSupported()` so unsupported\nfeatures no-op. Never call a platform SDK directly. Never invent SDK methods.\n\n## Highest-leverage rules (apply everywhere)\n\n1. `await initializeAsync()` before any other SDK call. Call `startGameAsync()`\n   only when the game is loaded and interactable, never during loading.\n2. Call `game.gameplayStop()` BEFORE every interstitial; `game.gameplayStart()` to\n   resume after.\n3. Pause/mute in `beforeAd`, restore in `afterAd`. Grant rewarded-ad rewards in\n   `adViewed` only, never `afterAd` (it fires even on dismissal).\n4. No external `<script src=\"http...\">`. All platforms sandbox or strip them.\n5. Guard optional modules (`auth`, `banners`, `friends`) with `isSupported()`.\n\n## This is a summary, not the source of truth\n\nPer-platform rules diverge (Poki's 30s/60s ad timing, CrazyGames' 3-minute floor\nand wrapper options, Yandex pause/resume and locale, GameDistribution's `gameId` and\nevent flow, YouTube's cert-mandatory pause/audio handling). These change. Do not\nrely on this list for compliance decisions.\n\nFor the authoritative, current rule set, call the **yes2sdk MCP**:\n\n- `yes2sdk:get_platform_requirements` (platform) returns the full rule list with\n  severities.\n- `yes2sdk:validate_integration` (platform, plus the build inline and/or an\n  Inspector `eventLogJson`) runs the actual checks and surfaces FAILs. The\n  `$yes2sdk-verify` skill holds the calling procedure; use it rather than guessing\n  which build parameters the connected server can read.\n- `yes2sdk:get_quickstart` (platform) and `yes2sdk:get_api_reference` (module) give\n  exact call sequences and method signatures.\n\nWhen in doubt, fetch from the MCP rather than guessing.\n"
}