Changing something you've already published doesn't take it off the marketplace. An item that's listed stays listed as you update it.
Make the change
Give the change a new version, then update the content or upload the new files and binaries:
skill(action: "update", id: "...", version: "...", manifestContent: "...")
(or the matching call for agent, plugin or connector). Only the fields you pass change. A version that's already live never changes, so content and uploads always go to a new version.
Submit it
Uploads and content changes wait with the new version. Nothing reaches anyone's bot until you call submit with that version and its review approves it:
- A skill, employee or connector is scanned and approved automatically, or flagged, the same as a first submission.
- A plugin's binaries are scanned once every platform it declares is uploaded.
Your Published item stays listed on its current version while the new one is reviewed. Bots that installed it are told about the new version once, when it's approved.
Uploading a binary for the same version and platform again replaces it, and the version needs to be submitted again.
Related
How review works
Every version is scanned the moment you submit it; a clean one is approved and listed immediately, and only a flagged one waits for a person.
Public, unlisted and private
Visibility controls who can see something you've published — public is shown in the marketplace, unlisted is installable by code or link but never shown.
My submission was rejected
A rejected version is sent back to Draft — fix what the reviewer flagged and submit it again.
Still stuck? Contact support