Publishing your first extension
Create a useful marketplace listing, upload a checked package, and understand first approval and later releases.
On this page
A good marketplace listing explains what a package does, who it is for, and what users need to run it. Publish actual packaged work rather than a promise of a future capability.
Prepare your account and listing
Register a website account and verify your email address. GitHub linking is optional. In the creator workspace, supply a clear name, summary, description, type, category, license, declared compatibility, and support URL.
Describe the concrete workflow, required desktop or engine version, limitations, and relevant installation instructions. Keep screenshots tied to the version they demonstrate. Do not include provider credentials, private project files, or setup tokens in the package or listing.
Upload a release
Build the archive for its actual package type and upload it with a version and release notes. Platform plugins use their supported manifest and runtime contract; editor extensions, skills, and roles have different packaging requirements. The source integration reference is useful for authoring contracts; this website's package checks have their own marketplace requirements.
Review check results before submitting. Checks inspect archive paths and limits, required files, identity, version declarations, compatibility, license metadata, and integrity. They do not execute the package or establish its safety and runtime behavior.
Understand publication
Your first publication needs administrator approval. A submitted package is not public until that approval succeeds. Address requested changes in the listing and package rather than resubmitting an unchanged release.
After approval, later checked releases can publish automatically unless the administrator requires manual review for that listing. Public versions keep their uploaded package identity. Use release notes to identify behavior changes, migration instructions, and the tests you actually ran.
See installation from a user's perspective and plugin contracts when extending the platform.