Skip to content

Publishing offers a reviewed, immutable version of your work as a template. A strong template explains what it helps someone accomplish, includes the material needed to begin, and makes their remaining setup clear.

Prepare the result and listing

Choose work you have permission to manage and redistribute. Show a representative deliverable, explain the intended audience, and describe the task it supports. A live demo is optional; a clear example can communicate the capability without a running Site.

SourceReusable material
AgentSupported reusable configuration and resource definitions
ChatCurrent working files and eligible editing assets from linked Artifacts
ProjectSaved source and supported portable development configuration

Review included dependencies and redistribution rights. Being able to read a File or use a Skill does not automatically authorize publishing it.

Review the package

  1. Prepare the source and listing.
  2. Inspect the exact contents proposed for publication.
  3. Resolve required material that cannot safely be included.
  4. Explain the recipient's account and capability setup.
  5. Choose the version change and write useful release notes.
  6. Review the standard publication terms and explicitly confirm publication.

Private messages, execution history, credentials, account bindings, balances, grants, and production Site relationships stay out. Relevant source or configuration changes require a fresh review before publication.

Maintain the published work

Listing edits change its presentation. A new published version changes the reusable package. Neither automatically updates existing remixes. See Versions.

Workspace policy can restrict publication. Merchant setup may also be required by the publishing workflow; use Merchants to complete the available setup. Publication alone does not earn an allocation—Earnings explains eligible use.

Example: package a review specialist

A reusable report-review Agent might include its method, permitted reference material, and setup instructions. Replace private examples with material you can redistribute and explain which account connections the adopter must supply.

Review the exact proposed package after the cleanup. A useful listing should let someone understand the first task they can run and how to judge its result. See Versions and Remixing.

Write the first-use instructions

Tell adopters what to supply, what to run first, and how to check the result. For a review specialist: “Attach a report, request a review against the included criteria, and verify that each finding cites the relevant passage.” Identify required connections separately from optional improvements.

Keep example data safe to redistribute. After source or configuration changes, review the newly proposed package rather than assuming the earlier review still describes it.