What problem does it solve? Taking a working Tauri desktop app to end users requires OS-specific installers, cryptographic signing, and a secure auto-update channel — a process that is easy to get wrong and dangerous to skip, since unsigned updates are an attack vector. ## Core Features & Use Cases - Per-OS Installers: Configures bundle.targets for Windows (MSI/NSIS), macOS (.dmg/.app), and Linux (.AppImage/.deb). - Signing & Auto-update: Generates the updater key pair with tauri signer generate, keeps the private key in CI secrets, and publishes signed artifacts plus latest.json to GitHub Releases via tauri-action. - Code Signing Guidance: Handles Windows Authenticode and macOS Developer ID notarization, or warns about SmartScreen/Gatekeeper "unknown publisher" prompts when certificates are absent. - Use Case: You have a tested Tauri app and want users on Windows and Linux to install it and receive verified automatic updates — this Skill configures the keys, CI workflow, and a test release proving the vN → vN+1 update path. ## Quick Start Use the desktop-packaging skill to generate the signed installers and set up auto-update via GitHub Releases for my Tauri app.