$ ~/registry/skill/openai-curated-winui-app

SKILL

winui-app

Name: winui-app
Author: OpenAI

Build, design, and troubleshoot modern WinUI 3 desktop apps with C#.

Stars

★ 23,132

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 22.0k

Summary

This skill appears to be an open-source prompt-oriented development guide, and the system marks it as prompt-only with no secrets or remote endpoints, indicating low overall risk. The README includes local environment setup and scaffolding commands, but these are workflow instructions for development rather than standalone high-risk behavior; the main concern is local machine changes if an agent is allowed to execute them.

CredentialsLow risk

The materials explicitly state that no keys or environment variables are required, and there is no sign of requesting API tokens, account credentials, or other sensitive authentication data, so credential exposure risk is low.

Network egressLow risk

The system checks indicate no remote endpoints, and the materials do not declare sending user data to third-party services. While the described workflow may use winget/dotnet to fetch official dependencies, there is no evidence of exfiltration to unknown or unrelated destinations.

Code executionCaution

The README explicitly includes commands that can run locally, such as `winget configure`, `dotnet new`, and `dotnet build`, which may modify the development environment, install components, and create/build projects. This is standard local execution capability for a development skill and warrants normal caution.

Data accessCaution

The documentation says it will create projects in the user's current workspace, verify generated files, and perform review/refactoring/troubleshooting on local projects, implying read/write access to workspace files. There is no indication of broad access to system data beyond the stated purpose.

Supply chainLow risk

The source is an open-source GitHub repository under openai/skills with strong community adoption (about 22k stars), which are significant risk-reducing factors. Although the license is unspecified and maintenance status is unknown, the supply-chain risk is still low overall due to auditable source code and a high-trust origin.

Recommendations

Only allow the agent to run the local commands in the README if you actually want to provision a WinUI development environment.
Review `config.yaml` before running `winget configure` to confirm the components to be installed or changed are expected.
Limit operations to a dedicated development workspace to avoid accidental changes to existing projects or user directories.
Prefer official Microsoft/.NET dependency sources and keep install/build logs for auditing.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "winui-app" skill from askskill:
1. Download https://raw.githubusercontent.com/openai/skills/main/skills/.curated/winui-app/SKILL.md
2. Save it as ~/.claude/skills/winui-app/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

WinUI App

Use this skill for WinUI 3 and Windows App SDK work that needs grounded setup guidance, app bootstrap, modern Windows UX decisions, or concrete implementation patterns.

Required Flow

Classify the task as environment/setup, new-app bootstrap, design, implementation, review, or troubleshooting.
If the task is about preparing a machine for WinUI, auditing readiness, or creating a brand new app, start with the bundled setup-and-scaffold flow in this skill before broader design, implementation, or troubleshooting work:
- Pick the app name when the request is for a new app.
- Use the exact name the user gave when it is already a safe folder name.
- If the user did not give a name, derive a short PascalCase name from the request and state what you chose.
- Create the project in the user's current workspace unless they asked for another location.
- Do not use --force unless the user explicitly asked to overwrite existing files.
- Run the bundled WinGet configuration from the skill directory so the relative path stays exactly config.yaml:

winget configure -f config.yaml --accept-configuration-agreements --disable-interactivity

Treat the configuration as intended to enable Developer Mode, install or update Visual Studio Community 2026, and install the Managed Desktop, Universal, and Windows App SDK C# components needed for WinUI development.
Assess the configuration result before continuing. Continue on success. If it fails, inspect the output instead of guessing. If the winui template is already available and the toolchain is usable, note the partial failure and continue. If prerequisites are still missing, stop and report the blocker clearly.
Verify the template is available before scaffolding:

dotnet new list winui

For diagnostics-only environment requests, explain that the bundled bootstrap may change the machine and get confirmation before running it. If the user declines changes, use the manual verification guidance in references/foundation-environment-audit-and-remediation.md and summarize readiness under present, missing, uncertain, and recommended optional tools.
For a brand new app, scaffold with dotnet new winui -o <name>. Add template options only when the user asked for them. Supported options: -f|--framework net10.0|net9.0|net8.0, -slnx|--use-slnx, -cpm|--central-pkg-mgmt, -mvvm|--use-mvvm, -imt|--include-mvvm-toolkit, -un|--unpackaged, -nsf|--no-solution-file, --force. Do not invent unsupported flags. If the user asks for packaged behavior, pass --unpackaged false. Otherwise keep the template default.
Verify a new scaffold by confirming the expected project file exists and running dotnet build against the generated .csproj.
Launch a newly scaffolded app through the correct path for its actual packaging model and confirm there is a real top-level window instead of relying only on the launcher process exit code.

