Adrien Clerbois
8e03e6abeb
* feat(plugins): add fluentui-blazor plugin bundling skill and MCP server Bundle the existing skills/fluentui-blazor skill with the official Fluent UI Blazor MCP server (NuGet: Microsoft.FluentUI.AspNetCore.McpServer, launched via dnx) so users get usage guidance plus live component, enum, icon, documentation, and v4-to-v5 migration lookup from a single plugin install. The skill is referenced, not copied; skills/fluentui-blazor/ is unchanged. Regenerated marketplace.json and docs/README.plugins.md via npm run build. * fix(eng): count MCP servers in README plugin item totals update-readme.mjs summed agents, skills and extensions but ignored composition.mcpServers, while generate-website-data.mjs already counted MCP entries. The README and website catalogs therefore disagreed for any plugin declaring an MCP server. Mirror the website generator logic, including the .mcp.json path form and multi-server files, so both catalogs report the same totals. Affects awesome-copilot (4 to 5 items) and fluentui-blazor (1 to 2 items). * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * refactor(plugins): align fluentui-blazor MCP config with the Agent Plugin spec Rename .mcp.json to mcp.json at the plugin root and add the https://agent-plugins.org/schemas/1.0.0/mcp.schema.json reference, matching the Agent Plugin MCP server specification. Drop the manifest mcpServers reference, since clients discover mcp.json without it. Also correct a README claim that the server reads the library version in use. Its documentation is generated at package build time and serves the version it was built against, which is what the Prerequisites section already stated. * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * chore: regenerate plugins README after restoring the mcpServers manifest reference Re-adding extensions[com.github.awesome-copilot].mcpServers to plugin.json makes the item counter include the bundled MCP server, so the fluentui-blazor row goes from 1 to 2 items. The generated file was not refreshed at the time, which failed the validate-readme check. * refactor(plugins): drop the mcpServers manifest reference for fluentui-blazor Clients discover the plugin-root mcp.json on their own, and the com.github.awesome-copilot namespace is stripped from the served manifest by materialize-plugins.mjs, so the field had no effect on the published plugin. Regenerate docs/README.plugins.md in the same commit: the item counter keys off the manifest field, so the row goes back from 2 to 1 item and validate-readme would otherwise fail. * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * refactor(plugins): scope the fluentui-blazor PR to the plugin itself Drop extensions[com.github.awesome-copilot].mcpServers from plugin.json as requested in review: clients discover the plugin-root mcp.json on their own, and materialize-plugins.mjs strips this namespace from the served manifest, so the field never reached clients. Revert the item-counter change to eng/update-readme.mjs and regenerate. Counting MCP servers is a repo-wide concern and now lives in its own pull request, so this one only adds the plugin. --------- Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
🤖 Awesome GitHub Copilot
A community-created collection of custom agents, instructions, skills, hooks, workflows, and plugins to supercharge your GitHub Copilot experience.
Tip
Explore the full collection on the website → awesome-copilot.github.com
The website offers full-text search and filtering across hundreds of resources, plus the Learning Hub for guides and tutorials.
Using this collection in an AI agent? A machine-readable
llms.txtis available with structured listings of all agents, instructions, and skills.
📖 Learning Hub
New to GitHub Copilot customization? The Learning Hub on the website offers curated articles, walkthroughs, and reference material — covering everything from core concepts like agents, skills, and instructions to hands-on guides for hooks, agentic workflows, MCP servers, and the Copilot coding agent.
What's in this repo
| Resource | Description | Browse |
|---|---|---|
| 🤖 Agents | Specialized Copilot agents that integrate with MCP servers | All agents → |
| 📋 Instructions | Coding standards applied automatically by file pattern | All instructions → |
| 🎯 Skills | Self-contained folders with instructions and bundled assets | All skills → |
| 🔌 Plugins | Curated bundles of agents and skills for specific workflows | All plugins → |
| 🍳 Cookbook | Copy-paste-ready recipes for working with Copilot APIs | — |
Install a Plugin
For most users, the Awesome Copilot marketplace is already registered in the Copilot CLI/VS Code, so you can install a plugin directly:
copilot plugin install <plugin-name>@awesome-copilot
If you are using an older Copilot CLI version or a custom setup and see an error that the marketplace is unknown, register it once and then install:
copilot plugin marketplace add github/awesome-copilot
copilot plugin install <plugin-name>@awesome-copilot
Contributing
See CONTRIBUTING.md · AGENTS.md for AI agent guidance · Security · Code of Conduct
The customizations here are sourced from third-party developers. Please inspect any agent and its documentation before installing.
Contributors ✨
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
📚 Additional Resources
- VS Code Copilot Customization Documentation - Official Microsoft documentation
- GitHub Copilot Chat Documentation - Complete chat feature guide
- VS Code Settings - General VS Code configuration guide
™️ Trademarks
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.