skills/unity-liveops/SKILL.md
Plan, inspect, and validate Unity LiveOps integrations for remote config, analytics, ads, IAP, economy tuning, events, A/B testing, push notifications, consent, and release-safe operations. MUST use for live game service readiness, SDK service initialization order, test-mode checks, privacy gates, and production configuration reviews. Do not add secrets or production keys to source-controlled files.
npx skillsauth add cuozg/oh-my-skills unity-liveopsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Coordinate Unity live game operations safely across services, SDKs, environments, privacy gates, and release readiness.
Use for:
Packages/manifest.json, Packages/packages-lock.json, and package folders for LiveOps-related SDKs.Assets/LevelPlay, Assets/Push Notifications, Assets/Plugins/Android, and SDK packages.ManageAsset(Search/GetInfo) to locate config assets, SDK folders, scenes, prefabs, and documentation.ManageGameObject(GetComponents) to inspect bootstrap objects and service components.PackageManager_GetData for package metadata; delegate package changes to unity-package-manager.ReadConsole or GetConsoleLogs to detect initialization, resolver, SDK, or platform errors.ManageScene(GetHierarchy) when validating bootstrap scene wiring.Verify:
unity-sdk-integration.unity-mobile.unity-code.unity-package-manager.Report services inspected, environment mode, privacy/consent status, initialization evidence, validation results, and any production-release blockers.
tools
Generate Unity raster image assets through Unity MCP: game sprites, item art, backgrounds, UI icons, portraits, concept images, transparent cutouts, image edits, upscales, background removal, and Unity scene or Game View screenshots. Use when a Unity project needs image files imported under Assets or screenshots captured from the editor. Do not use for meshes, audio, animation, materials, gameplay code, UI Toolkit layout, or generic non-Unity image generation.
tools
Create Unity technical solution documents from user requirements, feature ideas, bug goals, specs, or codebase problems. Use when the user asks for a technical approach, architecture, implementation strategy, solution options, feasibility analysis, system design, or "how should we build/fix this" for Unity runtime, Editor, tools, assets, data, UI, WebGL, SDKs, or production pipelines.
tools
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
development
Convert a spec document into an implementation TODO list in the same spec folder. U se when the user says goal-todo, todo from spec, generate tasks from spec, turn this spec into todos, create implementation checklist, extract tasks, or asks to read a Docs/Specs design doc and produce what must be implemented. Includes UI/UX review and codebase investigation before writing the checklist. Do not use for implementing the tasks, creating new goal files, writing test cases, or verifying completed work.