Windows Package Manager Installer

Use this skill to handle Windows software installation requests through package managers instead of manual download flows whenever possible.

Workflow decision tree

1. Identify the user's goal.

   • Install a specific Windows app -> follow Software installation workflow.
   • Install or configure winget / chocolatey / Windows package management environment -> follow Package manager environment workflow.

2. Prefer package managers over direct-download instructions.

   • Check whether the target software is available in winget.
   • Check whether the target software is available in choco.
   • If at least one package manager supports the target, use a package-manager-based solution.

3. Decide package manager priority.

   • Prefer winget first for mainstream desktop apps available from the Microsoft ecosystem.
   • Prefer choco when winget is unavailable, broken, missing the package, or when the package is commonly better supported in Chocolatey.
   • If both are supported, choose the one with simpler and more reliable installation commands for the specific software.

4. If the selected package manager is missing, install it first.

   • Missing winget -> guide the user to install or repair App Installer / winget availability.
   • Missing choco -> install Chocolatey.
   • After Chocolatey installation, configure the Tsinghua mirror.

5. Finish every response with a status-oriented summary.

   • Confirm what is already installed.
   • Confirm what was installed or configured.
   • State the exact command to run next if the user still needs to execute something.
   • End with a clear success/failure-style message in Chinese.

Software installation workflow

Step 1: Normalize the target software

Extract the product name and normalize it to the likely package-manager search term.

Examples:

• "安装 vscode" -> search Visual Studio Code / vscode
• "安装微信" -> search WeChat
• "安装 7zip" -> search 7zip / 7-Zip

When the user provides a vague app name, prefer a best-effort search-and-install approach instead of asking unnecessary follow-up questions.

Step 2: Check package-manager suitability

Use this order of reasoning:

1. Is this clearly a Windows desktop or CLI app? If yes, package managers are likely appropriate.
2. Is the app commonly distributed through winget or choco? If yes, prefer package-manager installation.
3. If the app is not likely to exist in either package manager, say so plainly and fall back to vendor-download guidance.

Step 3: Check environment state

Before giving install commands, reason through these checks in order:

1. Is the machine Windows?
2. Is PowerShell available?
3. Is the session likely elevated as administrator when needed?
4. Is winget available?
5. Is choco available?

Use simple verification commands when helpful: