What problem does it solve? Shipping a Godot digital-twin viewer to a site usually means re-exporting the whole project every time the model, binding map, or live data source changes. This Skill packages the export-safe viewer together with its data tree as one retargetable deployable, so a site swaps models or repoints its live URL with a text edit instead of a rebuild. ## Core Features & Use Cases - Data-beside-build packaging: Runs tools/twin_ship.sh to export the desktop build headless, stage the model, property sidecar, binding map, and recordings in a data/ folder beside the executable (never baked into the pck), rewrite viewer.cfg to data-relative paths, boot the binary as a smoke gate, and zip the artifact deterministically. - Retargeting without re-export: The --retarget mode swaps the model, binding map, or recording in an already-shipped artifact while asserting the executable mtime and url= line stay untouched. - Per-platform guidance: Covers the recommended export_presets.cfg (universal macOS binary, exclude_filter keeping data out of the pck), macOS .app data placement with the honest unsigned/Gatekeeper warning, Linux and Windows layouts, and loud cross-platform smoke SKIPs. - Use Case: A plant digital twin passes its verify gates and a stakeholder needs a runnable demo on their own Mac with no Godot install — run twin_ship.sh --preset macOS, hand over the zip, and later retarget it to a different building model without re-exporting. ## Quick Start Ask the agent to ship the verified twin viewer as a deployable zip for macOS using twin_ship.sh with the macOS export preset.