Publishing to Explore

Share skills, commands, agents, workflows and factory templates beyond your workspace: visibility, preflight checks, versions and unpublishing.

On this page

Explore is Duun’s catalog of factory templates, workflows, project templates, agents, skills, commands, prompts and connector presets. Anything you build in your workspace can be published there, to your team, your workspace, anyone with a link, or every Duun workspace. This page covers skills and commands in detail; the same flow applies to the other kinds.

Start a publication

Open Publish… from:

  • A skill’s or command’s menu in Settings → Skills & commands (Publish to Explore…).
  • An agent’s menu (Publish…), or a workflow’s menu (Publish as template…).
  • The Publish… button on Explore, which first asks what to publish.

Built-in workflows can’t be published: they are already on Explore.

The Publish wizard

  1. What. Pick the object to publish, if you didn’t start from one.
  2. Listing. Title, summary (up to 140 characters), readme (Markdown, prefilled from the description), icon, colour, category, roles, stack, tags and example prompts. A live card preview shows how it will look in Explore.
  3. Audience. Choose a visibility and review the preflight table.
  4. Review. Check the card, set the version and add release notes, then select Publish.

Visibility

VisibilityWho can see and install it
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 listings add a checklist before you can continue: no secrets, a filled-in readme, and at least one example prompt.

Preflight

Preflight looks at everything the item refers to and sorts it into classes, so nothing private leaves by accident:

ClassWhat happensExamples
TravelsIncluded with the itemAgents, skills and commands you own that it binds
Already visibleReferenced, not copiedItems already at or above the chosen visibility
Becomes a requirementInstallers are asked to connect their ownIntegrations such as Linear or Sentry
StrippedReplaced with a placeholderSecret values, repo names, machine ids, webhook URLs, Slack channels
Not ownedBlocks publishingItems someone else owns

A Not owned row blocks Next until you remove the reference or the owner publishes that item at the same visibility or wider.

For a skill, preflight checks SKILL.md and every file in scripts/ and references/. Strings that look like keys or tokens are flagged; replace them with an environment variable that installers provide as a secret.

Versions

The first release is 1.0.0. Each later release picks patch, minor or major and requires release notes. As a rule of thumb:

BumpWhen
PatchWording fixes, clearer steps, no change in behaviour
MinorNew steps, new optional files, broader coverage
MajorDifferent behaviour, renamed scripts, new requirements

Installers with Auto-update on get patch and minor releases automatically unless they edited their copy. Everyone else sees Update to x.y in Your library, with the changelog for the versions they missed.

To release a new version, open the publication from Explore → Your library → Published by you and choose New version…. The wizard starts at Listing with your fields filled in.

Publish from the CLI

The CLI publishes a skill folder or an existing workspace skill:

duun skills publish ./postgres-migrations --visibility public --bump minor \
  --notes "Adds a backfill script and a lock-level reference."

Without --bump, the first publish is 1.0.0 and later ones are a patch. The command prints the preflight table and stops with exit code 3 if any row blocks publishing. See the CLI reference and, for automation, POST /skills/{skill}/publish in the Skills API.

Manage a publication

Your library → Published by you lists every publication with its visibility, state, views, installs, active installs and remixes. Each row’s menu has:

  • Edit listing: change text and images without a new version.
  • New version…: release a change.
  • Change visibility: lowering visibility asks you to confirm (“Reduce access?”).
  • Copy link.
  • Unpublish.

Unpublish

“Unpublishing takes the item off Explore. Workspaces that installed it keep their copy.” They stop receiving updates. You can publish again later, which continues from the last version number.

Share without publishing

To give teammates access inside the workspace without a listing, use Share… instead. It grants people or teams Can use or Can edit, can let everyone in the workspace use the item, and can turn on a link. See Share with your team.

    Type to search the docs, help center and blog.