⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
code-quality
Statically check changed C# against the same deterministic rules github-code-quality[bot] runs on pull requests, so a contributor can fix likely findings before opening the PR and keep the bot's inline comments to a minimum. Activate when a contributor asks to "check code quality", "run code quality on my changes", "will the code quality bot complain", "pre-check before I open the PR", "code quality check", or similar. Scoped to C#. Reads the diff and compares it against the enumerated csharp-code-quality rule set below — no CodeQL download or build required. This is a fast approximation of a dataflow engine, not a reproduction; report accordingly. Does NOT apply fixes unless explicitly asked.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
winapp CLI
[!IMPORTANT] :warning: Status: Public Preview — The Windows App Development CLI (winapp CLI) is experimental and in active development. We'd love your feedback! Share your thoughts by creating an issue.
[!NOTE] The
mainbranch contains work that is in active development. Documentation, features, and behavior here may differ from what is publicly released. For the latest stable version, see the latest release. To try the newest in-progress build, see Install from latest build below.
The Windows App Development CLI (winapp CLI) is a single command-line interface for managing Windows SDKs, packaging, generating app identity, manifests, certificates, and using build tools with any app framework. This tool bridges the gap between cross-platform development and Windows-native capabilities. Whether you're building with .NET/Win32, CMake, Electron, or Rust, this CLI gives you access to:
- Modern Windows APIs - Windows App SDK and Windows SDK with automatic setup and code generation
- Package Identity - Debug and test by adding package identity without full packaging in a snap
- MSIX Packaging - App packaging with signing and Store readiness
- Developer Tools - Manifests, certificates, assets, and build integration
Perfect for:
- Cross-platform developers using frameworks like Qt or Electron wanting native Windows features or targeting Windows
- Developers who love their current tools and want to build Windows apps from VS Code, or any other editor
- Developers crafting CI/CD pipelines to automate building apps for Windows
🤔 Why?
Many Windows APIs require your app to have package identity, enabling you to leverage some of the OS components Windows offers, that you wouldn't otherwise have access to. With identity, your app gains access to user-first features like notifications, OS integration, and on-device AI.
Our goal is to support developers wherever they are, with the tools and frameworks they already use. Based on feedback from developers shipping cross-platform apps on Windows, we built this CLI to streamline integrating with the Windows developer platform - handling SDK setup, header generation, manifests, certificates, and packaging in just a few commands:
Few examples of what package identity and MSIX packaging unlocks:
- Interactive native notifications and notification management
- Integration with Windows Explorer, Taskbar, Share sheet, and other shell surfaces
- Protocol handlers (
yourapp://URIs) - Web-to-app linking (
yoursite.comopens your app) - On-device AI (Local LLM, Text and Image AI APIs)
- Custom CLI commands via AppExecutionAlias
- Controlled access to camera, microphone, location, and other devices (with user consent)
- Background tasks (run when app is closed)
- File type associations (open
.xyzfiles with your app) - Startup tasks (launch at Windows login)
- App services (expose APIs to other apps)
- Clean install/uninstall & auto-updates
✏️ Get started
Checkout our getting started guides for step by step instructions of how to setup your environment, generate manifests, assets, and certificate, how to debug APIs that require package identity, and how to MSIX package your app.
// HOW IT'S BUILT
KEY FILES