Read references/_sections.md, then load only the reference files that match the task.
Make the packaging model explicit before creating or refactoring the app. Default to packaged for Store-like product workflows and Visual Studio deploy/F5 flows. Default to unpackaged when the user expects repeatable CLI build-and-run loops or direct .exe launches after each change.
When the task is an opaque XAML compiler failure such as MSB3073 or XamlCompiler.exe, read references/foundation-template-first-recovery.md and simplify back toward the current dotnet new winui scaffold for the chosen packaging model before inventing custom recovery structure.

…

View full docs ↗

OpenAIGet→

// similar tools

SKILL

★257

win-dev-skills

Build Windows apps with WinUI 3 and the Windows App SDK.

microsoftGet→

SKILL

using-guigui

Helps you build and debug Guigui GUI components and interactions.

guigui-guiGet→

MCP

windows-gui-mcp

Automate Windows desktop apps with reliable UI control discovery and action verification.

—Get→

SKILL

★23k

chatgpt-apps

Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications.

OpenAIGet→

SKILL

★440

create-code-app

Build and deploy Power Apps code apps with React and Vite quickly.

microsoftGet→

MCP

MCP Apps Starter Kit

Run interactive in-app tools in Claude Desktop for planning, tracking, and decisions.

—Get→

$ loading_

Please install the "winui-app" skill from askskill: 1. Download https://raw.githubusercontent.com/openai/skills/main/skills/.curated/winui-app/SKILL.md 2. Save it as ~/.claude/skills/winui-app/SKILL.md 3. Reload skills and tell me it's ready

// docs

WinUI App

Use this skill for WinUI 3 and Windows App SDK work that needs grounded setup guidance, app bootstrap, modern Windows UX decisions, or concrete implementation patterns.

Required Flow

Classify the task as environment/setup, new-app bootstrap, design, implementation, review, or troubleshooting.
If the task is about preparing a machine for WinUI, auditing readiness, or creating a brand new app, start with the bundled setup-and-scaffold flow in this skill before broader design, implementation, or troubleshooting work:
- Pick the app name when the request is for a new app.
- Use the exact name the user gave when it is already a safe folder name.
- If the user did not give a name, derive a short PascalCase name from the request and state what you chose.
- Create the project in the user's current workspace unless they asked for another location.
- Do not use --force unless the user explicitly asked to overwrite existing files.
- Run the bundled WinGet configuration from the skill directory so the relative path stays exactly config.yaml:

winget configure -f config.yaml --accept-configuration-agreements --disable-interactivity

Treat the configuration as intended to enable Developer Mode, install or update Visual Studio Community 2026, and install the Managed Desktop, Universal, and Windows App SDK C# components needed for WinUI development.
Assess the configuration result before continuing. Continue on success. If it fails, inspect the output instead of guessing. If the winui template is already available and the toolchain is usable, note the partial failure and continue. If prerequisites are still missing, stop and report the blocker clearly.
Verify the template is available before scaffolding:

dotnet new list winui

For diagnostics-only environment requests, explain that the bundled bootstrap may change the machine and get confirmation before running it. If the user declines changes, use the manual verification guidance in references/foundation-environment-audit-and-remediation.md and summarize readiness under present, missing, uncertain, and recommended optional tools.
For a brand new app, scaffold with dotnet new winui -o <name>. Add template options only when the user asked for them. Supported options: -f|--framework net10.0|net9.0|net8.0, -slnx|--use-slnx, -cpm|--central-pkg-mgmt, -mvvm|--use-mvvm, -imt|--include-mvvm-toolkit, -un|--unpackaged, -nsf|--no-solution-file, --force. Do not invent unsupported flags. If the user asks for packaged behavior, pass --unpackaged false. Otherwise keep the template default.
Verify a new scaffold by confirming the expected project file exists and running dotnet build against the generated .csproj.
Launch a newly scaffolded app through the correct path for its actual packaging model and confirm there is a real top-level window instead of relying only on the launcher process exit code.

Read references/_sections.md, then load only the reference files that match the task.
Make the packaging model explicit before creating or refactoring the app. Default to packaged for Store-like product workflows and Visual Studio deploy/F5 flows. Default to unpackaged when the user expects repeatable CLI build-and-run loops or direct .exe launches after each change.
When the task is an opaque XAML compiler failure such as MSB3073 or XamlCompiler.exe, read references/foundation-template-first-recovery.md and simplify back toward the current dotnet new winui scaffold for the chosen packaging model before inventing custom recovery structure.

…

View full docs ↗