Library and collections

Prompts, agents, workflows, MCP tools and skills live in one library with tags, search and collections. How to organise it.

Updated 17 October 2026 · View as Markdown

The Library is where everything lives. It holds five kinds of asset:

KindWhat it is
PromptTyped pieces that render into text. Prompts can also be saved as a response or a context
AgentInstructions, a provider and settings
WorkflowNodes that pass results on in order
MCP toolA name, a description and an input schema, with a mock or HTTP execution
SkillKnow-how your AI can pick up: a description and its inputs

Pieces are reusable fragments that prompts can include. They have their own page in the Library.

Give assets tags as you create them. Search covers everything you own, by title, tag or text, across all kinds. Your AI can search the same way with prompts and action search.

Collections#

A collection is a named shelf. It can hold any kind of asset, and an asset can sit on several shelves.

  • Create a collection, then add assets to it.
  • Taking an asset off a shelf does not touch the asset.
  • Deleting a collection leaves its assets where they are.

A collection is a good way to group everything for a client or a project: the prompts, the agent that uses them and the workflow that chains them.

Plan limits#

Prompts, workflows and agents are counted per plan. See Plans and limits.

For your AI#

The collections tool has create, list, get, add, remove, update and delete. See the reference.