Lesson 8 of 8⏱ 5 minEveryone
Ship it
Updates, getting listed, and a final checklist.
In 30 seconds
- A published version never changes: raise the version for any change.
- Send your item to us. We review it, sign it and publish it.
- Use the checklist before you send it.
Updating your item
- A published version never changes. To change anything, raise
version. The release process refuses changed files under an old version number. - Updates ask again only if what your item reaches, keeps or adds has changed.
- Be careful with data. If your item keeps data, make sure a new version can read what the last version saved.
Getting listed
Every release in the Marketplace is signed by Tallgeese, which is what lets the app trust it. So the path for your item is:
- Build and check your item.
- Send it to us. We read your text and instructions, rebuild your tool from source, and try the item for real.
- We publish it in the next catalog release.
- Updates follow the same path with a new version number.
Tell us what you're making
Write to developers@tallgeese.ai with a few lines about your idea, which parts it uses, and your item folder or a link to it. Paid items are sold through the Marketplace's own checkout.
What we look for
- Everything you declare is true and as small as possible.
- The words are clear, friendly and accurate in all five languages.
- It works well in real use, not just on paper.
- You have the right to everything inside: licences are kept for adapted work, and a service's logo is used within its brand rules.
- It avoids things we leave out on purpose: tools for building software, and anything that can spend or move money without clear approval.
Before you send it
| Area | Check |
|---|---|
| Project | tgs-market check . says nothing. The id is lowercase with hyphens. The version was raised if anything changed. |
| Words | All five languages, the same number of tasks and prompts, no technical terms, a native speaker has read the translations, honest about the internet and sign-in. |
| Skills | Each description starts with when to use it and stays short. Steps are numbered. Failure cases are covered. Nothing runs. |
| Connector | You tried the sign-in with a real account. You read the service's tool list and trimmed it. Everything that changes something asks first. The service's terms allow it. |
| Tool | It reaches the minimum. Descriptions are short. Answers are bounded and say how to continue. The built file is included. |
| Specialist | Instructions are focused. Consequential actions are confirmed in chat. Every setting and button has text in all languages. The page works in light and dark mode. |
| Testing | Every example prompt tried. An unrelated question leaves your item alone. You've said which computers you tried. |
| Rights | Licences kept for adapted work. Logos used properly. Nothing pretends to be someone else. |
Need an exact field or limit? Open the reference. Want inspiration? See the reference apps.