Distributing Agents with Plugins
Distribution of custom agents to teams is accomplished through plugins, which package agents, skills, and MCP configurations in a shared repository that team members can install with one click in GitHub Copilot or Claude Code. The post explains how to set up marketplace and plugin manifests to enable seamless sharing across ecosystems without manual file copying.

post Tech Adventures in Business Central | AL Development & AI Solutions
"The exact same plugin repo works for both GitHub Copilot and Claude Code. One repo, two ecosystems."
Key points
- A plugin bundles agents, skills and MCP config you already have into a repo that teammates can install in one step, so nobody copies files by hand.
- One repo serves both GitHub Copilot and Claude Code, using a marketplace manifest for each tool at .github/plugin/marketplace.json and .claude-plugin/marketplace.json.
- Each plugin manifest only needs a name, description, version and author. Both tools read the shared agents/ and skills/ folders by default.
- Do not split agents into a folder per tool: the Copilot extension in VS Code merges every plugin.json and installs the agents twice. Put both tools’ names in one tools array instead.
- Each skill needs its own subfolder directly under skills/, and deeper nesting of skill folders does not work. Teammates pick up changes with one sync command, with no reinstall.
Quotes
- “The exact same plugin repo works for both GitHub Copilot and Claude Code. One repo, two ecosystems.” (Demonstrates the efficiency of plugin-based distribution, eliminating the need to maintain separate repositories for different tools)
Context
- Features: plugin marketplace installation, agent distribution, skill sharing, MCP configuration sharing, cross-ecosystem plugin support
Source: Tech Adventures in Business Central, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.