Four related concepts
These are not four mutually exclusive file formats. Both Agent Plugins and Xpert Plugins can deliver Assistant Templates. A Plugin App can reference templates to initialize its entry and collaborating roles. Users converse with the resulting published Assistant instances.
Choosing an approach
File packages depend on models, tools, sandboxes, and connectors already supported by the destination system. MCP configuration can describe a service connection without implementing the service itself. Install a native extension when new server functionality is needed, then reuse it across multiple file-based templates.
Where capabilities belong
The Assistant definition determines its responsibilities: roles and instructions, actual skill dependencies, tools, first-use requirements, and routines. A plugin is the delivery vehicle and should not maintain a duplicate inventory of Assistant capabilities. Template details derive Memories, Skills, Routines, and Integrations from these declarations. App highlights explain business value, while app composition lists actual roles and resources. These sections should not repeat the same marketing copy. Dependency binding resolves a template reference to an actual resource in the destination environment, such as a skill, MCP service, or toolset, and records its version. It does not bind marketing text or grant all capabilities in a plugin.Importing, adding, authorizing, and using
Copying package files distributes them; platform validation is still required before use. Installation does not sign into third-party accounts. A ready organization app does not grant every employee access. Workspace editing and published-Assistant use permissions are managed separately.
Apps currently initialize private workspaces maintained by the initializer. Business users receive published-Assistant access through organization groups. See Application configuration and Assistant and application authorization.
Office Ops and the template series
Office Ops is a file-based Agent Plugin containing a template, seven office skills, initial ledgers, and initially paused routines. It does not require a dedicated NestJS module for the role. Models, file operations, approval, and scheduling use existing platform capabilities. The plugin repository’sagent-plugins/assistants/ directory manages Office Ops alongside 89 other template packages. Categories cover sales and customers, marketing, operations, personal tasks, product management, design and creativity, engineering, and recruiting. Categories support discovery without changing permissions or execution behavior.
Templates share a consistent avatar series. English and Chinese names and descriptions follow the interface language; internal skills and execution instructions need not be translated. Plugin icons and Assistant avatars are separate configuration surfaces, so changing a plugin icon does not automatically update its template avatar.
These roles use Xpert’s template contract; direct import of another product’s private template files is not promised.
Versions and upgrades are separate
Package versions describe delivered content. Template-source versions determine available instance upgrades. Accounts, preferences, conversations, files, and task state belong to actual instances. Installing a new package version does not silently overwrite existing Assistants. Users inspect changes and local conflicts in an upgrade preview, save a draft, and publish the new definition. App initialization repair is separate from template upgrades and database migration. An explicit source migration can move a native-plugin template to an Agent Plugin after compatibility checks. Matching display names do not establish matching identity.Continue reading
- Using Assistant templates: discovery, import, setup, routines, sharing, and upgrades.
- Discover & add: operating the four entry points.
- Application configuration: declaring and initializing business apps.
- ChatKit plugins, middleware, and digital experts: conversation selection and runtime boundaries.