Tauri Build — production builds, signing and distribution for Tauri v2

Prerequisites: a Tauri v2 project (or a planned Tauri app) and a target platform; signing identities for signed releases (Apple Developer account for macOS/iOS, code-signing certificate for Windows) Install "Tauri Build — production builds, signing and distribution for Tauri v2" for me. It gives my agent @full-stack-skills' release workflow: detect build/release/signing/distribution intent via trigger phrases, identify target platforms and packaging formats, configure the release build and signing requirements, produce per-platform installers or app bundles (dmg, Windows installer, AppImage, deb/rpm, Flatpak, Snap, macOS bundle, app-store/mobile packages), and validate release artifacts and update channels, with the official Tauri v2 docs as references. Apache-2.0 licensed. Repository: https://github.com/full-stack-skills/tauri-skills/blob/main/skills/tauri-build/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "tauri-build". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. create a Tauri v2 project if needed, set up my signing identities/accounts for the target platforms; nothing else — it's a guidance skill). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.