How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

Create Cowork Plugin Package - Prompt

Name: Create Cowork Plugin Package
Author: jnPiyush

Prompt file imported from jnPiyush/AgentX (.github/prompts/cowork-plugin-create.prompt.md). Fill in {{name}}, {{capability}}, {{skills}}, {{connector}}, {{outputDir}} before use. Copyright stays with the author.

Create Cowork Plugin Package

Inputs

{{name}}: Cowork plugin name
{{capability}}: Business capability the plugin supports
{{skills}}: Specialized skills to bundle, or none for a connector-only package
{{connector}}: MCP connector requirement, or none
{{outputDir}}: Package output directory

Requirements

Read .github/skills/development/cowork-plugin-creator/SKILL.md in full before authoring files.
Decompose {{capability}} into non-overlapping skills. Each skill owns one stage, task, or domain and defers explicitly at its boundaries. The package must declare at least one skill or at least one connector.
Create {{outputDir}}/<plugin-name>/manifest.json with manifestVersion, a stable GUID id, version, developer, name, description, icons, agentSkills, and any agentConnectors. Do not add fields outside the supported schema.
Add color.png at 192x192 pixels and outline.png at 32x32 pixels, and reference both from icons.
Create skills/<skill-name>/SKILL.md for every skill. The frontmatter name must be kebab-case and match its folder name exactly, and the description must contain realistic trigger phrases.
Register every skill folder in agentSkills. Populate references/ and scripts/ inside a skill folder only when that skill needs them.
When {{connector}} is not none, add an agentConnectors entry with an HTTPS mcpServerUrl, a packaged mcpToolDescription file under tools/, and an authorization block whose type is None, OAuthPluginVault, ApiKeyPluginVault, or DynamicClientRegistration. Every type except None requires a vault referenceId. Never embed credentials in the package.
Do not leave TODO markers, generic placeholders, secrets, personal data, customer-sensitive data, or unsupported claims.
Require human review before sending, publishing, deleting, approving, or taking another consequential action.
Run .github/skills/development/cowork-plugin-creator/scripts/New-CoworkPluginPackage.ps1 against the completed source directory.
Verify the zip contains manifest.json, both icons, and every registered skill folder at the archive root with no wrapper directory.
Return the generated zip path and a concise list of packaged files. The final deliverable must be the zip file, not only a Markdown response or source directory.

Output Format

## Cowork Plugin Package

**Plugin**: <name>
**Capability**: <capability>
**Archive**: [<archive-name>.zip](<workspace-relative-path>)

### Package Contents

* `manifest.json`
* `color.png`, `outline.png`
* `skills/<skill-name>/SKILL.md` (when a skill is declared)
* `tools/<tool-description>.json` (when a connector is declared)

### Skills

Omit this section for a connector-only package.

| Skill | Purpose | Triggers |
|-------|---------|----------|
| <skill-name> | <purpose> | <trigger phrases> |

### Next Steps

1. Upload the package for personal testing in Microsoft 365 Copilot Cowork.
2. Validate skill routing, connector access, and approval prompts.
3. Publish through Microsoft 365 administration after business, security, and privacy review.

Constraints

Never fabricate connector endpoints, tool names, credentials, or customer data
Never wrap package contents in an extra parent directory inside the zip
Ask only for genuinely missing essentials, then proceed

Install Create Cowork Plugin Package and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Create Cowork Plugin Package ## Inputs * `{{name}}`: Cowork plugin name * `{{capability}}`: Business capability the plugin supports * `{{skills}}`: Specialized skills to bundle, or `none` for a connector-only package * `{{connector}}`: MCP connector requirement, or `none` * `{{outputDir}}`: Package output directory ## Requirements 1. Read `.github/skills/development/cowork-plugin-creator/SKILL.md` in full before authoring files. 2. Decompose `{{capability}}` into non-overlapping skills. Each skill owns one stage, task, or domain and defers explicitly at its boundaries. The package must declare at least one skill or at least one connector. 3. Create `{{outputDir}}/<plugin-name>/manifest.json` with `manifestVersion`, a stable GUID `id`, `version`, `developer`, `name`, `description`, `icons`, `agentSkills`, and any `agentConnectors`. Do not add fields outside the supported schema. 4. Add `color.png` at 192x192 pixels and `outline.png` at 32x32 pixels, and reference both from `icons`. 5. Create `skills/<skill-name>/SKILL.md` for every skill. The frontmatter `name` must be kebab-case and match its folder name exactly, and the description must contain realistic trigger phrases. 6. Register every skill folder in `agentSkills`. Populate `references/` and `scripts/` inside a skill folder only when that skill needs them. 7. When `{{connector}}` is not `none`, add an `agentConnectors` entry with an HTTPS `mcpServerUrl`, a packaged `mcpToolDescription` file under `tools/`, and an `authorization` block whose `type` is `None`, `OAuthPluginVault`, `ApiKeyPluginVault`, or `DynamicClientRegistration`. Every type except `None` requires a vault `referenceId`. Never embed credentials in the package. 8. Do not leave TODO markers, generic placeholders, secrets, personal data, customer-sensitive data, or unsupported claims. 9. Require human review before sending, publishing, deleting, approving, or taking another consequential action. 10. Run `.github/skills/development/cowork-plugin-creator/scripts/New-CoworkPluginPackage.ps1` against the completed source directory. 11. Verify the zip contains `manifest.json`, both icons, and every registered skill folder at the archive root with no wrapper directory. 12. Return the generated zip path and a concise list of packaged files. The final deliverable must be the zip file, not only a Markdown response or source directory. ## Output Format ```markdown ## Cowork Plugin Package **Plugin**: <name> **Capability**: <capability> **Archive**: [<archive-name>.zip](<workspace-relative-path>) ### Package Contents * `manifest.json` * `color.png`, `outline.png` * `skills/<skill-name>/SKILL.md` (when a skill is declared) * `tools/<tool-description>.json` (when a connector is declared) ### Skills Omit this section for a connector-only package. | Skill | Purpose | Triggers | |-------|---------|----------| | <skill-name> | <purpose> | <trigger phrases> | ### Next Steps 1. Upload the package for personal testing in Microsoft 365 Copilot Cowork. 2. Validate skill routing, connector access, and approval prompts. 3. Publish through Microsoft 365 administration after business, security, and privacy review. ``` ## Constraints * Never fabricate connector endpoints, tool names, credentials, or customer data * Never wrap package contents in an extra parent directory inside the zip * Ask only for genuinely missing essentials, then proceed

