winapp-identity Skill
Enable Windows package identity for desktop apps to access Windows APIs like push notifications, background tasks, share target, and startup tasks. Use when adding Windows notifications, background tasks, or other identity-requiring Windows features to a desktop app. Published by microsoft in winappCli.
What is winapp-identity Skill?
Enable Windows package identity for desktop apps to access Windows APIs like push notifications, background tasks, share target, and startup tasks. Use when adding Windows notifications, background tasks, or other identity-requiring Windows features to a desktop app. Published by microsoft in winappCli. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Testing use cases
Technical details
- Install or run with Copy skill directory
When to use winapp-identity Skill
- Use it for testing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/winappCli
- Skill file: .claude/skills/winapp-identity/SKILL.md
What it does
Enable Windows package identity for desktop apps to access Windows APIs like push notifications, background tasks, share target, and startup tasks. Use when adding Windows notifications, background tasks, or other identity-requiring Windows features to a desktop app.
Skill instructions
When to use Use this skill when: - The exe is separate from your app code — e.g., Electron apps where electron.exe is in nodemodules, not your build output - Testing sparse package behavior specifically — AllowExternalContent, TrustedLaunch, etc. - Registering identity without copying files — create-debug-identity leaves the exe in place Prefer winapp run for most frameworks. If your exe is inside your build output folder (.NET, C++, Rust, Flutter, Tauri), use winapp run <build-output instead — it registers a full loose layout package and launches the app, simulating an MSIX install. Use create-debug-identity only when winapp run doesn't fit your scenario. Prerequisites 1. Package.appxmanifest in your project — from winapp init or winapp manifest generate 2. Built executable — the .exe your app runs from What is package identity? Windows package identity enables your app to use restricted APIs and OS integration features: - Push notifications (WNS) - Background tasks - Share target / s
Explore related resources
Frequently asked questions
What is winapp-identity?
winapp-identity is a open-source AI agent skill with Copy skill directory. Enable Windows package identity for desktop apps to access Windows APIs like push notifications, background tasks, share target, and startup tasks.
Who is winapp-identity best for?
winapp-identity is best for reusing agent instructions, scripts, and references, testing workflows.
How do I install winapp-identity?
Install or run winapp-identity using Copy skill directory. Check winapp-identity for the latest setup command.
Is winapp-identity actively maintained?
winapp-identity may need a closer maintenance check before production use.
Auto-fetched from GitHub.
