Summary
Add support in the Xpert plugin system for bundling and loading Codex-like plugin resources, such as skills, MCP servers, hooks, and related resource definitions.
Motivation
As plugins become more capable, they often need to provide more than UI pages or server-side business logic. A plugin may also need to ship agent-facing instructions, reusable skills, tool/server integrations, lifecycle hooks, or other resources that extend how agents work inside Xpert.
Supporting these resources as first-class plugin bundle assets would make plugins more self-contained, portable, and easier to install or distribute.
Requested capability
It would be helpful if the plugin framework could support bundled resources such as:
skills: plugin-provided agent skills or workflow instructions.mcp: MCP server definitions, tool registrations, or connection metadata.hooks: lifecycle/event hooks for agent, plugin, or workspace behavior.- Other plugin bundle resources that may be discovered and loaded by the platform at install/runtime.
Possible design direction
The plugin manifest could declare these resources explicitly, for example as plugin bundle sections or resource entries. During plugin installation or activation, Xpert could discover, validate, register, and expose them to the relevant runtime surfaces.
Expected behavior might include:
- Package resources together with the plugin.
- Validate resource schema and permissions before activation.
- Enable or disable resources with the plugin lifecycle.
- Expose plugin-provided skills/tools/hooks to agents in a scoped and permission-aware way.
- Support local development and production packaging consistently.
Example use cases
- A business plugin ships its own agent skill instructions and domain-specific workflows.
- A plugin provides MCP tools for external systems and registers them automatically.
- A plugin hooks into workspace, chat, or agent lifecycle events.
- Teams can install one plugin bundle and get UI, server modules, tools, skills, and hooks together.
Notes
This is similar in spirit to Codex-style plugin bundle resources, where a plugin can package multiple extensibility surfaces instead of requiring each resource to be installed and configured separately.
Summary
Add support in the Xpert plugin system for bundling and loading Codex-like plugin resources, such as skills, MCP servers, hooks, and related resource definitions.
Motivation
As plugins become more capable, they often need to provide more than UI pages or server-side business logic. A plugin may also need to ship agent-facing instructions, reusable skills, tool/server integrations, lifecycle hooks, or other resources that extend how agents work inside Xpert.
Supporting these resources as first-class plugin bundle assets would make plugins more self-contained, portable, and easier to install or distribute.
Requested capability
It would be helpful if the plugin framework could support bundled resources such as:
skills: plugin-provided agent skills or workflow instructions.mcp: MCP server definitions, tool registrations, or connection metadata.hooks: lifecycle/event hooks for agent, plugin, or workspace behavior.Possible design direction
The plugin manifest could declare these resources explicitly, for example as plugin bundle sections or resource entries. During plugin installation or activation, Xpert could discover, validate, register, and expose them to the relevant runtime surfaces.
Expected behavior might include:
Example use cases
Notes
This is similar in spirit to Codex-style plugin bundle resources, where a plugin can package multiple extensibility surfaces instead of requiring each resource to be installed and configured separately.