From your project to the Skill Store
On this page
Publishing a release and listing it publicly are separate choices. You can prepare your project before you apply.
Who this is for: authors who are ready to share a theme or declarative app with other Jibo owners through the Skill Store.
1. Apply once
Open the publisher dashboard, choose a display name and tell us what you want to build. An operator reviews the publisher identity. Publisher approval permits submissions within account limits; every third-party submitted version also needs a separate exact-bundle operator review before it can be signed and published.
If you are signed out, the console asks you to sign in and brings you back to Publish. Your publisher status and current limits appear there.
2. Create an app identity
Choose Create an app identity. Copy its app-… ID into your manifest. Each identity belongs to the publisher who created it. Never submit an example using its original app ID or assume a locally generated ID is registered.
3. Check the pack
Use the theme kit to validate and pack your source. Set a plain X.Y.Z version and accurate release notes. For updates, keep the app ID and increase the version. Submitted and published versions cannot be overwritten. A corrected pack uses a higher version and receives fresh review.
Check your asset rights, text contrast, minimum software version and required theme API. Describe what the theme changes, not capabilities it does not have.
Theme reference · Release checklist · Test on your Jibo
4. Upload a theme
In Publish a theme, choose a .phtheme file, or a .zip containing one theme folder with theme.json and its listed images. Check the name, version, preview and What it changes before publishing.
The server validates the pack, normalizes the images and keeps an immutable pending submission outside public releases. An operator inspects the source and normalized bytes and records approval, rejection or requested changes. Only approved exact bytes can be signed and published. A rejected upload shows what needs fixing. Do not repeatedly retry the same rejected pack; uploads count toward the account's rate limit.
If ZIP support is unavailable in your browser, pack locally and choose the .phtheme instead. The regular declarative app .json picker is not the theme picker. Native skill bundles do not use either picker.
5. Choose when to list it
Read the submission state under Your apps. Pending, rejected and changes-requested versions are not public releases. After operator publication, choose List publicly when you want owners to find it. A pending update leaves the prior public version available. Publishing alone does not apply a theme to a Jibo.
Owners choose their own Jibos. They install a theme, try it, then choose Keep or Undo. Themes do not require an on-robot approval tap. Native app installation, updates and removal require physical approval on Jibo.
Updates and removal
Use Upload a new version on your theme's card to return to the theme upload form. Increase the version and include release notes. Release updates do not use another app slot.
Unlisting hides the listing from browsing; it does not remove existing installations. Withdrawal and archiving are separate controls. Read their current state in the publisher dashboard before changing availability.