Publish to Explore

Share a factory, workflow, agent, skill, command or prompt with your team or every Duun workspace, without leaking secrets.

On this page

If you’ve built something useful, such as a factory template, a skill or a slash command, you can publish it so others can install it. You choose who sees it, from just you to every Duun workspace. Duun checks what would travel with it first, so secrets and internal details stay behind.

What you can publish

Factories (as templates), workflows, agents, skills, commands, prompts and project templates. Built-in workflows can’t be published again; they’re already on Explore.

Publish an item

  1. Open the item and choose Publish to Explore… from its menu. You can also select Publish… at the top of Explore and pick what to publish.
  2. On Listing, fill in the title, a short summary and a readme. Add a category, roles, stack and example prompts so people can find it. The preview card updates as you type.
  3. On Audience, choose who can see it. The options are explained below.
  4. Read the preflight table under the audience options. It shows what travels with the item and what doesn’t. Fix any row that blocks publishing.
  5. On Review, check the card and the version, then select Publish. The first version is 1.0.0.

Who can see it

AudienceWho
PrivateOnly you
TeamThe teams you pick
WorkspaceEveryone in your workspace
Anyone with the linkNot listed; anyone with the link can view and install
Public on ExploreListed for every Duun workspace

Public items also need a filled readme and at least one example, and must not contain secrets.

What the preflight check does

  • Agents, skills and commands you own travel with the item.
  • Integrations become requirements. People installing it connect their own.
  • Secret values, repo names, machine IDs, webhook URLs and Slack channels are replaced with placeholders, so nothing internal is shared.
  • Items someone else owns block publishing until you remove them or the owner publishes them.

Publish a new version

Open Explore → Your library → Published by you, then choose New version… from the item’s menu. Pick patch, minor or major and write release notes; people who installed it see them when they update.

Unpublish

Choose Unpublish from the same menu. Unpublishing takes the item off Explore. Workspaces that installed it keep their copy.

If something goes wrong

  • Publish is blocked. A preflight row says the item uses something you don’t own. Remove it, or ask the owner to publish it first.
  • You can’t choose Public. Your workspace’s Admin may limit public publishing, or the checklist isn’t complete.

Developers can publish skills from the CLI with duun skills publish; see Publishing to Explore.

    Type to search the docs, help center and blog.