What problem does it solve? Automating game editors like Unity, Godot, Unreal, or Blender often involves risky, opaque operations that can silently modify projects, install tools, or conflict with existing MCP server configurations. This Skill enforces an approval-gated workflow so every editor operation is planned, permissioned, reversible, and verified before anything changes. ## Core Features & Use Cases - Approval-Gated Transactions: Builds an explicit transaction plan with exact commands, permissions, backups, rollback steps, and a digest that must be confirmed before any action runs. - Host Adapter Routing: Detects the host application and project read-only, refuses ambiguous host selection, and enforces a single active MCP server per application. - Production Quality Gates: Runs seven completion gates covering rights and licensing, format validation, visual consistency, runtime budgets, playability tests, regression evidence, and human approval. - Use Case: A developer wants to automate asset import in Unity. The Skill inventories existing MCP configurations, proposes a transaction with rollback and health checks, waits for digest confirmation, then applies only the listed actions and records the lock state. ## Quick Start Use the engine-automation skill to plan this editor operation, show the required permissions and rollback steps, and wait for my approval before changing anything.
