Question: preferred submission path for a community Copilot plugin like StitchFlow?

[yshishenya]

Context

I maintain StitchFlow: https://github.com/yshishenya/stitchflow

It provides a GitHub Copilot plugin manifest at .github/plugin/plugin.json, plus a canonical skill (stitchflow) and a local Stitch workflow for generating UI screens, variants, HTML, and screenshots.

Question

Your CONTRIBUTING guide says external plugins from remote sources are not accepted in the normal way unless they are Microsoft or GitHub managed.

What is the preferred path for a community plugin like this?

Options I am considering:

• contributing it as a full in-repo plugin contribution
• contributing it as a skill instead of a plugin
• waiting for another supported marketplace path

Why I am asking

I do not want to submit something in the wrong format and create review noise. If there is a recommended path for a community Copilot plugin with a public GitHub repo and Apache-2.0 license, I am happy to follow it.

[aaronpowell]

One option is always to publish your own marketplace, it's a matter of putting an appropriately structured marketplace.json file in the .github/plugins folder (and the .claude-code/plugins IIRC), then people can add your marketplace and plugin(s) from there.

If the desire is to leverage awesome copilot as a marketplace/discovery mechanism, then you would need to contribute the skill (and associated files, such as the CLI tool you have) into the awesome copilot repo so that it can be surfaced as a plugin via our marketplace.