Publishing Agent & Team Presets

If you’ve built an agent or team worth sharing, you can publish it as a preset so other users can install it. This page covers publishing an agent preset and a team preset. Creating and publishing a single skill is covered separately in Creating Skills. To find and install presets other people have already published, see Installing Skills & Presets.

Publishing an agent as a preset

1. Go to the chat screen of the agent you want to publish
2. Click the Share & Publish icon at the top of the screen
3. Click Agent Preset

Agent Father tidies it up first

Clicking the button doesn’t open the review screen right away. First, a helper named Agent Father prepares the publish for you. This runs automatically, in four steps:

1. Looking through the agent’s personality and memory
2. Generalizing so others can plug in their own setup
3. Checking what may not travel cleanly
4. Saving the draft

An agent with a lot of memory can take a bit longer, but it keeps running in the background even if you close the window. Once it’s ready, an Open the review screen button appears — click it to move on.

The review screen — three steps

This is where you review, edit, and actually publish the draft Agent Father handed you. It has three steps.

Step 1 · Basic info — Enter the preset’s name, description, and category, and choose whether to publish it public or private. If the agent currently has an active web app, a toggle for including it in the preset also appears here (for how bundling a web app works in detail, see the Advanced section of the installing guide).

Step 2 · Brain — Pick which files to include from this agent’s persona (SOUL.md) and memory files, using checkboxes. Uncheck anything containing personal information, and edit a file’s body directly if you only want to keep part of it.

If you came through Agent Father, notes that describe the state of a job you’re in the middle of (personal working notes like “what to do next on this task”) start out unchecked in this list. These are true only for you, and unlikely to mean anything to whoever installs the preset. The screen tells you how many were left out and which files they are — check them back in yourself if you decide they should be included.

Step 3 · Customize · Schedules — If installers should each answer differently for some value, turn on “Customize” and register questions (installers are walked through a short interview at install time). If this agent has any scheduled runs, pick which ones to include in the preset here as well.

If you came through Agent Father, this step may also show “Things to double-check before sharing” above the rest. For example, if the content pins something that’s different for every installer (say, a file path specific to this one agent), you’ll see a warning. This kind of warning doesn’t block publishing, but it’s worth a second look — left as-is, it hands installers something that doesn’t apply to them. Anything that looks like sensitive information such as an API key, or hidden instructions meant to manipulate whoever installs the agent, is flagged more strongly, and in that case the publish button stays disabled until it’s cleaned up — go back to the agent, fix the flagged part, then call Agent Father again to refresh the draft.

Once you’re done reviewing, click Publish. You’ll get a link to view it on the marketplace; if you published it private, you’ll see a “Published privately” notice and only you can see it. See the installing guide for how to switch a private preset to public later.

Publishing a new version of a preset you’ve already shared

Publishing an agent again after it’s already published creates a new version (v2, v3, …). In that case, Step 1 becomes “Version info”: a Changelog field for describing what changed, plus a checklist of what to update this time (model, config, schedules, web app). Skills aren’t in that list — they’re always refreshed to whatever version the agent currently uses. If you’re republishing a preset you forked from someone else’s, the changelog must be at least 30 characters before you can publish.

Publishing a whole team as a preset

A team made up of multiple agents can also be bundled into a single preset. There’s one thing to prepare first, though — every member you want in the team preset must already be published as its own agent preset. Publish each teammate individually using the steps above before bundling them.

1. From the team’s screen, click the Share & Publish icon at the top of the screen
2. Click Team Preset

Unlike an agent preset, there’s no automatic Agent Father preparation step — the publish form opens right away.

• Name, description, category — information about the team preset itself.
• Pick members — choose which of your already-published agent presets to include. They don’t have to actually belong to this team — anything you’ve published is fair game.
• Shared questions (optional) — if the members you picked have overlapping customization questions, they’re suggested as candidates. Confirm one and it’s asked only once at install time, applying the same answer to every member that uses it.
• Public or private, changelog — same as an agent preset.

Pick at least one member and click Publish to register the team preset. There’s no re-review of individual members’ Brain files here — each one was already reviewed when it was published on its own.

Managing a published preset

For switching a published preset between private and public, republishing it to pick up newer skills, and who’s allowed to make an organization preset public, see the My Presets sections of Installing Skills & Presets — publishers and installers share the same screen there.

---

Advanced

Read this only if you’re curious what’s being checked under the hood during publishing.

• The “true only for the publisher” axis: both the default-off personal notes in Step 2 and the warnings in Step 3 are computed once, when Agent Father builds the draft, and handed to the review screen from there. Publishing an agent preset always goes through Agent Father, so this check runs every time.
• Team presets don’t have this axis at all: publishing a team preset only combines agent presets that were each already reviewed and published on their own, so the team preset screen itself does no Brain file review or personal-note detection.
• Warnings vs. blocking: the default-off for personal working notes and the warning for per-installer values are both “just a heads-up” — neither blocks publishing. Anything that looks like a secret, or like a hidden instruction meant to manipulate whoever installs the agent, is treated more seriously and keeps the publish button disabled until it’s addressed. We don’t publish the exact rules used to detect these, but when one trips, the screen tells you which file and what was found.
• Older client compatibility: a client that doesn’t know about these two checks falls back to the safe behavior — showing every Brain file checked by default.