{"id":55525,"plugin_id":"plugin_asdk_app_6abcd43bd3f48191857b19f011870399","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-26T12:07:42.489Z","digest":"52a1ca5c86d14fdef4443c372939f5944ddd4f0b20b2459d10463b7af415ab85","against":null,"payload":{"description":"Diagnoses a Yes2SDK symptom or compliance failure. Use when ads will not show, audio stays dead after an ad, a reward is not granted, a loading screen never dismisses, a verify run FAILs on a rule id, or a platform may not support a module.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":212},{"relative_path":"references/tool-routing.md","size_in_bytes":6075}],"name":"yes2sdk-diagnose","skill_md_contents":"---\nname: yes2sdk-diagnose\ndescription: Diagnoses a Yes2SDK symptom or compliance failure. Use when ads will not show, audio stays dead after an ad, a reward is not granted, a loading screen never dismisses, a verify run FAILs on a rule id, or a platform may not support a module.\n---\n\n# Diagnosing a Yes2SDK integration\n\nFour questions, four tools. Pick by the question actually being asked rather than\nrunning all four.\n\n| The question | Route to |\n| --- | --- |\n| \"it does not work\", an error or a symptom | `yes2sdk:troubleshoot` |\n| \"why did this check fail\", a rule id in hand | `yes2sdk:get_compliance_rule` |\n| \"does this platform support X\" | `yes2sdk:get_platform_capabilities` |\n| \"what modules exist\", an unfamiliar module name | `yes2sdk:list_sdk_modules` |\n\n## Drilling into a verify failure\n\nA `$yes2sdk-verify` run reports findings with a rule id and a short fix hint. The\nhint is a summary; the rule is the thing the platform rejects on.\n\n1. Take the rule id off the finding.\n2. `yes2sdk:get_compliance_rule` with that id returns the full rule text, severity,\n   and why the platform enforces it.\n3. If the finding is a symptom rather than a rule violation (audio dead after an\n   ad, loading screen never dismissing, rewards not granting), go to\n   `yes2sdk:troubleshoot` instead. Those have known causes that the static rule\n   text does not explain.\n4. Re-run `$yes2sdk-verify` for that platform after the fix. Do not mark a FAIL\n   resolved on reasoning alone.\n\n## Before blaming the code\n\nCheck the feature exists on that platform. `yes2sdk:get_platform_capabilities`\nanswers it. An `isSupported()` guard returning false is the SDK working correctly,\nnot a bug. The fix is to handle the unsupported path, not to force the call.\n\n## Reference\n\n`references/tool-routing.md` covers all 11 `yes2sdk` MCP tools: which question each\nanswers, its preconditions, and the failure modes observed in practice. Read it\nwhen a tool returns nothing useful or rejects its arguments.\n\n## Never answer from memory\n\nRule text, limits and capability matrices change server-side. Fetch them. This\nskill carries routing knowledge only; the server is the single source of truth\nfor what any rule says.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}