{ "prompt": "# Create Cowork Plugin Package\n\n## Inputs\n\n* `{{name}}`: Cowork plugin name\n* `{{capability}}`: Business capability the plugin supports\n* `{{skills}}`: Specialized skills to bundle, or `none` for a connector-only package\n* `{{connector}}`: MCP connector requirement, or `none`\n* `{{outputDir}}`: Package output directory\n\n## Requirements\n\n1. Read `.github/skills/development/cowork-plugin-creator/SKILL.md` in full before authoring files.\n2. Decompose `{{capability}}` into non-overlapping skills. Each skill owns one stage, task, or domain and defers explicitly at its boundaries. The package must declare at least one skill or at least one connector.\n3. Create `{{outputDir}}/<plugin-name>/manifest.json` with `manifestVersion`, a stable GUID `id`, `version`, `developer`, `name`, `description`, `icons`, `agentSkills`, and any `agentConnectors`. Do not add fields outside the supported schema.\n4. Add `color.png` at 192x192 pixels and `outline.png` at 32x32 pixels, and reference both from `icons`.\n5. Create `skills/<skill-name>/SKILL.md` for every skill. The frontmatter `name` must be kebab-case and match its folder name exactly, and the description must contain realistic trigger phrases.\n6. Register every skill folder in `agentSkills`. Populate `references/` and `scripts/` inside a skill folder only when that skill needs them.\n7. When `{{connector}}` is not `none`, add an `agentConnectors` entry with an HTTPS `mcpServerUrl`, a packaged `mcpToolDescription` file under `tools/`, and an `authorization` block whose `type` is `None`, `OAuthPluginVault`, `ApiKeyPluginVault`, or `DynamicClientRegistration`. Every type except `None` requires a vault `referenceId`. Never embed credentials in the package.\n8. Do not leave TODO markers, generic placeholders, secrets, personal data, customer-sensitive data, or unsupported claims.\n9. Require human review before sending, publishing, deleting, approving, or taking another consequential action.\n10. Run `.github/skills/development/cowork-plugin-creator/scripts/New-CoworkPluginPackage.ps1` against the completed source directory.\n11. Verify the zip contains `manifest.json`, both icons, and every registered skill folder at the archive root with no wrapper directory.\n12. Return the generated zip path and a concise list of packaged files. The final deliverable must be the zip file, not only a Markdown response or source directory.\n\n## Output Format\n\n```markdown\n## Cowork Plugin Package\n\n**Plugin**: <name>\n**Capability**: <capability>\n**Archive**: [<archive-name>.zip](<workspace-relative-path>)\n\n### Package Contents\n\n* `manifest.json`\n* `color.png`, `outline.png`\n* `skills/<skill-name>/SKILL.md` (when a skill is declared)\n* `tools/<tool-description>.json` (when a connector is declared)\n\n### Skills\n\nOmit this section for a connector-only package.\n\n| Skill | Purpose | Triggers |\n|-------|---------|----------|\n| <skill-name> | <purpose> | <trigger phrases> |\n\n### Next Steps\n\n1. Upload the package for personal testing in Microsoft 365 Copilot Cowork.\n2. Validate skill routing, connector access, and approval prompts.\n3. Publish through Microsoft 365 administration after business, security, and privacy review.\n```\n\n## Constraints\n\n* Never fabricate connector endpoints, tool names, credentials, or customer data\n* Never wrap package contents in an extra parent directory inside the zip\n* Ask only for genuinely missing essentials, then proceed", "variables": [ "name", "capability", "skills", "connector", "outputDir" ], "notes": "Create an upload-ready Microsoft 365 Copilot Cowork plugin zip with manifest.json, icons, and one or more agent skills, MCP connectors, or both. Arguments: name=... capability=... skills=... [connector=none] [outputDir=artifacts/cowork-plugins].", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/jnPiyush/AgentX", "path": ".github/prompts/cowork-plugin-create.prompt.md", "ref": "87e53aa71c1735e6200294240920d0221899a6f7", "url": "https://github.com/jnPiyush/AgentX/blob/87e53aa71c1735e6200294240920d0221899a6f7/.github/prompts/cowork-plugin-create.prompt.md", "key": "jnPiyush/AgentX/.github/prompts/cowork-plugin-create.prompt.md" } } }

Create Cowork Plugin Package

About

Create Cowork Plugin Package

Inputs

Requirements

Output Format

Constraints

Install Create Cowork Plugin Package and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews