Skip to content

[Feature]: Proposal: list both agent plugins everywhere, and give WinUI developers both #1292

Open

Description

@niels9001

Is your feature request related to a problem? Please describe.

This repo ships two agent plugins:

  • winui (plugins/winui): the winui-dev agent and 7 skills for building WinUI 3 apps: create, design, build and run, test, review, package, and migrate from WPF.
  • winappcli (plugins/winapp): the winapp agent and 14 skills for WinApp CLI work in any framework: packaging, signing, package identity, manifests, Windows API lookup, UI automation, WinUI DevTools, performance, and Windows Sandbox.

WinUI developers get the most from installing both, because three WinUI skills live in winappcli: winui-devtools, winapp-performance, and winapp-find-ui. Three things get in the way:

  1. The plugins aren't listed everywhere, and the existing listings point at old sources.

    Directory Who sees it winui today winappcli today
    Awesome Copilot (github/awesome-copilot) Built into Copilot CLI, the GitHub Copilot app, and VS Code Listed, but installs v0.7.1 from microsoft/win-dev-skills Listed, pinned to an untagged commit
    GitHub's first-party marketplace (github/copilot-plugins) Built into VS Code. Copilot CLI and app users must add it. Add WinUI and WinApp CLI plugins github/copilot-plugins#88, open since Sep 9 without a maintainer review, installs v0.6.1 from win-dev-skills Not submitted
    Anthropic's directory Claude Code, claude.ai, Cowork Submitted Sep 9 through a form Anthropic has since retired, pointing at a folder that no longer exists Not submitted
    OpenAI's directory Codex, ChatGPT Not submitted Not submitted
    Cursor Marketplace Cursor Not submitted. The earlier blocker, a bundled DLL (Cursor: resolve binary-policy blocker and submit WinUI plugin win-dev-skills#181), is gone: plugins/ contains no binaries. Not submitted

    This repo's own marketplaces already list both plugins for Copilot CLI, Claude Code, and Codex, but users only find them if they add microsoft/WinAppCli.

  2. Installing one plugin never installs the other. Users have to know about the second plugin and run a second command.

  3. The winui-dev agent doesn't mention winappcli's skills. The winapp agent already sends WinUI app work to winui's skills when that plugin is installed, but not the other way around.

Describe the solution you'd like

1. List both plugins in every directory above, pinned to the next release. It's the first release that contains plugins/winui; #1260 tracks moving the existing listings to it. Each directory needs its own step:

2. Get WinUI developers both plugins. Only Claude Code can install a second plugin automatically:

Host Can installing one plugin add the other?
Claude Code Yes, through a dependencies entry in the plugin manifest (tested, see below)
claude.ai and Cowork No. Users turn on each plugin.
Copilot CLI, the GitHub Copilot app, and VS Code No. Their docs describe no plugin dependencies, and each install command takes one plugin.
Codex and ChatGPT No. Codex's plugin manifest has no dependency field.
Cursor No. An organization's team marketplace can install plugins by default for its members.

Options:

  • A. A Claude Code dependency, plus install prompts and paired install commands everywhere else (recommended).
    • winui declares "dependencies": ["winappcli"], so in Claude Code, claude plugin install winui@winappcli installs both.
    • Every listing and docs page shows both install commands together:
      copilot plugin marketplace add microsoft/WinAppCli
      copilot plugin install winappcli@winappcli
      copilot plugin install winui@winappcli
      
    • When winappcli's skills aren't available, the winui-dev agent and the winui-setup skill tell the user how to install it.
    • Cost: one manifest line, a few lines in the agent and setup skill, and docs. Claude Code users who install winui also get winappcli, which adds about 1,100 tokens of skill and agent descriptions to each session.
  • B. Paired install commands in docs and listings only. Show both install commands together everywhere, and change no plugin files. It's the cheapest option, but users have to notice the second command, and the agents don't help.
  • C. Move the three WinUI-only skills (winui-devtools, winapp-performance, winapp-find-ui) into winui. winui then covers WinUI work on its own, and winappcli adds packaging, signing, identity, and UI automation for any framework. It reshapes both plugins, and two of these skills are [Feature]: Build public, evidence-backed benchmarks for the skills and tooling #1179 pilot skills.

I recommend A. It matches the goal of WinUI developers using both plugins, it's a single install wherever a host allows it, and it keeps each plugin's current shape.

3. Check whether both beats winui alone. The app benchmark's cli-plus-plugins setup already loads both plugins (#1179). Add a setup that loads only winui, and compare the two.

Additional context

Tested: Claude Code installs both from one command. In a temporary copy of plugins/ with an isolated Claude config folder, using Claude Code 2.1.258, I added "dependencies": ["winappcli"] to plugins/winui/.claude-plugin/plugin.json:

> claude plugin validate --strict plugins\winui
√ Validation passed
> claude plugin install winui@winappcli
√ Successfully installed plugin: winui@winappcli (scope: user) (+ 1 dependency: winappcli)

Both plugins were then enabled. A bare dependency name resolves in the same marketplace. So this works in this repo's marketplace, and it should work in Anthropic's directory once both plugins are listed there (not tested).

Decisions needed

  1. Which option (A, B, or C) gives WinUI developers both plugins.
  2. Who submits for Microsoft to Anthropic and OpenAI. The first organization to submit a plugin folder to Anthropic keeps that listing, and OpenAI requires a business-verified organization.
  3. Whether Anthropic's listings follow main or release tags (also in [Feature]: Point the public winui and winappcli plugin listings at this repo's releases #1260).

Related: #1260, #1291, #1272, #1179, #812, #813, microsoft/win-dev-skills#158, microsoft/win-dev-skills#181, github/copilot-plugins#88.

Sources: Claude Code plugin dependencies, Copilot CLI plugin reference, Cursor plugins, OpenAI plugin submission.

Activity

  1. Jaylyn-Barbee commented on Nov 13, 2026

    @Jaylyn-Barbee
    Contributor

    Blocker for the OpenAI and Cursor listings: we need an account to submit the plugins from.

    • OpenAI (platform.openai.com/plugins): submissions come from a business-verified organization, so this needs a Microsoft organization account.
    • Cursor (cursor.com/marketplace/publish): the application needs a publisher account.

    Until someone owns these accounts, neither plugin can be submitted to either directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions