Bring an existing agent plugin into Work IQ Developer Tools (WIQD) and the plugin registry or create a new plugin to utilize the full Microsoft Copilot packaging workflow.A plugin gives Microsoft Copilot new ways to get work done. It packages one or more capabilities, such as skills, MCP servers, or agents, so Copilot can support the workflows that matter to your organization.Starting fresh? Work IQ Developer Tools (WIQD) can help you turn a business problem or inefficient workflow into a plugin that extends what Copilot can do.Most developers will not start with an empty folder. You may already have skills that capture how work gets done, an MCP server that connects to your systems, or an agent built for another client. WIQD helps you use that existing work as the starting point for a Microsoft Copilot plugin.Your first choice is straightforward: import or create.Once you have chosen your starting point, tell WIQD what you want the plugin to do through your preferred coding harness. We recommend GitHub Copilot. Whether you import existing work or create something new, you use the same WIQD command surface.Preview: The wiqd plugin command surface is currently public preview and may change.Start with what you haveIf your existing plugin uses the Agent Plugins format, you can import it into WIQD. The format packages skills and MCP server configurations. WIQD brings the supported parts into a project you can inspect and build on, rather than asking you to recreate them by hand.Install WIQD, then import your plugin:wiqd plugin import --path ./my-agent-plugin \ --privacy-url https://contoso.com/privacy \ --terms-url https://contoso.com/termsAfter import, check what WIQD brought into the project. You can then refine how those capabilities work in Microsoft Copilot before moving on to validation and packaging.Don’t have a plugin? Describe oneStart with the work you want Copilot to do. The WIQD plugin for GitHub Copilot CLI lets you describe that outcome in natural language, then uses WIQD commands to build the plugin and reports each step as it goes.For example, you could ask:Create a standalone plugin called Triage Helper. Add a skill that triages incoming customer issues and connect it to our incident-management MCP server.Behind that request, WIQD can use commands like these:wiqd plugin create --name "Triage Helper"wiqd plugin add skill --name "Triage Issues"wiqd plugin add connector --name "Incident Management" \ --description "Triage and manage customer incidents" \ --url https://incidents.contoso.com/mcpYou can go from an idea to a plugin project without learning the command tree first. WIQD reports what it ran as you go, and those same commands are available when you want to take direct control from the terminal.Build a plugin directly from the terminalThe WIQD commands used by the GitHub Copilot CLI plugin are also available directly in your terminal for local development and repeatable automation. Install WIQD before following this Bash example.Create triage-helper, scaffold a skill for incoming issues, and register the incident-management MCP server:# Create the pluginwiqd plugin create --name triage-helpercd triage-helper# Add the capabilities it needswiqd plugin add skill --name "Triage Issues"wiqd plugin add connector \ --name "Incident Management" \ --description "Triage and manage customer incidents" \ --url https://incidents.contoso.com/mcpThe commands create the project structure; you still need to write the skill’s triage instructions and configure any authentication the MCP server requires. Once the plugin is ready, the next steps are the same whether you built it via CLI, described it in natural language, or imported existing work.Validate and package your pluginWhether you imported a plugin or created one through natural language or WIQD commands, continue from the plugin project directory. Check the project locally before provisioning anything in Microsoft 365:# Check declarative-agent artifacts, if presentwiqd plugin validateThis is an offline check, not a full review of the plugin. It does not inspect skill content or the top-level app manifest, so a clean result is not an all-clear for a skill-and-connector plugin.Next, sign in and provision the Microsoft 365 resources. Provisioning changes your environment and supplies information WIQD needs to build the package:wiqd auth login --interactivewiqd plugin provisionwiqd plugin packagewiqd plugin validate --mode deepDeep validation checks the built Microsoft 365 app package. That package brings the skill and MCP connector configuration, plus a declarative agent if your scenario needs one, into a single unit your team can version, distribute, and support.A validated package does not guarantee the same experience on every Copilot surface. Check that each surface supports the capabilities your plugin needs before you share or publish it.Get your plugin to usersFor use within your organization, WIQD can share the plugin with specific users or across your tenant:wiqd plugin share --scope users --email developer@contoso.com# Or make it available across the tenantwiqd plugin share --scope tenantFor an ISV reaching customers outside its organization, the package is the plugin you submit and support, rather than a collection of skills, manifests, and connector settings customers must assemble themselves. Take that package to Partner Center to submit it for Microsoft certification, and address any feedback before release. WIQD prepares the package, but Partner Center handles public submission and certification.Build once. Validate for each surface.The Agent Plugins format gives skills and MCP server configurations a portable shape. WIQD can bring supported existing work into a Microsoft 365 plugin project or help you create one, then package it for distribution. Microsoft Copilot's plugin registry gives participating Microsoft experiences a managed plugin record to discover.One package does not mean one runtime. Each Copilot experience determines which capabilities it supports, how users acquire the plugin, and how those capabilities run. A plugin with a skill, an MCP connector, and an agent may not deliver the same experience on every surface.Bring forward the work you already have, or build the plugin your scenario needs. Either way, you have one package to carry across participating experiences, with compatibility checked where your users will actually use it.Get started Get started with WIQD Review the Agent Plugins specification. Follow the WIQD plugin walkthrough. Explore the wiqd plugin command reference. Follow the Microsoft 365 Copilot publishing overview and Partner Center marketplace submission guidance after WIQD packages and validates the plugin.