winapp-cli

Automate Windows app packaging, signing, and manifest generation via CLI.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/beel-collab/presets.dev --skill winapp-cli-beel-collab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: winapp-cli
Source: https://github.com/beel-collab/presets.dev/tree/main/skills/winapp-cli
Command: npx skills add https://github.com/beel-collab/presets.dev --skill winapp-cli-beel-collab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Windows app development lifecycle requires coordinating SDKs, app identity, manifests, and signing across multiple tools. The winapp-cli CLI centralizes these tasks into a single, consistent workflow, reducing setup time and errors.

Core Features & Use Cases

  • Project Initialization (winapp init): Prepare a workspace with AppxManifest.xml, development certificates, and SDK configuration.
  • MSIX Packaging (winapp pack): Build and package applications into MSIX with optional signing and self-contained deployment.
  • Package Identity for Debugging (winapp create-debug-identity): Attach temporary identity to executables for debugging Windows APIs that require identity.
  • Manifest Management (winapp manifest): Generate and update AppxManifest.xml and related assets from source images.
  • Certificate Management (winapp cert): Create and trust development certificates for signing packages.
  • Package Signing (winapp sign): Sign MSIX packages and executables with PFX certificates.
  • SDK Build Tools Access (winapp tool): Run Windows SDK build tools from any framework or CI environment.

Quick Start

Initialize a Windows app workspace: winapp init Build and package the app into MSIX: winapp pack ./build-output --output MyApp.msix Optionally add a temporary debugging identity and sign: winapp create-debug-identity ./bin/MyApp.exe; winapp sign --cert ./mycert.pfx --cert-password secret ./MyApp.msix

Frequently Asked Questions about winapp-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I package an Electron or Tauri app into MSIX?▼

You can package Electron, Tauri, .NET, or Rust build outputs into MSIX using a dedicated CLI that handles bundling and optional signing. It streamlines Windows app packaging across multiple frameworks.

How do I create and trust a development certificate for signing MSIX packages?▼

You can generate and trust a development certificate for MSIX signing by running a dedicated CLI command that creates the PFX file and configures local trust, automating the certificate management workflow.

Why do I need a temporary package identity for debugging Windows APIs?▼

A temporary package identity is required for debugging because certain Windows APIs reject executables without app identity. Attaching a temporary identity to the executable allows these APIs to function correctly during development.

What's the best way to generate an AppxManifest.xml from source images?▼

The best way to generate an AppxManifest.xml from source images is using a manifest management command that automatically creates and updates the manifest and related package assets, ensuring correct Windows app configuration.

Can I access Windows SDK build tools from a CI environment?▼

Yes, you can access Windows SDK build tools from any CI environment by executing a specific CLI command that exposes and runs the SDK tools, ensuring consistent builds across different frameworks and pipelines.

How do I initialize a Windows app workspace with SDK configuration?▼

You can initialize a Windows app workspace by running a single CLI command that scaffolds the AppxManifest.xml, generates development certificates, and configures the Windows SDK, preparing the project for packaging.