René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Ecosystem guidance – copilot-plugins vs. awesome-copilot (vs. self-published)?","articleBody":"Hi! I’m the author of `flutter-slipstream`, a plugin and MCP server that gives coding agents runtime inspection and interaction capabilities for Flutter apps. It currently supports Claude Code and Gemini CLI and I'm gearing up to support Copilot.\n\nI'm trying to figure out the best path for distribution and could use some guidance. I like the improved discovery that comes with official marketplaces, but I want to make sure I'm putting the tool in the right place without bottlenecking my release cycle. I have two main questions:\n\n**1. Where does a tool like this belong?**\n\nWhat is the philosophical dividing line between `copilot-plugins` (the official collection) and `awesome-copilot`? Does a tool like Slipstream / MCP for Flutter belong in the official collection, or is that reserved for general-purpose language tools? \n\n**2. How does the release cycle work if I'm listed?**\n\nIf `flutter-slipstream` is included in either `copilot-plugins` or `awesome-copilot`, how are new versions handled? I know you can reference an external repository, but if I push a `v1.1.0` bug fix to my own repo, do I have to wait for a PR review to ungate that release? \n\nAny advice appreciated; thanks!\n","author":{"url":"https://github.com/devoncarew","@type":"Person","name":"devoncarew"},"datePublished":"2026-04-25T20:22:03.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/35/copilot-plugins/issues/35"}