Skip to content
GitHub

How a catalogue works

Publish your own packs and profiles for your agents to install from.

Create a catalogue with one command, then add your own packs to it.

A catalogue is a folder with a catalogue.toml at its root, a packs/ folder of packs, and a profiles/ folder of named pack lists. With agentbundle installed, scaffold it:

agentbundle catalogue init my-catalogue --name my-catalogue

This writes catalogue.toml, a root AGENTS.md (which catalogue package needs to build a release), and an _example pack and profile. It never overwrites an existing file, so running it again is safe. A fresh catalogue packages into an empty release until you add a real pack.

Confirm the scaffold is valid:

agentbundle catalogue verify --root my-catalogue

A failure names the check and its fix.

Copy packs/_example to packs/my-pack and edit its pack.toml:

schema = 1
[pack]
name = "my-pack"
display-name = "My Pack"
description = "A short description of what this pack does."
version = "0.1.0"

Folders that start with _ are templates that discovery skips, so run verify again after you add a real pack.

Lint before CI packages and publishes it:

agentbundle catalogue lint --root .

The Catalogue CI contract defines the packaging and publish steps.

Next, configure catalogue.toml to set the catalogue’s identity and distribution.