Catalogue
Publish teams, roles, skills, prompts and document templates that every workbench in your organisation pulls in.
The catalogue is your organisation's shared library for AI Workbench. Whatever you publish in it, every workbench and node pulls into its templates on its next sync: the same agent roles, the same skills, the same prompts and document templates for everyone. Entries are content, not programs: nothing in the catalogue runs when a workbench downloads it.
Administrators publish to the catalogue. In Mojo Up AI Cloud that is a team's owners and admins.
What you can publish
| Kind | What it is | Content |
|---|---|---|
| Role | An agent role: who the agent is and how it works. | Markdown |
| Skill | A piece of know-how agents can use. | Markdown |
| Prompt | A prompt people can reuse. | Markdown |
| Team | A team template: its members, built from roles and skills. | Team configuration (JSON) |
| Document template | A template for a document, such as a decision record or a design document. | Markdown with front matter naming the template, its summary and the path it is written to |
Tool servers are published from the Tools view instead: see Tools.
Publish an entry
Open Catalogue
The Published list shows every entry with its kind, identifier, version and summary, and when the catalogue last changed.
Fill in Add or replace
- Id: a short identifier, for example
code-review. Publishing with an id that exists replaces that entry. - Kind: role, skill, prompt, team or document template.
- Name and Summary: what people see in the workbench.
- Version: your own version label, shown beside the id.
- The content: Markdown, or for a team its configuration as JSON. Choosing Document template starts the content from an example of its front matter.
Publish
Choose Publish. Workbenches pick it up on their next sync. To change an entry later, choose Edit beside it; to withdraw it, choose Remove.
Team templates on shared compute
A team member can be placed on shared compute (headless nodes) with runsOn in the team configuration, for example:
"runsOn": { "tags": ["gpu"], "requires": {}, "fallback": "local" }A template names node tags, never a particular node; the console lists the tags your nodes carry under the editor. A template that names a node is refused. See Nodes.
Enterprise teams
In self-hosted AIOE, portfolio managers also build enterprise teams under Portfolio, Teams: a team's members are catalogue roles with their skills, or people, and the team is granted to projects and to compute pools (node tags). A member's instructions are its role's catalogue content followed by each of its skills. Workbenches load the teams granted to a project read-only. See Projects.