Ship Signed Windows Desktop Apps

    1

    Integrate Azure Artifact Signing and signed auto-updates into Tauri, Electron, or native Windows desktop applications.

    $29

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Ship Signed Windows Desktop Apps

    Example session with this skill installed

    I'm getting 'VerifiableCredential card missing' in Authenticator while trying to set up Azure Trusted Signing for my Tauri app. How do I fix this and wire the signing into my build?

    • Read your context and instructions
    • Compiled the ship signed windows

    The "card missing" error occurs because you haven't generated a Verified ID with a Microsoft partner yet. You must complete the ID and selfie check before the presentation request will work.

    Azure Signing Integration

    StepActionResolution / Command
    Identity FixGet Verified IDOn the Azure verification page, select "Don't have a Verified ID? Get verified here" to scan the partner QR.
    Identity FixShare CardAfter the selfie check, scan the original Azure QR again to share the credential.
    Tauri ConfigUpdate tauri.conf.jsonAdd artifact-signing-cli to your bundle > windows > signCommand.
    AuthSet Env VarsDefine AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, and AZURE_TENANT_ID.
    {
      "bundle": {
        "windows": {
          "signCommand": "artifact-signing-cli -e https://neu.codesigning.azure.net/ -a YourAccount -c YourProfile -d \"My App Name\" %1"
        }
      }
    }
    

    Next steps

    1. Install the CLI tool using cargo install artifact-signing-cli.
    2. Once identity is Completed, create a Public Trust certificate profile in the Azure portal.
    3. Run a test build and verify the output with Get-AuthenticodeSignature to ensure the publisher name matches your legal entity.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Code-signing a Windows app with Azure Artifact Signing is cheap, but the path is full of traps: identity validation stuck on "Action Required", a "card missing" error in Microsoft Authenticator, 404s on the Verified ID QR code, emails sent to the wrong mailbox, certificateThumbprint that never works, and installers that are signed while the app inside is not.

    This skill walks your agent through the whole path, from prerequisites to a release that is signed, timestamped and verified, then adds a Tauri 2 auto-updater with signed manifests and tests it, including a forged-manifest test.

    Includes: a troubleshooting table for identity validation, a signCommand setup for Tauri, verify-signatures.ps1 (checks status, signer and timestamp, and fails the build if anything is unsigned), make-latest-json.mjs, templates and a release checklist.

    Includes an EXPERT.md reference (exact parameters, thresholds, failure diagnosis). Tested scripts: verify-signatures.ps1, make-latest-json.mjs.

    Built from a real release shipped in 2026.

    Requires paid Azure subscription. User must manually handle identity verification and secret entry. Geographic restrictions apply for public trust certificates.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 28 days ago

    Requires

    tauri
    Node.js

    Permissions

    Read Files
    Write Files
    Listed28 days ago

    What's inside

    Frequently Asked Questions

    Partly, and the skill is explicit about the limit. A valid Azure Artifact Signing signature removes the "Unknown Publisher" dialog and lets Windows name you as the publisher. SmartScreen, however, is also reputation-based: a brand-new publisher can still see a warning for a while even when everything is signed and timestamped correctly. Reputation builds on the publisher identity as downloads accumulate. The skill tells you this up front rather than promising a warning-free first release.

    Yes. It includes specific configuration steps for Tauri 2's signCommand, Electron's build pipeline, and any other .exe signed with signtool.exe, including .NET applications.

    You will receive a step-by-step implementation guide, pre-configured CLI commands for Azure integration, PowerShell verification scripts, and a troubleshooting map for identity validation.

    The skill focuses on the technical integration and automation; users must still have a paid Azure subscription and pass Microsoft's standard identity verification process.

    Yes. The skill gives the exact workflow for generating the Tauri updater signing key, signing the update artifact, and publishing the manifest (latest.json), plus a forged-manifest test so you can prove a tampered update is actually rejected.

    Any agent that follows the SKILL.md standard and can run CLI commands and edit configuration files - Claude Code, Codex CLI, Cursor, GitHub Copilot and Gemini CLI among them. The signing steps are ordinary command-line and config work, so nothing is tied to one agent.

    New in DevOps & Cloud