winapp-cli

Initialize Windows app projects, generate manifests, and package MSIX files.

37.6k|4.7k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill winapp-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: winapp-cli
Source: https://github.com/github/awesome-copilot/tree/main/skills/winapp-cli
Command: npx skills add https://github.com/github/awesome-copilot --skill winapp-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Windows App Development CLI (winapp) provides a streamlined workflow for initializing Windows app projects, generating manifests, managing development certificates, and packaging apps into MSIX packages.

Core Features & Use Cases

  • Project initialization and SDK setup for Windows apps (winapp init)
  • MSIX packaging and signing (winapp pack, winapp sign)
  • Managing package identity for debugging and Windows APIs (winapp create-debug-identity)
  • Manifest generation and asset management (winapp manifest)
  • Access to Windows SDK build tools from any framework (winapp tool)
  • Cross-platform app support (Electron, Rust, Tauri, Qt)

Quick Start

Install the winapp CLI via Winget or npm, initialize a project with winapp init, then build and package with winapp pack ./build-output --output 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 a Windows app into MSIX format?

MSIX packaging bundles your Windows app with manifests and signing for modern distribution. Use winapp pack to convert your build output into an MSIX package, then sign it with winapp sign to prepare it for deployment or store submission.

Can I use winapp-cli with Electron, Rust, or Tauri apps?

Yes, winapp-cli supports cross-platform frameworks including Electron, Rust, Tauri, and Qt. Initialize your project with winapp init, then use the same packaging and signing workflow regardless of your framework.

What do I need to do before packaging my app with winapp?

Install winapp via Winget or npm, ensure you're on Windows 10 or later, run winapp init to set up your project and SDK, generate a manifest with winapp manifest, and prepare your build output directory before packaging.

How do I create a debug identity for Windows APIs?

Use winapp create-debug-identity to generate a package identity for development and testing. This identity allows your app to access Windows APIs and run locally before signing for distribution.

Do I need to manage certificates separately for MSIX signing?

winapp-cli integrates certificate management into its workflow. The winapp sign command handles signing certificates for MSIX packages, eliminating the need to manage signing separately outside the CLI.

What if I need to access Windows SDK build tools from my framework?

Use winapp tool to access Windows SDK build tools directly from any framework without manual SDK configuration. This streamlines cross-platform development by centralizing tool access through the CLI.