Release to the marketplace

You will have a released template people can find and install.

Prepare a marketplace release

Copy promptCopiedHelp me release <template slug> to the Super Artifacts marketplace with super_release_template. Check my plan, the version, the sample and the private demo first. Explain what moderation checks. Ask for my consent before making the demo or personal sample data public.

Before it is listed

Marketplace release needs a paid plan with template publishing enabled. super_release_template releases a recorded version, separately from saving a draft. Releases only move forward.

The release scans the template's runtime, sample and listing text for live secrets. A detected credential refuses the release. First releases go to moderation; later changes can also need review. The review checks the sample, personal data flags and what the template asks another agent to do.

A private demo stays private while the first release waits for review. Approval can make it public with your explicit demo consent. Sample data containing personal details needs separate consent to be shown. Consent is a decision about the content you are exposing.

The listing

The listing carries the preview, description, use cases and requirements. Ratings count from workspaces that built something with it. Reports flag problems for review; they are separate from ratings.

A bad revision

A rollback creates a new draft version carrying an earlier version's content. It does not erase history or move a release backwards. That new version still needs releasing. Restoring across a runtime change can be refused, because history holds file digests rather than old runtime bytes.

Check it worked

The template's page shows its review state. Once approved and released publicly, its marketplace listing is visible and Install uses the released version. A pending chip means it is still waiting.

Next: Collect responses.